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

Attributes in annotations to specify Constraint, Index (etc.) name. #6215

New Issue
Closed
opened 2026-01-22 15:29:02 +01:00 by admin · 1 comment
admin commented 2026-01-22 15:29:02 +01:00
Owner
Copy Link

Originally created by @ancpru on GitHub (Apr 3, 2019).

Originally assigned to: @Ocramius on GitHub.

Feature Request

Q A
New Feature yes
RFC yes/no
BC Break no

Summary

Doctrine automatically generates the names of the constraints/indexes for @OneToMany, @ManyToMany, They are sometimes a bit cryptic when working on the DB. It would be
nice to have an attribute like "constraintName" in the definition.

In general I think that it would be nice to have more db-schema hints in order to make automatic schema generation easier and more straight forward.

For example, cascading (update, delete) might not make sense for ORM, but it can be useful to let the DB take care of it.

Originally created by @ancpru on GitHub (Apr 3, 2019). Originally assigned to: @Ocramius on GitHub. ### Feature Request <!-- Fill in the relevant information below to help triage your issue. --> | Q | A |------------ | ------ | New Feature | yes | RFC | yes/no | BC Break | no #### Summary Doctrine automatically generates the names of the constraints/indexes for @OneToMany, @ManyToMany, They are sometimes a bit cryptic when working on the DB. It would be nice to have an attribute like "constraintName" in the definition. In general I think that it would be nice to have more db-schema hints in order to make automatic schema generation easier and more straight forward. For example, cascading (update, delete) might not make sense for ORM, but it can be useful to let the DB take care of it. <!-- Provide a summary of the feature you would like to see implemented. -->
admin added the New FeatureWon't Fix labels 2026-01-22 15:29:02 +01:00
admin closed this issue 2026-01-22 15:29:02 +01:00
admin commented 2026-01-22 15:29:03 +01:00
Author
Owner
Copy Link

@Ocramius commented on GitHub (Apr 3, 2019):

ON UPDATE cascade operations are something that will not be re-introduced in ORM. See also https://github.com/doctrine/orm/issues/7574#issuecomment-479335970

Please use a migration tool with custom-written migrations for customising constraint names and cascade operations that are not supported by the ORM. Closing as duplicate of #3753

@Ocramius commented on GitHub (Apr 3, 2019): `ON UPDATE` cascade operations are something that will not be re-introduced in ORM. See also https://github.com/doctrine/orm/issues/7574#issuecomment-479335970 Please use a migration tool with custom-written migrations for customising constraint names and cascade operations that are not supported by the ORM. Closing as duplicate of #3753
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 New Feature Won't Fix
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#6215
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?