Skip to content

Drop the old schema_migrations table #708

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

Merged

Conversation

carols10cents
Copy link
Member

We haven't been using this since we switched to diesel;
__diesel_schema_migrations manages this now. We left this around just
in case we needed to roll back the switch to diesel in production, but
we're good and switched now.

The existence checks are so that these migrations won't error if people
are starting from a database that either does or does not have a
schema_migrations table.

We haven't been using this since we switched to diesel;
`__diesel_schema_migrations` manages this now. We left this around just
in case we needed to roll back the switch to diesel in production, but
we're good and switched now.

The existence checks are so that these migrations won't error if people
are starting from a database that either does or does not have a
schema_migrations table.
@carols10cents carols10cents requested a review from alexcrichton May 2, 2017 18:18
@alexcrichton alexcrichton merged commit 69cfe72 into rust-lang:master May 2, 2017
@carols10cents carols10cents deleted the drop-old-schema-migrations-table branch May 2, 2017 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants