News for hackers. Stuff that matters.
Re:PostgREST by bayesian_horse on Monday November 04, 2019 @07:22AM (#21440940)
I would expect authorization and validation to be a real pain with PostgREST (I don't know enough about it to tell definitively, though).

Even row-level access control, while not widespread any way, is often not enough. Complex validation in SQL can be done, of course, but SQL isn't exactly meant for these things, IMHO.

Re:PostgREST by ako on Tuesday November 05, 2019 @03:05AM (#21450527)
This is an interesting read on validation in postgres: https://begriffs.com/posts/2017-10-21-sql-domain-integrity.h...
Re:PostgREST by ako on Monday November 04, 2019 @12:56PM (#21444298)
Stored procedures often offer a better and more efficient way to implement data validation than non database native alternatives.
Re:PostgREST by bayesian_horse on Wednesday November 06, 2019 @02:17AM (#21460401)
It may indeed be efficient.

Maybe I just don't like the idea of putting all my application logic into SQL statements.

What I like about Django's ORM, for example, that you can declare a field to be an IP address, and this not only does the validation (which SQL can do easily, I am sure), but this declaration also carries over to HTML forms, admin interface, REST API serialization and HTML Templates.

Re:PostgREST by ruslan_talpa on Monday November 04, 2019 @09:44AM (#21442068)
why would you "expect" that if you don't know about it?
Re:PostgREST by bayesian_horse on Wednesday November 06, 2019 @02:20AM (#21460414)
I know more than basic SQL. Maybe I am indeed not an accomplished enough master in SQL, but I can't see why I would ever prefer SQL over Python in terms of defining application logic.