[DDC-2089] Modify OneToMany to allow unidirectional associations without the need of a JoinTable Created: 19/Oct/12 Updated: 05/Jun/15
|Project:||Doctrine 2 - ORM|
|Reporter:||Enea Bette||Assignee:||Benjamin Eberlei|
|Labels:||onetomany, persister, unidirectional|
Debian Wheezy, Mysql 5.1, Apache2, PHP 5.4
As I sayd in the title, it would be nice if the ORM layer could permit to map a 1:n association in the db as an unidirectional OneToMany in the classes, without using a JoinTable in the database.
Is it possible?
|Comment by Enea Bette [ 16/Dec/12 ]|
A little up... for inspiration from JPA
|Comment by Daniel Pitts [ 07/Oct/14 ]|
This is also a big issue for Symfony2 forms. It's very difficult to make a form type for a collection of "things", where the "things" are fully owned by the parent object.
|Comment by Florian Vogelpohl [ 05/Jun/15 ]|
There are any plans to implement this feature?
E.g.: If you have an entity Account which holds a collectionof Members (unidirectional) and now you want to remove a Member from the collection you get an "Cannot delete or update a parent row: a foreign key constraint fails " error ...