Fix ID generation for Doctrine ORM 3 on PostgreSQL#479
Merged
maltehuebner merged 1 commit intomainfrom Mar 4, 2026
Merged
Conversation
Doctrine ORM 3 changed AUTO strategy from SEQUENCE to IDENTITY for PostgreSQL. Since the existing database uses sequences (data_id_seq, station_id_seq, etc.), explicitly set SEQUENCE strategy with the correct sequence names to prevent null ID inserts. Co-Authored-By: Claude Opus 4.6 <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
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
AUTOstrategy fromSEQUENCEtoIDENTITYfor PostgreSQLdata_id_seq,station_id_seq, etc.)SEQUENCEstrategy with correct sequence names on all 4 entitiesnull value in column "id" violates not-null constraintwhen inserting data via APITest plan
luft:fetchcommand successfully persists new data values🤖 Generated with Claude Code