-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Unable to change delimiter in mysql migrations #1036
Comments
As a workaround, I found that you can add
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
In MySQL migrations, it is typical to set the value of the delimiter to a different value than
;
when creating a stored procedure. The official docs even recommend doing this.However, when trying to use such a migration with
migrate
, it results in an error:Other delimiters likewise fail (tested with
//
andFOOBAR
).Steps to Reproduce
Steps to reproduce the behavior:
Expected Behavior
migrate
should run the migration correctly with no errors.Migrate Version
4.17.0
Loaded Source Drivers
go-bindata, file, github, github-ee, godoc-vfs, s3, gcs, gitlab, bitbucket
Loaded Database Drivers
clickhouse, cockroach, crdb-postgres, yugabyte, ysql, neo4j, stub, firebird, cassandra, mysql, redshift, yugabytedb, sqlserver, pgx, pgx4, postgresql, mongodb+srv, spanner, firebirdsql, pgx5, cockroachdb, postgres, rqlite, mongodb
Go Version
n/a
Stacktrace
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: