Question 1

gormigrate vs golang-migrate for Go database migrations

Accepted Answer

Gormigrate is ideal for simple, code-based migrations integrated with Gorm, offering versioning and rollback, while golang-migrate provides more advanced features, CLI tools, and SQL-based migrations for complex, scalable projects.

Question 2

how to rollback a specific migration in gormigrate

Accepted Answer

Gormigrate handles rollbacks by executing the Rollback function defined in each migration struct, applied in reverse order. For targeted rollbacks, you may need to adjust the migration list or manually invoke rollback logic based on the ID.

Question 3

Does gormigrate support running migrations inside transactions?

Accepted Answer

Yes, Gormigrate includes a UseTransaction option to run migrations inside a single transaction, but note that not all databases support DDL commands in transactions, as mentioned in the options section.

Question 4

Can I use gormigrate with Gorm v1?

Accepted Answer

Yes, Gormigrate supports Gorm v1 via the import path gopkg.in/gormigrate.v1, while Gorm v2 uses github.com/go-gormigrate/gormigrate/v2, as specified in the README compatibility notes.

Question 5

How to handle initial database setup with gormigrate?

Accepted Answer

Use the InitSchema function in Gormigrate to define the entire schema for new databases, which runs automatically if no migrations have been applied, as shown in the example using AutoMigrate and constraints.

Question 6

Is gormigrate safe for production use in distributed systems?

Accepted Answer

Gormigrate lacks built-in locking, so for distributed deployments, you must implement external distributed lock mechanisms to prevent race conditions during migration execution, as advised in the README.

gormigrate

What is gormigrate?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions