3 ms·
No 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
by jbverschoor 5y ago
No 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).