-
Notifications
You must be signed in to change notification settings - Fork 71
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
Always use a schema for expressing the schema version table #18
Comments
That would be an unfortunate occurrence. Changing the type of |
I've just pushed |
Another option to more fully guard against that situation would be to inspect the database and see if there is already a version table in a different schema. .... Actually, wait a second. In your original scenario, in step 3 the original .... That's the problem... So I guess it might be fair to add a check to ... Okay. Just released |
With the currently unprefixed
schema_version
table the following sequence of events is possible.tern
run createsschema_version
inpublic
tern
now createsschema_version
in$user
tern
now attempts to re-apply migrations from 0, potentially causing havocSimply specifying
versionTable: "public.schema_version"
solves this. Using apgx.Identifier
forversionTable
intype Migrator
will encourage people to do this.The text was updated successfully, but these errors were encountered: