What if instead of API's for data sets, we simply placed a sqlite file onto a web server as a static asset, so you could just periodically do a GET and have a local copy.
What If OpenDocument Used SQLite?
11–20 of 109 posts
Re: What If OpenDocument Used SQLite?
#12What if instead of API's for data sets, we simply placed a sqlite file onto a web server as a static asset, so you could just periodically do a GET and have a local copy.
Re: What If OpenDocument Used SQLite?
#13wouldn’t an XML database be easier?
*: without adding an index of your own, at which point it isn't really XML anymore, it's some kind of homebrew XML-based archive format.
Re: What If OpenDocument Used SQLite?
#14Re: What If OpenDocument Used SQLite?
#15Re: What If OpenDocument Used SQLite?
#16Recently, DuckDB team raise similar question on DataLake catalog format. Why not just use SQL database for that ? It's simpler and more efficient as well.
Re: What If OpenDocument Used SQLite?
#17What if instead of API's for data sets, we simply placed a sqlite file onto a web server as a static asset, so you could just periodically do a GET and have a local copy.
More industrious people have apparently wrapped this up on NPM: https://www.npmjs.com/package/sqlite-wasm-http
Re: What If OpenDocument Used SQLite?
#18Re: What If OpenDocument Used SQLite?
#19What if instead of API's for data sets, we simply placed a sqlite file onto a web server as a static asset, so you could just periodically do a GET and have a local copy.
A few years ago someone posted a site that showed how to query portions of a SQLite file without having to pull the whole thing down.