will Chrome drop WebSQL support?

[Raul]

We have a complex HTML5 offline application using WebSQL. It isn't
easy migrate it to IndexedDB. Will Chrome drop WebSQL support? Is
there a date for this?

Thank you in advance!

[Jordon Wii]

I'd imagine it isn't really known at this point, but if it is I'd be
interested to know as well.

It really is a shame that WebSQLdb got dropped from the spec.

[wtayl...@googlemail.com]

I am in the same boat. Where is the best place to go to keep up to date with any planed changes to Chrome?

[Ido]

Hey Raul,

I hear you about the pain of migrating... 

But I guess, if you wish to work with a spec that is 'live' (=being improved/fixed) you need to do the move.

I've wrote this: http://www.html5rocks.com/en/tutorials/webdatabase/websql-indexeddb/ in order to try and help... 

Good luck,

Ido

[Alec Flett]

http://chromestatus.com/ is a great resource for this kind of thing.

There are no immediate plans to deprecate WebSQL, but as it is not cross-browser, barely maintained, and generally receives no attention, I would focus on IndexedDB.

Alec

--
You received this message because you are subscribed to the Google Groups "Chromium HTML5" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-html...@chromium.org.
To post to this group, send email to chromiu...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-html5/?hl=en.
For more options, visit https://groups.google.com/a/chromium.org/groups/opt_out.
 
 

[Joshua Bell]

Going forward, we'll make announcements about feature deprecations to the Chromium Blog (blog.chromium.org).

For example, in M24 we deprecated/removed some features:

http://blog.chromium.org/2012/11/a-web-developers-guide-to-latest-chrome.html

[Anil Sharma]

Hi All, any update on it? I'm also developing an app using phonegap and websql. I expect it would be supported for at least one more year. after that I'll go with native versions of my app.

[Austin France]

We also have an application using WebSQL.  

We did manage to migrate it to IndexedDB (I can toggle which DB it uses) but is was very difficult, and the IndexedDB version is nowhere near as performant, primarily through lack of support for various types of operations.  IndexedDB isn't really mature enough for serious DB work yet.

I can provide some examples if interested.

Regards
Austin

--

You received this message because you are subscribed to the Google Groups "Chromium HTML5" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-html...@chromium.org.
To post to this group, send email to chromiu...@chromium.org.

Visit this group at http://groups.google.com/a/chromium.org/group/chromium-html5/.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[Joshua Bell]

No updates to report.

On Fri, May 15, 2015 at 1:54 AM, Austin France <a...@sorcerer.co.uk> wrote:

We also have an application using WebSQL.  

We did manage to migrate it to IndexedDB (I can toggle which DB it uses) but is was very difficult, and the IndexedDB version is nowhere near as performant, primarily through lack of support for various types of operations.  IndexedDB isn't really mature enough for serious DB work yet.

I can provide some examples if interested.

It would be great to see your examples, but this probably isn't the right forum, since this is chromium-specific and advancing Indexed DB with more powerful query abilities is a cross-browser/standards sort of discussion.

You could also post to public-webapps but it sounds like you could write a nice (informal) A/B comparison doc showing what was east/fast and what was hard/slow. If you were to write up your observations (blog post, github gist or google doc, whatever) I'd be interested to read it and pass it on to other browser developers and library developers who've expressed interest in working on this exact challenge. 

[Anil Sharma]

Thanks Austin, Joshua. I'll carry on with websql itself for now.

On Thursday, March 22, 2012 at 9:38:54 PM UTC+5:30, Raul wrote:

[Austin France]

Sorry for the delayed reply.  

I was this morning working back in this area of code, so thought it a good time to re-discover the issues I encountered and document them.  I have also given an overview of how I went about changing our application to be able to switch between IndexedDB and WebSQL back ends for anyone interested.

It only covers what was hard/particularly slow/missing.

https://docs.google.com/document/d/1qsEr0j3okqmAcMNNLo-GEkKdzJvE6PfIGrJ6b-voLU0/edit?usp=sharing

Regards
Austin

[Paul Kinlan]

Interesting doc, a lot of the issues you list have are fixed by https://github.com/google/lovefield, for example it supports aggregate queries and notifications and LIMIT and OFFSETs

P

[Austin France]

Thanks Paul, Lovefield looks interesting.

Regards
Austin

[Joshua Bell]

Austin: thanks for the write-up! Very helpful, and I've already passed it on to some folks who are looking into improving the IDB API to make such things easier.

Paul: and thanks for sharing the pointer to Lovefield. We (the Chrome IDB folks) are in close touch with them, and looking at rolling their feedback into future IDB work. 

[LockHeed]

Lovefield, although a very interesting looking project, does not support sub-queries and has issues with transactions across multiple tabs.  Lovefield I think will never support subqueries which rules out
nearly all complex reports. The native websql implementation is a lot better.

I would also like to know if there are any plans of removing WebSQL from chrome.   For our current application we have sql databases available through cordova on android and iOS and through node/postgres on the server.

I'm extremely disappointed of the push to have WebSQL dropped from the spec, because there are a large range of applications that range that are not possible to build (in terms of complexity / time) using indexeddb (Think any complex statistical report  where the data is stored in multiple locations.

So are there any plans to remove WebSQL?

Is it fee-sable one could compile up sqlite into web-assembly, and if so what would be the underlying storage mechanism?