steve-chavez

10 ms·

91.
by steve-chavez 5y ago
> The whole idea of the API layer is to be able to make changes to your internals without breaking all your consumers. You can do so by not exposing tables and instead use views and stored functions/procedures. See https:/&#x2
92.
by steve-chavez 5y ago
> What would be nice is a way to mandate that queries must go through certain indices. Yes, this is an interesting idea. We're kinda gravitating towards this approach in PostgREST lately. For example, on a recent discussion about in
93.
by steve-chavez 5y ago
Many thanks! Also want to mention that I could not do the work without the help of the PostgREST Team[1] :) [1]: https://github.com/orgs/PostgREST/people
94.
by steve-chavez 5y ago
There are python clients available[1]. For example with postgrest-py[2] you can do: async with PostgrestClient("http://<yourhost>.com") as client: r = await client.from_("countries").select(
95.
by steve-chavez 5y ago
If your identity-service can generate a JWT, then you can integrate your auth with PostgREST. There's a related example with Auth0[1] in the docs. [1]: https://postgrest.org/en/v9.0/auth.html#jwt-from-auth0
96.
by steve-chavez 5y ago
That's not true. For example, in PostgREST we setup a nix-shell[1] that allows us to run tests in different PostgreSQL versions(from 9.6 to 14). [1]: https://github.com/PostgREST/postgrest/tree/main/
97.
by steve-chavez 5y ago
Not yet AFAICT. I've been following the nix-processmgmt[1] project, which looks it could make NixOS independent of the init system. [1]: https://github.com/svanderburg/nix-processmgmt
98.
by steve-chavez 5y ago
Could yo elaborate on why you don't use PostGIS? I've always assumed its C algorithms are high-performance.
99.
by steve-chavez 5y ago
> I wonder if this works with yugabyte It should work too! Check this line here[1]. That shows that Yugabyte also has the `ProcessUtility_hook`(same one used in the article) defined. It would be a matter of installing and loading the Sup
100.
by steve-chavez 5y ago
You mean event triggers[1] right? For the problem mentioned in the blog post — protecting roles — it's not possible to use event triggers because PostgreSQL doesn't fire[2] a DDL event for `CREATE/ALTER/DROP ROLE`. If an
101.
Protecting reserved roles with PostgreSQL Hooks(supabase.io)
100 points by steve-chavez 5y ago|15 comments
102.
A tale of making company-wide standard psqlrc(depesz.com)
2 points by steve-chavez 5y ago|0 comments
103.
The Hard Quadrant(momjian.us)
1 points by steve-chavez 5y ago|0 comments
104.
by steve-chavez 5y ago
Hey @pschetelat. I've opened a Jobs Board[1] on PostgREST GitHub discussions. If you'd like you could also post the job offer there. [1]: https://github.com/PostgREST/postgrest/discussions/categorie.
105.
by steve-chavez 5y ago
SQL is turing complete. A demonstration with recursive CTEs is done here[1]. [1]: https://wiki.postgresql.org/wiki/Cyclic_Tag_System
106.
by steve-chavez 5y ago
> why isn't someone rolling those tables into something a bit easier with some backend process. To put it in more concrete terms(plain SQL): the tables could be aggregated on a set returning function or a view.
107.
Practical SQL for Data Analysis(hakibenita.com)
602 points by steve-chavez 5y ago|191 comments
108.
by steve-chavez 5y ago
There seems to be a continued fraction for pi[1] as well: pi = 3 + (1^2)/6 + (3^2)/6 + (5^2)/6 + (7^2)/6 + (9^2)/6 + (11^2)/6 + ... [1]: https://www.maa.org/sites/default/files&
109.
by steve-chavez 5y ago
You can abstract at the DB layer with views + stored procedures[1]. [1]: https://postgrest.org/en/stable/schema_structure.html#schema...
110.
by steve-chavez 6y ago
> Too bad they were not invented until SQL-89, and could thus not be considered when the JOIN syntax we all know was designed and formalized by ANSI in SQL-86. TIL! > After renaming the foreign keys The idea about using FK as a JOIN t
111.
by steve-chavez 6y ago
> We use open source to build our software (hey nothing special here : bazillion companies do that) That's not true. Supabase improves and builds the open source ecosystem it uses. In the case of PostgREST, we've added performa
112.
Pg_service.conf: The Forgotten PostgreSQL Config File(2016)(cybertec-postgresql.com)
2 points by steve-chavez 6y ago|0 comments
113.
PgAdmin Moving from Backbone.js to ReactJS(enterprisedb.com)
3 points by steve-chavez 6y ago|0 comments
114.
by steve-chavez 6y ago
Cool! I remember seeing a pg TOTP implementation in this gist[1] before. Seems this extension was based off that? [1]: https://gist.github.com/bwbroersma/676d0de32263ed554584ab132...
115.
by steve-chavez 6y ago
IO at the edges also gives your program the Functional core, imperative shell [1] design by default. [1]: https://www.destroyallsoftware.com/screencasts/catalog/funct...
116.
by steve-chavez 6y ago
Yes! We leverage PostgreSQL Policies[1], which give you the same flexibility(more actually) as Firebase security rules. [1]: https://supabase.io/docs/guides/auth#policies
117.
by steve-chavez 6y ago
Here's an OSS project that makes heavy use of plpython3u: https://github.com/Delibrium/delibrium-postgrest/blob/master...
118.
by steve-chavez 6y ago
Supabase team member here. Multi-tenant is already possible with PostgreSQL RLS policies[1]. We provide a nice UI[2] to make them simpler to use. [1]: https://www.postgresql.org/docs/current/ddl-rowsecurity.html [
119.
by steve-chavez 6y ago
If you like serverless, Supabase[1] will handle all the PostgreSQL and PostgREST management for you :) [1]: https://supabase.io/beta
120.
Stored Procedures as a Back End(gnuhost.medium.com)
209 points by steve-chavez 6y ago|192 comments

More ›