Don't generate DEFAULT 0 clause for AUTO_INCREMENT columns
#1980
Conversation
This file contains hidden or 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
lauxjpn
added a commit
to lauxjpn/Pomelo.EntityFrameworkCore.MySql
that referenced
this pull request
Mar 3, 2025
…umns. (PomeloFoundation#1980) (cherry picked from commit 23db204)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR #1844 introduced a regression bug that can generate invalid SQL (a
DEFAULT 0clause for anAUTO_INCREMENTcolumn).We now make sure that we don't generate default values of any kind, when generating column definition SQL for an
AUTO_INCREMENTcolumn.This fix will be backported to
8.0.Fixes #1914