Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I had this initial response, but you can have another service running tasks on and in to the database, or more complicated views for interacting with more complex models. PostgREST is just a service for interacting with your data, logic has to be done client side/in another service.


So my server side code will now become a collection of triggers, views etc? That doesn't sound too appealing.


Writing boilerplate to turn rows in to objects is also not appealing. As with many things I suspect there is a valid use case either side.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: