Hacker News Reader

It fell through because everyone choose SQLite as the implementation, and having one implementation means it's quirks would be enshrined as the standard.

Really speaks to SQLite's quality that major vendors would just reach for it without considering making their own.

Browsers: yes

https://github.com/sql-js/sql.js

It's a sqlite browser port which doesn't persist data. I think that's kind of essential for a database.

Sure it does! You can `POST` the buffer that backs the database to your favorite blob store, and read it back when you're done. You can write to it as much as you like when the page is active.

So every time somebody loads up your website, you read a text blob, initialize a new database and populate it?

https://sqlite.org/about.html

"Think of SQLite not as a replacement for Oracle but as a replacement for fopen()"

You can actually partially persist data on the client side in SQLite, as you can embed the data in you html, which is exactly what we do with our product

There was an attempt to add SQLite to browsers at some point, but it was abandoned because we would never get two independent implementations.

https://www.w3.org/TR/webdatabase/

Reply on news.ycombinator.com