steve-chavez

6 ms·

31.
by steve-chavez 2y ago
The TLDR is that Nginx offers about x2 more throughput than Caddy.
32.
Nginx vs. Caddy Performance [video](youtube.com)
2 points by steve-chavez 2y ago|5 comments
33.
by steve-chavez 2y ago
Transactions are done using database functions https://docs.postgrest.org/en/v12/references/api/functions.h... .
34.
SQL/SE Query Language Extension for Schema Evolution (1992) [pdf](dl.acm.org)
31 points by steve-chavez 2y ago|4 comments
35.
SQL/SE Query Language Extension for Schema Evolution (1992) [pdf](dl.acm.org)
2 points by steve-chavez 2y ago|0 comments
36.
by steve-chavez 2y ago
You have explicit control over transactions with functions https://postgrest.org/en/latest/references/api/functions.htm... . I think this sentiment stems from users of postgrest-js[1], which is a JS libra
37.
by steve-chavez 2y ago
Yes, sorry about that. We're looking at it on https://github.com/PostgREST/postgrest/issues/3503 .
38.
by steve-chavez 2y ago
> * there is no column level security – e.g. I want to show payment_total to admin, but not to user I think what you want is dynamic data masking. RDMBSes like IBM DB2[1] and SQL Server[2] offer it out of the box. For PostgreSQL, there&#
39.
by steve-chavez 2y ago
> This is especially grating since the rest of the tooling seems to try to take me away from SQL a lot by using Postgrest. You're actually encouraged to write SQL with PostgREST, see this other comment https://news.ycombi
40.
by steve-chavez 2y ago
> PostGREST is very very basic and far less powerful than just writing SQL. I found it pretty frustrating to use, knowing that SQL would be far simpler. The PostgREST query grammar is basic on purpose, you're supposed to write SQL o
41.
by steve-chavez 2y ago
> A few things, RLS is secure by default, it's postgrest that's insecure by default. What makes you think that? PostgREST delegates all the authorization to PostgreSQL, which is secure by default. You have to explicitly assign
42.
by steve-chavez 3y ago
Simon Riggs's 2ndQuadrant was one of the first patreons for PostgREST. I'll forever be grateful, their support came in a hard time. Rest in peace Simon.
43.
Postgres Temporal PKs Merged(illuminatedcomputing.com)
1 points by steve-chavez 3y ago|0 comments
44.
by steve-chavez 3y ago
Yes, it's Nix! Supabase already uses Nix on some projects like https://github.com/supabase/nix-postgres/
45.
by steve-chavez 3y ago
Answered that above: https://news.ycombinator.com/item?id=38692597 We've also updated the doc with some manual sanitization[1], but that's definitely not the final form of this POC. [1]: https://postgre
46.
by steve-chavez 3y ago
> Already PostGREST is getting complicated, additions like this will make it less attractive to me. This feature[1] actually simplified a lot and removed a lot of magic assumptions in the PostgREST codebase. It goes in line with REST as
47.
by steve-chavez 3y ago
We segregate responsibilities so no one has complete control of the PostgREST project. For example, begriffs[1] is in charge of handling the funds (Patreon), wolfgangwalther[2] owns the .org and .com domains and both are owners of the Postg
48.
by steve-chavez 3y ago
This doc was meant to be a POC, just to show what's possible. We're working on migrating it to Mustache templates which do automatic escaping: https://github.com/PostgREST/plmustache?tab=readme-ov-file#e... Y
49.
by steve-chavez 3y ago
PostgreSQL has supported XML [1] for a while too. With that, even SOAP endpoints are possible: https://postgrest.org/en/stable/how-tos/create-soap-endpoint... [1]: https://www.postgresql.org/d
50.
by steve-chavez 3y ago
> PostgREST has a scary "allow by default" permission model which is nearly enough to turn me off of the whole project. PostgREST follows Postgres' "deny by default", you have to explicitly grant permissions for
51.
by steve-chavez 3y ago
Really cool! I'm working on something similar https://github.com/PostgREST/plmustache .
52.
by steve-chavez 3y ago
Really interesting project. Thanks for sharing!
53.
Your Infrastructure Should Know More About Your Database (2022)(dbos-project.github.io)
1 points by steve-chavez 3y ago|0 comments
54.
In defense of extreme database-centric architecture [pdf](revistas.um.edu.uy)
3 points by steve-chavez 3y ago|1 comments
55.
In defense of extreme database-centric architecture [pdf](revistas.um.edu.uy)
2 points by steve-chavez 3y ago|0 comments
56.
In defense of extreme database-centric architecture [pdf](revistas.um.edu.uy)
4 points by steve-chavez 3y ago|2 comments
57.
by steve-chavez 3y ago
This is an interesting feature that can be used to disallow login after 3 failed attempts, for example.
58.
Waiting for PostgreSQL 17 – Add support event triggers on authenticated login(depesz.com)
1 points by steve-chavez 3y ago|1 comments
59.
by steve-chavez 3y ago
They do use it: - https://supabase.com/docs/guides/api#rest-api-overview - https://supabase.com/docs/guides/getting-started/architectur...
60.
by steve-chavez 3y ago
Same on Brave, 700% CPU usage before I closed the page.

More ›