-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Production ready Database migration management (Make AutoMigrate production suitable) #5807
Comments
Go migrate works well, no need to add this functionality here. But i miss a diff cmd which would generate sql migration scripts so much. |
I'm developing an app that currently uses Gorm as Postgres Orm. We are expected to deliver production ready code in January. How do you currently work around this issue with Gorm? Do you use it's Migrator interfaces? Would be extremely appreciative of some example projects using Gorm in production. |
Gorm has an ORM is production ready for sure. Its auto-migrate isn't suitable for production environments has you tend to want to have move control over your database migration in a production setting, so you might need to use a different tool that lets you manage database migrations separately. (https://github.com/alob-mtc/migrator) is a tool I’m developing to address this. |
Describe the feature
Example use of User-APIs
Creating Migrations
Running Migrations
Rolling Back Migrations
Example implementation in a stand-alone lib here (https://github.com/alob-mtc/migrator), but I am of the opinion that if gorm adopts this internally will be nice
Motivation
Related Issues
The text was updated successfully, but these errors were encountered: