node-pg-migrate
postgres-meta
Our great sponsors
node-pg-migrate | postgres-meta | |
---|---|---|
4 | 2 | |
1,229 | 823 | |
1.7% | 3.6% | |
9.4 | 0.0 | |
2 days ago | 3 days ago | |
TypeScript | TypeScript | |
MIT License | Apache License 2.0 |
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.
node-pg-migrate
-
Fully featured Repository Pattern with Typescript and native PostgreSQL driver
Why PG? For the clarity of the article to a large circle of developers, the entire explanation will be built by PostgreSQL and PG package. And in a real project, the database schema will change over time, and in order to be able to perform migrations, we will use Node PG migrate.
-
New to PostgreSQL - Best way to use it?
b) How you will manage schema migrations: every time you change tables, columns, foreign keys, every time you create or modify stored procedures, and so on, you need to do this through a migration. Here I'm at loss to recommend anything specific, but if you went with Prisma, I would read their docs and use whatever they are recommending you (if they actually recommend something). If you want something more neutral but still in the node ecosystem, node-pg-migrate might be the winner here? I'm not sure.
-
Postgres: What is the development process?
You’ll probably want something like this too: https://github.com/salsita/node-pg-migrate
-
The Architecture of a One-Man SaaS
You can use any normal DB migration tool. For k8s, I put the app's readiness probe to false, run the migrations and then toggle the probe back to true.
Here are some migration libraries:
Go - https://github.com/golang-migrate/migrate
Node - https://github.com/salsita/node-pg-migrate
postgres-meta
-
Supabase Needs Column Level Security
What grinds my gears it that someone actually started this process with a simple pull request: ADD CRUD permissions. Someone from Supabase said, "sure, no problem, we will work on this next week"... and nope, nothing. Then the PR was randomly closed yesterday! Why? No idea, no explanation. Granted, this was a simple PR and they could be rethinking an easier way to do this. But I digress.
-
Week 4 notes
I picked the first issue, which was a bug in the Supabase dashboard, where users could not edit a database column from a primary type to its array type. The dashboard was built with Nextjs and TailwindCSS, using the Supabase-UI components libraries. It looked like was a quick fix to me. After investigation, the error was not with the dashboard but it was an error of insufficient type handling of column type identifiers within the Posgres-Meta package, which was also written by Supabase Team. Then, I headed to the package upstream and fixed it. The PR got merged and released soon after.
What are some alternatives?
sql-lint - An SQL linter
knex-types - Generate TypeScript definitions (types) from a PostgreSQL database schema.
graphjin - GraphJin - Build NodeJS / GO APIs in 5 minutes not weeks
supabase - The open source Firebase alternative.
logpaste - A simple web service for storing text log files
ElectroCRUD - Database CRUD Application Built on Electron | MySQL, Postgres, SQLite
prawn-stack - A pageview counter using the AWS free tier, Postgres, Node and React
flan - A tasty tool that lets you save, load and share postgres snapshots with ease
migrate - Database migrations. CLI and Golang library.
kubernetes-the-hard-way - Bootstrap Kubernetes the hard way. No scripts.
diagrams - :art: Diagram as Code for prototyping cloud system architectures
blog - OpenSource,Database,Business,Minds. git clone --depth 1 https://github.com/digoal/blog