4 ms·
I thought about making something using SQLite virtual tables to back all of the data on FDB in order to basically provide a SQL interface with FDB without writi
by endisneigh 4y ago
I thought about making something using SQLite virtual tables to back all of the data on FDB in order to basically provide a SQL interface with FDB without writing a new layer, but some others tried and apparently didn't go well since you can't have indexes using virtual tables. Truly a shame.
Any other storage engines that support using another interface as the underlying store?
- alexchamberlain 4y agoPostgres Foreign Data Wrappers?
- snissn 4y agoYeah was gonna suggest this! I’m not the biggest expert but you can put Postgres in front of all your data sources and have pg route the queries through a heterogeneous infrastructure and get a nice interface
- richieartoul 4y agoYeah that would be cool. You could try forking an existing “SQL over key value” system like Cockroach or TiDB and replacing the KV store with FoundationDB. That is probably what I would explore first. Some of my old colleagues/friends are working on building a transactional document store (among other things) on top of FoundationDB, so if you can forgo SQL that’s another project you could explore working on: https://github.com/tigrisdata/tigris https://github.com/tigrisdata/tigris
- zitterbewegung 4y agoFoundationDB uses SQLite as the storage layer unless you mean to access the storage layer in FoundationDB to perform that task?
- endisneigh 4y agoyes, access through storage layer through FDB using a SQL interface. aka SQL interface with FDB guarantees.
- ddorian43 4y agoYugabytedb has integrated Postgresql and its open source.