sql-file
dbmate
sql-file | dbmate | |
---|---|---|
2 | 25 | |
1 | 4,391 | |
- | - | |
7.0 | 8.1 | |
4 months ago | 9 days ago | |
Clojure | Go | |
Apache License 2.0 | 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.
sql-file
-
Screw DSLs. Write migrations using plain SQL
Several years ago, I wrote something similar for Clojure, as part of a way to make it super simple to put a SQL database behind a Clojure all. Essential goal was for close to single jar file deployment.
https://github.com/mschaef/sql-file
Doesn’t get a lot of use aside from a few small things I use it for, but has been nice to have around.
(This was before I knew of Flyway…. These days I might just link to that for the migration part.)
-
Ask HN: Do you Self-host your database?
For personal stuff, I tend to keep it about as simple as possible with an HSQLDB instance hosted in-process. (All JVM/Clojure)
I use a small library that encapsulates the use-case (including some schema migration stuff that should probably be replaced with flyway).
https://github.com/mschaef/sql-file
There's a lot that can be said about this approach, both for and against, but I find that it brings a lot of power, is easy to set up, and generally stays out of the way. Given that the fundamental abstraction presented to user code is essentially SQL with connection pooling, there are also good escape strategies to get to architectures that would support however much capacity I'm ever likely to need.
dbmate
-
Ask HN: What tool(s) do you use to code review and deploy SQL scripts?
A regular code repo with the scripts (with pull/merge requests for review) and then a CI job that builds containers with something like dbmate https://github.com/amacneil/dbmate that can then be run against any staging/prod environment.
-
Level UP your RDBMS Productivity in GO
As we want to maintain the track of our changes to the DB, we are going to use migrations. In this case, we are going to use dbmate. But, you can use any other tool you want.
-
Rails 7.1 Released
> For example having database migrations built in etc.
I actually went the exact opposite route, at least when possible: https://github.com/amacneil/dbmate
Pure SQL migrations, regardless of the back end technology that you use, completely decoupled from how each framework/library views things and therefore not dependent on them (you could even rewrite the back end in another technology later on, if needed; or swap ORMs; or avoid issues when there's a major ORM version update).
It's really nice when you can generate entity mappings based on a live database, like with https://blog.jetbrains.com/dotnet/2022/01/31/entity-framewor...
So in my case, I can have:
* a DB that has migrations applied with dbmate, completely decoupled from any back end(s) that might use it
- FLaNK Stack Weekly 2 October 2023
-
How do your teams run DB migrations?
You can run dbmate as part of your CI/CD pipeline. You just keep a dbmate directory in your repo and deploy migrations with your code.
-
Working with TypeORM 0.3x with Nestjs - I wasn't aware so many people were facing issues with it
In general with ORMs, you will face a problem in one way or another. I ended up simply using https://github.com/gajus/slonik and https://github.com/amacneil/dbmate for migrations. My life is way much better since then.
-
what do you use for migrations? or how do you the sql tables and seeding?
I like dbmate, super simple and straightforward to use. For your specific use case, it can also be configured using your .env!
- GORM
-
New post: Is Prisma better than your 'traditional' ORM?
Would always go for a language agnostic migration tool, e.g. https://github.com/amacneil/dbmate to stay flexible and stay away from lock-in effects (besides sql).
- I greatly dislike ORMs, but I find myself wanting ORM agnostic SQL migration tools. What do you use to perform RDBMS table migrations outside of an ORM?
What are some alternatives?
docker-sqitch-pgtap - Run sqitch and pgTAP for PostgreSQL without installing them from docker
sqlite-bench - PostgreSQL & SQLite Speed Test
pgmigrate
goose - A database migration tool. Supports SQL migrations and Go functions.
Flyway - Flyway by Redgate • Database Migrations Made Easy.
liquibase - Main Liquibase Source
migra - Like diff but for PostgreSQL schemas
SQLBoiler - Generate a Go ORM tailored to your database schema.
golang-samples - Sample apps and code written for Google Cloud in the Go programming language.
bytebase - The GitHub/GitLab for database DevOps. World's most advanced database DevOps and CI/CD for Developer, DBA and Platform Engineering teams.
tbls - tbls is a CI-Friendly tool for document a database, written in Go.
pv-migrate - CLI tool to easily migrate Kubernetes persistent volumes