Live data from Hacker News

Lovefield – A relational database for web apps

google.github.io

51–60 of 60 posts

Re: Lovefield – A relational database for web apps

#51

From the first 1 minute and 15 seconds of the video: > "With WebSQL being deprecated, and IndexedDB not providing structured queries, web developers need a tool to satisfy their structured query needs." > "Web app developers need structured queries to work in the mobile world." > "With IndexedDB ... there's a steeeep learning curve to make it useful for your app. Moreover, IndexedDB does not provide structured querie…

FYI, it's a common mistake, but it's just SQLite. :)

Re: Lovefield – A relational database for web apps

#52
post #47

Earlier quoted context omitted.

Disclosure: I'm the author of a competing JavaScript database ( http://gunDB.io/ ). Unfortunately concurrency is typically the last thing that people think about. Concurrency is the first thing we deal with in our database, because you are right, without it data gets corrupted.

So would it be possible to communicate between the two tabs, via the database? In an event-driven way?

Yes, although right now I am doing that with websockets which is silly for local stuff. We are wanting to add WebRTC as well, but we could also add what you are talking about - make an issue for it on the github (although it will probably be low priority)

Re: Lovefield – A relational database for web apps

#54
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.

Any data-heavy applications that have significant grouping/filtering/etc.. SQL is very powerful, and when you try to work with large datasets in the browser, its kind of disappointing that you have to either transfer a lot of data on every data view change or do SQL's job with lodash collection methods.

Re: Lovefield – A relational database for web apps

#55
The whole saga is very sad. WebSQL was the right move all along. NoSQL turned out to be a fad and people really just want to use SQL to build real apps. Especially newbies, learning SQL is a lot easier than learning how to reimplement it's features on top of a document store.

Re: Lovefield – A relational database for web apps

#58
post #47

Earlier quoted context omitted.

Disclosure: I'm the author of a competing JavaScript database ( http://gunDB.io/ ). Unfortunately concurrency is typically the last thing that people think about. Concurrency is the first thing we deal with in our database, because you are right, without it data gets corrupted.

So would it be possible to communicate between the two tabs, via the database? In an event-driven way?

Check out intercom on github for inter-tab communication. I use it in we apps for many different things. Including log-back-in. One tab gets a session timeout and tells them all to go black asking for a password. Enter it in one tab and they all unlock.

It uses local storage

Re: Lovefield – A relational database for web apps

#59
post #21

I'm not a web developer, but this looks great, I want to learn how SQL things work, maybe this is a good start for beginner ? BTW, speaker's face is too serious.

I would think you'd want to use a more mature/complete SQL database, with broader documentation and a larger community, to learn about SQL. MySQL or PostgreSQL, would be the obvious free choices. Unless you specifically want to learn about client-side browser-based SQL databases (which is a pretty specific niche of SQL database), in which case this would be interesting, but possibly not extremely relevant to developm…

But a more mature/complete SQL database mostly write in c/c++, and the old design is very complex and hard to change.

Re: Lovefield – A relational database for web apps

#60
post #36

Earlier quoted context omitted.

Also Electron apps. It's currently pretty painful getting sqlite working with Electron, this could be a nice alternative.

Have you tried the emscripten port of SQLite? It's worked well for me... http://github.com/kripken/sql.js

I've tried it, the main problem I have withe it is that the whole DB has to be loaded into memory. It seems like it would be slow and unwieldy with even a moderate sized database. I'm still keeping it open as an option, but I like that Lovefield uses indexedb under the sheets.
Post reply on HN