migrate
atlas
Our great sponsors
migrate | atlas | |
---|---|---|
72 | 67 | |
13,889 | 4,903 | |
2.6% | 5.6% | |
7.5 | 9.8 | |
3 days ago | 5 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | 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.
migrate
-
Using migrations with Golang
Go does not natively support the use of migrations, but we could use the ORM that has this functionality, such as GORM which is the most used by the community, but We can use migrations without using an ORM, for this we will use the golang-migrate package.
-
How to use SQLC with Golang
$ curl -L https://github.com/golang-migrate/migrate/releases/download/$version/migrate.$os-$arch.tar.gz | tar xvz
- Looking for recommendations for model/schema/migration management in Golang
- API completa em Golang - Parte 1
-
Building RESTful API with Hexagonal Architecture in Go
Golang-migrate is a database migration tool designed for Go applications. It helps manage and apply changes to the database schema as the application grows, ensuring that the code and database structure stay in sync.
-
Python: Just Write SQL
First of all, thank you for SQLAlchemy! If I ever had to make a final choice in how I would interact with a database for a very large project that involves a considerable dev team, I would always bet on SQLAlchemy. Not that I would necessarily like all aspects of it, but when it comes to Python and SQL - “Nobody ever got fired for picking SQLAlchemy.”.
With that out of the way, despite ORMs doing much more than "just writing SQL", it is exactly on that point that I flinch: Most devs should be exposed to SQL. And if your project allows you to build around simple enough abstractions so that you aren't reinventing the wheel, you should definitely be writing SQL. Especially if you don't know SQL yet - which is the growing case of new devs coming into the job market.
You can achieve a lot with SQlAlchemy Core, a tool that I absolutely recommend, but my post is just a simple alternative to get developers to think about their approach. If that results in some devs reconsidering using "full fat" SQLAlchemy and to try SQLAlchemy Core, that's a win for me!
Your gist tries to highlight the difficulty of doing certain things without an ORM. Migrations (as just 1 example) doesn't need to be hard, simple tools like flyway, or migrate (https://github.com/golang-migrate/migrate) achieve a similar result (while also keeping you on the path of writing SQL!). Deep and complex relationships between objects also don't need to be hard - typically people approach this subject with a requirement to be very flexible in the way they want to build queries and objects, but that to me in a sign that maybe they should reconsider their business logic AND reconsider that, just maybe, their project doesn't require all that flexibility, it is fairly straightforward to extend objects and introduce some more complex representations as and when it is needed - will all of this make me write code faster? Absolutely not. That is why you have spent so much time perfecting SQLAlchemy, but then again, I am not advocating for devs to go and replace their usage of ORMs, just presenting an alternative that may or may not fit their needs for a new project + give devs the chance to learn something that the ORM might have taken away.
-
best practices for testing of stored procedure calls?
Doing this now with a mysql db for my use case. Using sp to take a large chunk of data migration load off my data layer code. I am using migrate (go library) for migrations and hooked it up with a bunch of test suites for all SP and Triggers it creates. I test it against a testDB maintained as part of my CI/CD. Haven’t had an issue with production yet. It does however require quite a bit of initial setup.
- Database migration tool
-
REST API with Go, Chi, MySQL and sqlx
Before we can start using MySQL we need to create a table to store our data. I will be using excellent migrate database migrations tool, it can also be imported as a libraray.
-
Authentication system using Golang and Sveltekit - User registration
We need a database table to store our application's users' data. To generate and migrate a schema, we'll use golang migrate. Kindly follow these instructions to install it on your Operating system. To create a pair of migration files (up and down) for our user table, issue the following command in your terminal and at the root of your project:
atlas
-
Pgroll: zero-downtime, undoable, schema migrations for Postgres
Check out: https://github.com/ariga/atlas
(I'm one of the authors of this project).
-
Show HN: Postgres Language Server
fwiw, I personally am interested in this approach too[0]. I keep running into roadblocks around the ordering of events and some of the hairy issues around "destructive" actions (eg: renaming columns). i think we can get there, especially once we make progress with this LSP.
There are other notable mentions in this space:
Reshape: https://fabianlindfors.se/blog/schema-migrations-in-postgres...
Atlas: https://atlasgo.io/
-
Database migration tool
Atlas: https://github.com/ariga/atlas. It can be integrated with any ORM, but also has an official one for GORM: https://atlasgo.io/guides/orms/gorm
-
Queryx: An Open-Source Go ORM with Automatic Schema Management
Run the queryx db:create command to create a PostgreSQL database, and then run queryx db:migrate to automatically create the database migration files and database structure. Queryx’s database schema management is built upon Atlas.
-
Tool for generating automatic migrations/schema diff
One of https://atlasgo.io's creators here.
-
Prisma like PGX Auto migration library
In this case, I'd recommend you to check Atlas: https://github.com/ariga/atlas
-
Quickly visualize your Django schemas with DjangoViz
My name is Rotem, I'm one of the creators of Atlas (https://atlasgo.io) a modern open-source schema management tool. Recently one of our engineers created a cool Django plugin that creates beautiful (in my eyes at least ;-)) and shareable ERDs from your Django data models.
-
Is there a similar tool or alternative in Go like strong_migrations?
Yes, there is: Atlas! https://atlasgo.io / https://github.com/ariga/atlas.
-
How to run DB migrations in CICD
Hi there You should take a look at Atlas - https://atlasgo.io which can help your team in many aspects of CI/ CD for databases : * CI - detect (and prevent) risky / incorrect migrations automatically * CD - support for modern deployment infrastructure (terraform, helm, etc)
-
How do you handle migrations ?
You might want to check out Atlas. It provides automatic migration planning for GORM, and has various guides on how deploying schema migration on the popular platform and tools, such as Helm, Kubernetes and ECS.
What are some alternatives?
goose
datahub - The Metadata Platform for your Data Stack
goose - A database migration tool. Supports SQL migrations and Go functions.
sqlc - Generate type-safe code from SQL
pgx - PostgreSQL driver and toolkit for Go
InfluxDB - Scalable datastore for metrics, events, and real-time analytics
tern - The SQL Fan's Migrator
skeema - Declarative pure-SQL schema management for MySQL and MariaDB
gormigrate - Minimalistic database migration helper for Gorm ORM
pogreb - Embedded key-value store for read-heavy workloads written in Go
sqlx - general purpose extensions to golang's database/sql