bugzino
pgress
bugzino | pgress | |
---|---|---|
1 | 3 | |
12 | 2 | |
- | - | |
2.2 | 0.0 | |
about 1 year ago | about 1 year ago | |
Kotlin | TypeScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bugzino
-
The Database Package Manager for PostgreSQL Trusted Language Extensions
At KotlinConf today I gave a talk on designing apps with two-tier architecture, where you implement your entire app without the web stack appearing anywhere at all. Instead you publish desktop and mobile apps that connect directly to an RDBMS like PostgreSQL via its native protocol, and use server extensions for any logic that is inconvenient to do with SQL.
This approach might seem horrifyingly outside-the-box but has a lot of advantages, and some of the reasons we didn't do things this way historically have been solved in recent years.
Because it was KotlinConf the demo uses PL/Java, which is pretty nice because there's such a healthy ecosystem of stuff based around JDBC and because deploying JVM stuff doesn't require any sort of cross-compilation. PL/Java also supports (for now) trusted extensions using sandboxing, although of course the sandbox can just get in the way and normally you trust your own server anyway so this is a double edged sword.
The demo code can be found here (it's a prototype and nobody reviewed it yet so be gentle)
https://github.com/hydraulic-software/bugzino
I'll write up a blog post version of the talk, but for now I had to mention that DBaaS providers don't actually enable this sort of design because they like to wall off the full power of the RDBMS behind custom APIs. But in two-tier design you really lean into the database and use all of its features. So, it'd be nice if:
a. database.dev were to support PL/Java extensions.
b. Supabase were to allow direct connections, as the native DB protocol supports a lot of features that otherwise have to be sort of hacked on top of HTTP. Ultimately, HTTP is designed to fetch hypertext whereas the PG native protocol is designed to work with data, and that difference shines through in a bunch of ways.
pgress
-
Show HN: Open-source, browser-local data exploration using DuckDB-WASM and PRQL
Hey Marco, I'll take a look - filters theoretically should be fast, when you create a new filter, it simply reads does a `select * from table limit 1` to get column names
I wasn't sure whether you could query DBs directly from the browser but looks like you can! (https://github.com/alexanderguy/pgress) - will add it to roadmap!
-
The Database Package Manager for PostgreSQL Trusted Language Extensions
I had fun with a similar concept: just access the database from the browser using nginx/TLS/lua: https://github.com/alexanderguy/pgress
If you're good with your authenticated users directly talking to the DB (which there are plenty of uses for), it's a great way to get your data into the browser.
- Don’t we all just want to use SQL on the front end?
What are some alternatives?
supavisor - A cloud-native, multi-tenant Postgres connection pooler.
storage-foundation-api-explainer - Explainer showcasing a new web storage API, NativeIO
pg_tle - Framework for building trusted language extensions for PostgreSQL
mingo - MongoDB query language for in-memory objects
set_user - PostgreSQL extension allowing privilege escalation with enhanced logging and control
mongo-parse - A parser for mongo db queries and projections.
HashQL-todos-sample
postgraphile-plugin-conn
omnigres - Postgres as a Platform
postgraphile-plugin-connection-filter - Filtering on PostGraphile connections