migrate
postgres
migrate | postgres | |
---|---|---|
5 | 42 | |
705 | 6,750 | |
2.0% | - | |
8.6 | 8.2 | |
16 days ago | 2 days ago | |
TypeScript | JavaScript | |
MIT License | The Unlicense |
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.
migrate
-
Ask HN: If you were to build a web app today what tech stack would you choose?
- Migration powered by graphile-migrate (https://github.com/graphile/migrate)
-
Intro to PostGraphile V5 (Part 2): Plugins and Presets
Having now built V5's unified plugins and presets system, I'm extremely pleased with it! I'm so happy, in fact, that I'm looking forward to integrating it with Graphile's other tools such as Graphile Worker (our Postgres-backed job queue) and Graphile Migrate (a lightweight SQL-based migration framework that focuses on DX) once V5 is out and stable.
-
How do you manage database structure changes? And deploying code?
Iād highly recommend you use Postgres for the DB and https://github.com/graphile/migrate for the DB migration tool.
-
What is your development stack for 2023?
graphile-migrate - Opinionated SQL-powered productive roll-forward migration tool for PostgreSQL
-
Step by Step OAuth 2.0 Social Login Passport.js?
For version control I use flyway but am considering just dropping it because idk if I will ever need to rollback. Most likely would switch to this if so: https://github.com/graphile/migrate
postgres
-
Neon Is Generally Available: Serverless Postgres
I want to use this as a chance to bring attention to a GitHub issue that I think would help reduce friction for Neon:
https://github.com/neondatabase/neon/issues/4989
If the Neon driver were to allow us to easily pass in a localhost connection, the development and test experience would be easier. Perhaps Neon could swap to something like this internally: https://github.com/porsager/postgres.
Having run a local dev environment connected to Neon and tests connected to Neon got in our way of adoption. We'd prefer to develop and run tests against a regular Postgres localhost database.
To the PMs of Neon, put yourself in the shoes of a new developer thinking of giving Neon a try. What changes will I have to make to my code and my development workflow?
-
Drizzle is just as unready for prime-time as Prisma, what else is there?
I'd push you to consider using postgres, slonik or similar for database queries. With these libraries, you just write SQL, but they perform input sanitization for you. So you can safely write:
- Ask HN: If you were to build a web app today what tech stack would you choose?
-
PostgresJs: The Fastest full featured PostgreSQL client for Node.js and Deno
Thanks Pier! Your comment saved me some frustration here :-D
https://github.com/porsager/postgres/discussions/627#discuss...
-
We migrated to SQL. Our biggest learning? Don't use Prisma ORM
There's a core client interface here:
- https://www.postgresql.org/docs/current/client-interfaces.ht...
On what makes it postgres.js faster, from author himself:
> it seems Postgres.js is actually faster than, not only pg, but of any driver out-there
- https://github.com/porsager/postgres/discussions/627
- https://porsager.github.io/imdbench/sql.html
-
Relational is more than SQL
When viewed as a DSL for set theory, views, CTEs, set-returning functions, et al are indeed proper first-class query abstractions.
When viewed through the lens of general purpose imperative or functional programming languages, it's easy to see how it can be seen as falling short.
I'll admit much of the tooling and driver APIs leave a lot to be desired.
Some tools do make good efforts though such as nested fragments in this driver.
https://github.com/porsager/postgres#building-queries
-
SQLite-based databases on the Postgres protocol? Yes we can
I don't think this should turn in to an ORM or not debate, but there are plenty of reasons, especially for the crowd that would do anything to avoid ORMs. Just try to take a peek into the multitude of "ORMs are bad" articles / discussions.
For instance - I would love to be able to use https://github.com/porsager/postgres with sqlite.
-
Is ORM still an anti-pattern?
Demonstrate how easily and accidentally one can make an SQL injection with these:
https://github.com/porsager/postgres
https://github.com/gajus/slonik
-
Storage on Vercel
They've looked at Postgres.js (https://github.com/porsager/postgres) before ā wouldn't mind if they enabled those other cases in the same way.
What are some alternatives?
fpc_wasm - Free Pascal to WASM demos
pg-promise - PostgreSQL interface for Node.js
Phinx - PHP Database Migrations for Everyone
trpc - š§āāļø Move Fast and Break Nothing. End-to-end typesafe APIs made easy.
yew - Rust / Wasm framework for creating reliable and efficient web applications
slonik - A Node.js PostgreSQL client with runtime and build time type safety, and composable SQL.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
prisma-redis-middleware - Prisma Middleware for caching queries in Redis
bytebase.com - Source for bytebase.com
MySQL - A pure node.js JavaScript Client implementing the MySQL protocol.
lib - Internationalization library built for SvelteKit.
PostgreSQL - PostgreSQL client for node.js.