mirror of
https://github.com/doctrine/orm.git
synced 2026-03-23 22:42:18 +01:00
DDC-2414: Unable to create One-To-Many relation with composite keys #3029
Reference in New Issue
Block a user
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?
Originally created by @doctrinebot on GitHub (Apr 25, 2013).
Originally assigned to: @beberlei on GitHub.
Jira issue originally created by user jedi_bc:
Given these entities :
I want to link users and groups but only from the same domain.
I also want a user to be in one group only.
The only way with composite keys is to make
One-To-Many, Unidirectional with Join Tablebut I can't putunique=truein the@JoinColumnof myinverseJoinColumnsbecause it will generate a unique index for each field and not one composite. I also can't use@UniqueConstraintas it is not supported in@JoinTable.@doctrinebot commented on GitHub (Apr 28, 2013):
Comment created by @FabioBatSilva:
Hi Bruno,
Could you please explain it a little deeper ?
you describe an one-to-many relation but your mapping has a many-to-many Group#users.
Also, you shoud describe operations you are executing and which errors you got.
Cheers
@doctrinebot commented on GitHub (Apr 29, 2013):
Comment created by jedi_bc:
Hi fabio,
The relation i was trying to make is http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/association-mapping.html#one-to-many-unidirectional-with-join-table
However, it implies to use a unique contraint and as explain above when trying to create the schema via doctrine, as i use composite keys, it will generate 2 unique contraints (one for each field) and not one composite unique constraint.
Nevertheless, it seems like using composite keys is a lot buggy in doctrine (see http://www.doctrine-project.org/jira/browse/DDC-2413)
@doctrinebot commented on GitHub (May 1, 2013):
Comment created by @beberlei:
We discussed this in DDC-2413, this is not supported by Doctrine.
@doctrinebot commented on GitHub (May 1, 2013):
Issue was closed with resolution "Invalid"