Issues: golang-migrate/migrate
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Allow golang-migrate to continue even if it can't find the current version
#1091
opened May 21, 2024 by
SJrX
Do not return an error when no change. Communicate error conditions using errors.
#1063
opened Mar 23, 2024 by
atljoseph
SQLite3 accepts file URL with prefix
file:///
, but golang-migrate requires prefix sqlite3:///
. Not flexible.
#1062
opened Mar 23, 2024 by
atljoseph
Dirty database version 1. Fix and force version
and error: can't read limit argument N
#1059
opened Mar 20, 2024 by
ctfrancia
Expensive SQL query inside ensureVersionTable & ensureLockTable
#1052
opened Mar 13, 2024 by
deepakd10
Allow users to fail when there are bad migration paths in their source
#1048
opened Mar 9, 2024 by
dnisenbaum1
"unexpected EOF" when connecting to MySQL DB via cloud-sql-proxy in github actions
#1040
opened Feb 21, 2024 by
pidgezero-one
Migrations that begin with the year 2024 fail during the 'up' migration process
duplicate
This issue or pull request already exists
#1024
opened Jan 3, 2024 by
alazarbeyenenew2
Actualize/improve documentation about installation process (go toolchain)
#1020
opened Dec 31, 2023 by
evassilyev
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.