You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 30, 2018. It is now read-only.
a) One-to-One Unidirectional and Bidirectional mappings are actually a one-to-many however, in the uni-directional version the parent does not have a mapping to the child while in the bi-directional one the parent does
b) One-to-Many is actually a many-to-many mapping which left me all fuzzled up.
c) Many-to-Many - I have not yet got that far
Since I am sure most developers have a database background, the concepts make it difficult to match the association mapping meanings to what the database ones are like.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am a new Doctrine 2 user, but I have found the association mapping documentation (https://github.com/doctrine/orm-documentation/blob/master/en/reference/association-mapping.rst) to be very confusing when compared to relationationla database terminology:
a) One-to-One Unidirectional and Bidirectional mappings are actually a one-to-many however, in the uni-directional version the parent does not have a mapping to the child while in the bi-directional one the parent does
b) One-to-Many is actually a many-to-many mapping which left me all fuzzled up.
c) Many-to-Many - I have not yet got that far
Since I am sure most developers have a database background, the concepts make it difficult to match the association mapping meanings to what the database ones are like.
The text was updated successfully, but these errors were encountered: