Stark-DB: SQLite-backed, change-tracking database available over HTTP
1–10 of 10 posts
Re: Stark-DB: SQLite-backed, change-tracking database available over HTTP
#2Doesn't this lose the primary latency benefit of Sqlite by introducing a network connection?
Re: Stark-DB: SQLite-backed, change-tracking database available over HTTP
#3Interesting that they chose to use port 5984, which is also the same port that CouchDB uses, but their API is completely different from the CouchDB API.
Re: Stark-DB: SQLite-backed, change-tracking database available over HTTP
#4Doesn't this lose the primary latency benefit of Sqlite by introducing a network connection?
I wanted to comment exactly the same. This loses the advantage of SQLite, make it slower and more cumbersome to operate. You can simply do this with a library.
Re: Stark-DB: SQLite-backed, change-tracking database available over HTTP
#5Re: Stark-DB: SQLite-backed, change-tracking database available over HTTP
#6Re: Stark-DB: SQLite-backed, change-tracking database available over HTTP
#7I'd only fallback to "changes" when I don't know the "intentions".
Re: Stark-DB: SQLite-backed, change-tracking database available over HTTP
#8What is the intended use case?
Re: Stark-DB: SQLite-backed, change-tracking database available over HTTP
#9Doesn't this lose the primary latency benefit of Sqlite by introducing a network connection?
Lemme try and defend without fully understanding or use:
Say you have a local sqlite database and want to share it.
Wouldn't this allow such an extension?
Re: Stark-DB: SQLite-backed, change-tracking database available over HTTP
#10What is the intended use case?
To get VC funding?