3 ms·

http://postgrest.org/en/v6.0/api.html#horizontal-filtering-rows http://postgrest.org/en/v6.0/api.html#horizontal-filtering-r... But I still prefer Hasura Graph

http://postgrest.org/en/v6.0/api.html#horizontal-filtering-rows http://postgrest.org/en/v6.0/api.html#horizontal-filtering-r... But I still prefer Hasura GraphQL on top of Postgres

CapriciousCptl 7y ago
I used Postgrest with React for a few projects awhile back. It was... okay. The problem is without having much of an ecosystem around it means there’s no established best practices and you have to kind of guess how to organize things. I ended up with a jumbled mess of SQL functions that never really jived. Maybe I didn’t give it the shot it deserved but Rails feels incredibly simpler.
taffer 7y ago
I would argue that a Postgrest API is conceptually closer to GraphQL than to SQL.
- deleted 7y ago
  [deleted]
- steve-chavez 7y ago
  PostgREST can look closer to SQL. For example this query: select time, device_id, humidity from conditions where humidity > 90 and time < '2016-11-16' order by time desc limit 10; Can be expressed as this request: curl -G "/conditions" \ -d select=time,device_id,humidity \ -d humidity=gt.90 \ -d time=lt.2016-11-16 \ -d order=time.desc \ -d limit=10 In long form without curl: /conditions?select=time,device_id,humidity&humidity=gt.90&time=lt.2016-11-16&order=time.desc&limit=10 Taken from: http://postgrest.org/en/v5.2/integrations/timescaledb.html#postgrest-on-hypertables http://postgrest.org/en/v5.2/integrations/timescaledb.html#p....