3 ms·
This is just sql in json, I prefer mapping SQL semantics onto HTTP semantics like postgrest does. Not aware of any project that does that for sqlite.
by SahAssar 5y ago
This is just sql in json, I prefer mapping SQL semantics onto HTTP semantics like postgrest does. Not aware of any project that does that for sqlite.
- hobo_mark 5y agoWhat does that look like?
- SahAssar 5y agoSee here: https://postgrest.org/en/stable/api.html https://postgrest.org/en/stable/api.html
- RedShift1 5y agohttps://github.com/bradleyboy/tuql https://github.com/bradleyboy/tuql converts an sqlite database to a GraphQL API
- taway1982345 5y agoIn a short time i'll release exactly that, postgrest semantics backed by sqlite :)
- jbverschoor 5y agoNo batches there. And only simple queries... > For more complicated filters you will have to create a new view in the database, or use a stored procedure
- SahAssar 5y agoYou can do bulk/batch inserts, and because of the single request = single query behavior you can much more easily cache responses. It's a tradeoff, but ws4sqlite just sees HTTP as a tunnel for SQL-in-json while postgrest tries to represent SQL in REST. Which you prefer is a matter of taste.
- mano78 5y ago(author) Yes, it's a tradeoff. ws4sqlite was meant to give an unstructured way to access sqlite, that cannot be accessed on the net; while I see PostgREST (a wonderful product that I also use) as a way to implement persistence for a model you already have in your application. They're not "direct competitors", as I see it, and PostgREST is much more ambitious (and complex, arguably).