Lovefield – A relational database for web apps

Post by dvh » Thu, Sep 10, 2015, 2:09 PM UTC

Post by soapdog » Thu, Sep 10, 2015, 2:16 PM UTC

dvh wrote: post #2

Then why did they killed websql in chrome packaged apps?

Post by rglullis » Thu, Sep 10, 2015, 2:21 PM UTC

jdimov9 wrote: post #3

What is a browser database and what is it good for? Would you use one instead of a back-end DB or in conjunction with one? How? Why? Why is this on 1st page - what is cool about it? I'm clearly missing something, but I can't be bothered to watch the videos - can someone TL;DR it for me, please.

Post by lt » Thu, Sep 10, 2015, 2:27 PM UTC

pfraze wrote: post #7

soapdog wrote: post #4

Earlier quoted context omitted.

probably because websql was not accepted as a w3c standard. Browser vendors should not add tech that works only on their browser and are not on the path to standardization.

Yeah, that was a bummer situation. The problem was that browser APIs require independent implementations to become standard. Chrome used SQLite for their WebSQL, which left Firefox without a good option. (Implementing a SQLite clone isn't feasible with their budget.) So, the standard was dropped. It's a shame, because SQLite is a great tech.

Post by Argorak » Thu, Sep 10, 2015, 2:31 PM UTC

neilellis wrote: post #5

jdimov9 wrote: post #3

What is a browser database and what is it good for? Would you use one instead of a back-end DB or in conjunction with one? How? Why? Why is this on 1st page - what is cool about it? I'm clearly missing something, but I can't be bothered to watch the videos - can someone TL;DR it for me, please.

It's like having PouchDB -> CouchDB but with SQL not NoSQL For me I'd like to: Firebase as backend. Sync user data to browser. Query user data elegantly in browser using select statements.