migration
Package migration for Golang automatically handles versioning of a database schema by applying a series of migrations supplied by the client.
by BurntSushiGo
Meet the team
See all 1 on GitHub →
Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
42
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent fixes
Let's say we have 10 replicas of stateless service talking to database that we need to update (and that update includes new migration), and we start updating them by batches of 2 for example. Do I understand it correctly that this should still work, because schema update is transactional, so only the transaction that committed first would be actually committed, and second would fail without any ill effects except that db "wrapped connection" itself would fail and need to be recreated? Or there are some other gotchas with that approach? Also, did you consider adding: either retry logic in case of failed commit or using explicit database lock and if not, then why? So I guess answer to question in title is "yes", but I'd like to have a better confidence that my understanding is correct )
Structured data for AI agents
Repository: BurntSushi/migration. Description: Package migration for Golang automatically handles versioning of a database schema by applying a series of migrations supplied by the client. Stars: 76, Forks: 5. Primary language: Go. Languages: Go (100%). License: Unlicense. Open PRs: 0, open issues: 0. Last activity: 12y ago. Community health: 42%. Top contributors: BurntSushi.