[DBAL-464] Fix dropping primary key with autoincrement column in MySQL #430
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello, thank you for creating this pull request. I have automatically opened an issue http://www.doctrine-project.org/jira/browse/DBAL-682 We use Jira to track the state of pull requests and the versions they got |
|
@doctrine/team-doctrine2 Is there anything that needs to be done here preventing a merge? |
beberlei
added a commit
that referenced
this pull request
Dec 18, 2013
[DBAL-464] Fix dropping primary key with autoincrement column in MySQL
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a table alteration scenario in MySQL, where a primary key is to be dropped that contains an autoincrement column. MySQL requires the autoincrement column attribute to be removed first before dropping the primary key. Otherwise the table alteration will fail.