mirror of
https://github.com/doctrine/orm.git
synced 2026-03-23 22:42:18 +01:00
DDC-443: Adding a Many-To-One Unidirectional mapping to help clarify Association Mapping documentation #555
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 (Mar 18, 2010).
Originally assigned to: @jwage on GitHub.
Jira issue originally created by user grekker:
For one-to-one unidirectional and many-to-many unidirectional flipping the owning and inverse sides is fairly intuitive.
However, the example given for One-To-Many Unidirectional does not lend itself to being flipped around (since you use a @ManyToMany for a One-To-Many unidirectional, and a @ManyToOne for a Many-To-One unidirectional).
Yes, you can figure out what you are supposed to do by looking at the One-To-Many Bidirectional and tweaking it, but I think it should be more obvious than that.
I suggest at a minimum adding an example of Many-To-One for at least unidirectional (or perhaps a note under One-To-Many suggesting how to do the inverse), but you can add bidirectional and self-referencing for consistency if you think that will be better understood.
Probably the note is the best way to go about it; it gets the point across without potentially confusing people by having One-To-Many and Many-To-One as if they were fundamentally different things.
@doctrinebot commented on GitHub (Apr 30, 2010):
Issue was closed with resolution "Fixed"