Logger
pgpkg
| Logger | pgpkg | |
|---|---|---|
| 1 | 3 | |
| 303 | 18 | |
| 1.3% | - | |
| 10.0 | 6.6 | |
| about 3 years ago | 28 days ago | |
| PLSQL | Go | |
| MIT License | 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.
Logger
-
We built our customer data warehouse all on Postgres
Deployment: Upgrade SQL scripts. You already have to do this on any relational DB if you need to alter existing tables. We just also deploy new/updated packages. We trigger them via pipelines.
Also keep in mind that the logic you deploy in the database is generally not as complex as other software as you mostly just query, modify and write highly structured data.
But we still run plenty of tests. There is a great unit testing tool for Oracle: utPLSQL [1]. We also spin up databases and run the installation and upgrade scripts on pull-requests.
[0] https://github.com/OraOpenSource/Logger
pgpkg
-
My Notes on Gitlab's Postgres Schema Design (2022)
You are absolutely correct; my previous business ended up ejecting almost all database logic from Java ORMs, and moved almost everything to SQL and stored procedures. Doing so resulted in a significant performance and productivity increase, relative to all the layers of nonsense we used to jump through.
One of the difficulties of doing this was that the tooling isn’t great. We had to write our own tools to make it work, but the benefits of going back to SQL were more than worth it.
(Many years later I made an open source version of that tooling, https://github.com/pgpkg/pgpkg)
-
We built our customer data warehouse all on Postgres
I wrote something [0]. It lets you write plpgsql functions, views, triggers and casts in a way that can be re-created without migration scripts. It’s a complete work in progress, not production ready, probably has bugs, but I use it daily. It lets me use Postgres as my main development environment.
It also managea migrations for tables, types, and other stuff, if fully atomic, and lets you write unit tests in SQL (which run inside save points so they don’t affect the database and can run during production deployments). It’s sort of my Swiss Army knife of plpgsql development.
[0] https://github.com/pgpkg/pgpkg
-
Ask HN: What web frameworks do you use?
I use static Svelte(Kit) + TypeScript + Tailwind on the front end, Go and Postgraphile in the middle, and PostgreSQL functions on the backend.
I did write my own PostgreSQL migration tool though, to make it easier to write SQL functions in my IDE: https://github.com/pgpkg/pgpkg
What are some alternatives?
revenut-app - A web + mobile app (PWA) with Stripe integration for forecasting SaaS revenue