3 ms·
This is a great idea, I love it. Perhaps it would be a good idea to offer exports in the form of .sql files that can be loaded into any database, a la 'curl api
by orf 12y ago
This is a great idea, I love it. Perhaps it would be a good idea to offer exports in the form of .sql files that can be loaded into any database, a la 'curl api.stripe.com/export... | psql'. I'm sure the export would be bigger than a binary sqlite file but it would remove the dependency on sqlite.
- masklinn 12y agoThat's somewhat limiting though, you need to export in the subset of SQL (DDL and queries) compatible to all databases and it is very small indeed (I hope you don't have any textual content of more than 8000 bytes encoded). But if what you want is to load the data into sqlite, chances are you can just export the sqlite content and load it into Postgres directly, since Richard Hipp (and the SQLite team) more or less consider Postgres to be the reference implementation of SQL: https://twitter.com/dchest/status/469597738431434752 https://twitter.com/dchest/status/469597738431434752
- bane 12y agoSome of the SQLite utilities let you dump the tables out of the SQLite file as CSV or .sql if you want. It would probably be easier if dB vendors just made a SQLite importer/exporter that turned any given SQLite file into a full database in their RBDM and visa-versa (or for some subset). It's not really that hard of a problem to do it and seems like a better way than shuffling around csv files or .sql files. At least then if you want to probe the files a little to see what's in them without loading them up you can just use one of the dozen or so SQLite utilities that are out there. The hardest part might be type inference on schemas that don't define the attribute types (SQLite ignores those and so they're optional) and converting over the full-text indexing and other extensions. But it's not exactly rocket science.