News for hackers. Stuff that matters.
Re:Work on SQLite4 has concluded by tyingq on Tuesday November 07, 2017 @06:22PM (#15648664)
Would have been a neat way to experiment around with putting a SQL front end on various KV interfaces. Redis or etcd, for example.
Re:Work on SQLite4 has concluded by michaelmior on Tuesday November 07, 2017 @07:12PM (#15648973)
CockroachDB has a good blog post[0] that describes how they implemented SQL. (CockroachDB is a key-value store.)

[0] https://www.cockroachlabs.com/blog/sql-in-cockroachdb-mappin...

Re:Work on SQLite4 has concluded by zaarn on Wednesday November 08, 2017 @02:41AM (#15650478)
>(CockroachDB is a key-value store.)

Correction: CockroachDB is based on a KV store, it's a full SQL RDBMS on top of this KV store.

Re:Work on SQLite4 has concluded by michaelmior on Wednesday November 08, 2017 @08:15AM (#15652049)
Yes, that note was misleading. Thanks for clarifying :)
Re:Work on SQLite4 has concluded by electrum on Wednesday November 08, 2017 @01:07AM (#15650215)
Presto has connectors for various types of non-SQL databases including Redis: https://prestodb.io/docs/current/connector/redis.html

Presto is a distributed SQL query engine for big data, so basically the complete opposite of SQLite, though it often gets used in federation scenarios, as does SQLite.

An interesting anecdote is that the team working on what would become osquery (https://osquery.io/) asked if they could reuse the SQL parser from Presto. We get that question a lot, and after explaining that the parser is the easy part (semantic analysis and execution is the real work), I determined that what they really wanted were SQLite virtual tables: https://sqlite.org/vtab.html (and those worked out great for them)

Re:Work on SQLite4 has concluded by nerfhammer on Tuesday November 07, 2017 @06:29PM (#15648714)
Fairly straightforward to make a mysql storage engine for it, e.g. https://github.com/AALEKH/ReEngine