doctrine/archived-orm
1
0
Fork 0
mirror of https://github.com/doctrine/orm.git synced 2026-03-24 06:52:09 +01:00
Code Issues 5.3k Packages Projects Releases 100 Wiki Activity

DDC-576: New entities must have primary key values right after flushing with IDENTITY strategy #706

New Issue
Closed
opened 2026-01-22 12:47:34 +01:00 by admin · 2 comments
admin commented 2026-01-22 12:47:34 +01:00
Owner
Copy Link

Originally created by @doctrinebot on GitHub (May 7, 2010).

Jira issue originally created by user drevolution:

After insertion of some new entity the primary key must be set. Example code is attached above.

Originally created by @doctrinebot on GitHub (May 7, 2010). Jira issue originally created by user drevolution: After insertion of some new entity the primary key must be set. Example code is attached above.
admin added the Bug label 2026-01-22 12:47:34 +01:00
admin closed this issue 2026-01-22 12:47:34 +01:00
admin commented 2026-01-22 12:47:36 +01:00
Author
Owner
Copy Link

@doctrinebot commented on GitHub (May 7, 2010):

Comment created by romanb:

I think I reproduced this already. Seems to be related to PostgreSQL + IDENTITY only. The SequenceIdentityGenerator must be used but apparently it is not used.

Thanks for the report. Will keep you updated.

ps. The standalone reproduce scripts are good. Thanks for that! If you are interested it would be even better if the test code would be provided as a unit test or with some additional comments and/or assertions about what the desired behavior is or where the supposedly wrong behavior is (even if it is very obvious, like in this issue).

@doctrinebot commented on GitHub (May 7, 2010): Comment created by romanb: I think I reproduced this already. Seems to be related to PostgreSQL + IDENTITY only. The SequenceIdentityGenerator must be used but apparently it is not used. Thanks for the report. Will keep you updated. ps. The standalone reproduce scripts are good. Thanks for that! If you are interested it would be even better if the test code would be provided as a unit test or with some additional comments and/or assertions about what the desired behavior is or where the supposedly wrong behavior is (even if it is very obvious, like in this issue).
admin commented 2026-01-22 12:47:36 +01:00
Author
Owner
Copy Link

@doctrinebot commented on GitHub (May 8, 2010):

Issue was closed with resolution "Fixed"

@doctrinebot commented on GitHub (May 8, 2010): Issue was closed with resolution "Fixed"
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BC Break
Bug
Can't Fix
Deprecation
Documentation
DQL
Duplicate
Failing Test
Hacktoberfest
Improvement
Improvement
Incomplete
Invalid
Missing Tests
New Feature
PR Created
pull-request
Mirrored from GitHub Pull Request
 Question
Regression
Status: Waiting feedback
Waiting feedback
WIP
Won't Fix
No Label Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#706
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?