3 ms·
Would have been a neat way to experiment around with putting a SQL front end on various KV interfaces. Redis or etcd, for example.
by tyingq 9y ago
Would have been a neat way to experiment around with putting a SQL front end on various KV interfaces. Redis or etcd, for example.
- nerfhammer 9y agoFairly straightforward to make a mysql storage engine for it, e.g. https://github.com/AALEKH/ReEngine https://github.com/AALEKH/ReEngine
- michaelmior 9y agoCockroachDB 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-mapping-table-data-to-key-value-storage/ https://www.cockroachlabs.com/blog/sql-in-cockroachdb-mappin...
- zaarn 9y ago>(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.
- michaelmior 9y agoYes, that note was misleading. Thanks for clarifying :)
- electrum 9y agoPresto has connectors for various types of non-SQL databases including Redis: https://prestodb.io/docs/current/connector/redis.html 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/ 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 https://sqlite.org/vtab.html (and those worked out great for them)