Hola Alfonso!

If you use Ext.data.proxy.SqlView, you internally use Web SQL according to
the documentation at
https://docs.sencha.com/touch/2.1.1/#!/api/Ext.data.proxy.Sql. So yes, your
app will most likely be affected.

Cheers,
Tom


On Fri, Feb 10, 2023 at 3:31 AM Alfonso Ochoa Legorreta <
[email protected]> wrote:

>
> Hi, I'm from Mexico and I have an android app created with the Sencha
> Touch framework and I use WebSQL for now everything is going great. My
> question is, will I also be affected by these changes?
> El jueves, 9 de febrero de 2023 a las 10:23:14 UTC-6, Randy Lauen escribió:
>
>> Hi Ben,
>>
>> I think that's what I'll experiment with first. I was hoping someone else
>> had traveled this road already and had some advice. My tentative plan for
>> migrating is to copy the WebSQL data to SQLite, but keep both
>> implementations running side by side for a while. If anything goes wrong,
>> users could switch back to WebSQL, at least for a while. I'm at the very
>> early stages of figuring out the new SQLite API, though, so there's a long
>> way to go.
>>
>> I don't know of any other extensions using WebSQL. The name of my
>> extension is History Trends Unlimited (Thomas asked about this earlier in
>> the thread). I created it 10 years ago, even though WebSQL was already
>> deprecated at that point. I figured the extension would eventually die when
>> WebSQL was removed; I'm very happy that there's a path forward now. Many
>> thanks to all those involved.
>>
>> --Randy
>>
>>
>> On Wed, Feb 8, 2023 at 6:05 PM Ben Morss <[email protected]> wrote:
>>
>>> *Carl*, the signs are promising for other browsers to implement all the
>>> APIs needed to run SQLite-over-Wasm. I'm optimistic!
>>>
>>> *Randy*, how hard would it be to implement something that read user
>>> data from Web SQL and wrote it into a parallel table structure in SQLite?
>>> Both of these will coexist in Chromium for some time.
>>>
>>> Let us know how this goes, if you could. I'd also like to be aware of
>>> other extensions out there that might be using Web SQL and could have
>>> missed our announcements....
>>>
>>>
>>> On Thu, Feb 2, 2023 at 6:13 PM Carl Turechek <[email protected]>
>>> wrote:
>>>
>>>> One more question is whether that will work on all browsers.. that
>>>> could at least be considered as an improvement. Also, I'm subbed to this
>>>> convo and haven't seen any notifications anywhere... Is it supposed to
>>>> email me?
>>>>
>>>> On Wednesday, February 1, 2023 at 6:50:35 AM UTC-5 [email protected]
>>>> wrote:
>>>>
>>>>> Hey Randy,
>>>>>
>>>>> On Tue, Jan 31, 2023 at 10:51 PM Randy Lauen <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Speaking of nontrivial examples, I have a Chrome extension that
>>>>>> relies heavily on WebSQL. On my desktop, the WebSQL database for my
>>>>>> extension is almost 400 MB. I know some users have a database over 1 GB.
>>>>>> I'm very excited about using Wasm SQLite, since I can (hopefully) 
>>>>>> configure
>>>>>> SQLite the way I want, instead of being stuck with the configuration used
>>>>>> by Chrome.
>>>>>
>>>>>
>>>>> Very exciting. Do you mind sharing the name of the extension?
>>>>>
>>>>>
>>>>>> What I'm not looking forward to, though, is the transition. Do you
>>>>>> have any advice on migrating data from WebSQL to Wasm SQLite? My best 
>>>>>> guess
>>>>>> so far is to have users use my extension's import/export mechanism to
>>>>>> export all of their WebSQL data to a file and then import it back into 
>>>>>> Wasm
>>>>>> SQLite.
>>>>>>
>>>>>
>>>>> Asking users to manually export their database file from Web SQL via
>>>>> your extension's export feature and then importing to SQLite is probably
>>>>> the easiest way, yes.
>>>>>
>>>>>
>>>>>> Also, with WebSQL, I can locate the SQLite database on disk within
>>>>>> Chrome's profile directory. Will that be possible with Wasm SQLite/OPFS?
>>>>>>
>>>>>
>>>>> As a developer, you can use the OPFS Explorer extension (
>>>>> https://chrome.google.com/webstore/detail/opfs-explorer/acndjpgkpaclldomagafnognkcgjignd)
>>>>> to do so.
>>>>>
>>>>>
>>>>>> Finally, between manifest v3 and WebSQL deprecation, my extension
>>>>>> will need a lot of changes this year. If it's possible to stagger the
>>>>>> deadlines for those, so I don't have to tackle both at the same time, 
>>>>>> then
>>>>>> that gets my vote!
>>>>>>
>>>>>
>>>>> The manifest v3 deadline is unrelated to this deprecation deadline.
>>>>> You can express your concerns about the extensions deadline on their 
>>>>> forum:
>>>>> https://groups.google.com/a/chromium.org/g/chromium-extensions.
>>>>>
>>>>> Cheers,
>>>>> Tom
>>>>>
>>>>

-- 
Thomas Steiner, PhD—Developer Relations Engineer (https://blog.tomayac.com,
https://twitter.com/tomayac)

Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany
Geschäftsführer: Paul Manicle, Liana Sebastian
Registergericht und -nummer: Hamburg, HRB 86891

----- BEGIN PGP SIGNATURE -----
Version: GnuPG v2.3.4 (GNU/Linux)

iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.
hTtPs://xKcd.cOm/1181/
----- END PGP SIGNATURE -----

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgRrLnbeqfsAW8%3Di%3Dd1515UH1q4U7fq7vTtboFuex_aOYrt_w%40mail.gmail.com.

Reply via email to