News for hackers. Stuff that matters.

A comment on PostgREST. Parent comment

Re:PostgREST by konschubert on Sunday November 03, 2019 @04:51PM (#21436912)
That’s a step in the right direction but I’m not sure if it really solves the problem.

But as I said, there are trade offs. I didn’t say it’s always a bad idea.

[ Parent | on HN ]
Re:PostgREST by felixyz on Sunday November 03, 2019 @05:11PM (#21437069)
I agree there are always trade-offs, but at least as far as "losing a lot of he database performance" and "doing complex joins on your front end", I don't think there is anything in the PostgREST approach that would push in that direction. For more background on the performance part (Oracle-specific but most of it carries over) check out http://www.prohuddle.com/webinars/ToonKoppelaars/ThickDB.php
[ Parent | on HN ]
Re:PostgREST by steve-chavez on Sunday November 10, 2019 @05:29PM (#21500603)
It's amazing that at PostgREST we have reached the same pattern for exposing the API(views + sps).

Thanks a lot for sharing.

[ Parent | on HN ]