Fix hardcoded INTEGER for autoincrement primary keys (#88)#89
Open
Fix hardcoded INTEGER for autoincrement primary keys (#88)#89
Conversation
Use the column's compiled type instead of a hardcoded INTEGER when emitting GENERATED BY DEFAULT AS IDENTITY, so that BigInteger and SmallInteger primary keys produce BIGINT/SMALLINT IDENTITY columns.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
INTEGERfor autoincrement primary keys, soBigInteger/SmallIntegerprimary keys were emitted asINTEGER GENERATED BY DEFAULT AS IDENTITY.BIGINTandSMALLINTIDENTITY columns are now emitted correctly (Firebird supports identity onSMALLINT,INTEGER,BIGINT).test_compiler.pycovering all three integer types.Test plan
BIGINT GENERATED BY DEFAULT AS IDENTITY.ruff checkandruff format --checkpass on the touched files.