Forward autoincrement property from field to column#674
Merged
collerek merged 9 commits intoApr 20, 2026
ormar-orm:masterormar-orm/ormar:masterfrom
smuething:fix_autoincrement_columnssmuething/ormar:fix_autoincrement_columnsCopy head branch name to clipboard
Merged
Forward autoincrement property from field to column#674collerek merged 9 commits intoormar-orm:masterormar-orm/ormar:masterfrom smuething:fix_autoincrement_columnssmuething/ormar:fix_autoincrement_columnsCopy head branch name to clipboard
collerek merged 9 commits into
ormar-orm:masterormar-orm/ormar:masterfrom
smuething:fix_autoincrement_columnssmuething/ormar:fix_autoincrement_columnsCopy head branch name to clipboard
Conversation
The autoincrement property of ormar fields did not get propagated to the SQLAlchemy column definition. As a result, the autoincrement property of the SQLAlchemy column defaulted to `auto`, making it impossible to create DDL that did not auto-increment the database column.
…utoincrement_columns
CodSpeed Performance ReportMerging #674 will not alter performanceComparing Summary
|
Verifies that autoincrement=False on an Integer primary key field is forwarded to the underlying SQLAlchemy column.
Aligns the fmt target with master's tooling so contributors do not need black installed locally.
collerek
approved these changes
Apr 20, 2026
collerek
added a commit
that referenced
this pull request
Apr 22, 2026
Bump version and add release notes for 0.24.0. Features: - on_update field option (#1273) - fk_name override on ForeignKey (#849) - forward autoincrement to SQLAlchemy column (#674) Fixes: - run standalone queries under AUTOCOMMIT isolation, restoring 0.21-era per-row CRUD performance (#1629, #1635) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
2 participants
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.
The autoincrement property of ormar fields does not get propagated to the SQLAlchemy column definition. As a result, the autoincrement property of the SQLAlchemy column defaults to
auto, making it impossible to create DDL that does not auto-increment the database column.With this small patch, it becomes possible to create a table with a manually managed, integer-based PK.