StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18961717
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-09-23T14:21:51.933
FavoriteCount
0
LastActivityDate
2013-09-23T14:29:16.147
LastEditDate
2013-09-23T14:29:16.147
LastEditorUserId
363004
OwnerUserId
363004
ParentId
18961412
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You only need to specify a <code>mappedBy</code> attribute when there is a bidirectional relationship to determine which side is the owning side. From the docs: <a href="http://docs.doctrine-project.org/en/2.0.x/reference/association-mapping.html#owning-side-and-inverse-side" rel="nofollow">http://docs.doctrine-project.org/en/2.0.x/reference/association-mapping.html#owning-side-and-inverse-side</a> <blockquote> <ul> <li>A bidirectional relationship has both an owning side and an inverse side.</li> <li>A unidirectional relationship only has an owning side.</li> <li>The owning side of a relationship determines the updates to the relationship in the database.</li> </ul> ... The following rules apply to bidirectional associations: The inverse side of a bidirectional relationship must refer to its owning side by use of the mappedBy attribute of the OneToOne, OneToMany, or ManyToMany mapping declaration. The mappedBy attribute designates the field in the entity that is the owner of the relationship. </blockquote> In your case you only have unidirectional relationship which means you don't have to specify <code>mappedBy</code>, you may be able to leave it out. <hr> Or you can add supplier to the Address class: <pre><code>/** * @ManyToOne(targetEntity="Supplier", inversedBy="addresses") */ private $supplier; </code></pre> which then allows you to set <code>mappedBy="supplier"</code> in <code>Supplier.php</code> <pre><code>/** * @OneToMany(targetEntity="Address", mappedBy="supplier", cascade={"persist", "remove"}) */ private $addresses; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMultiple ManyToOne relationships in Doctrine
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJonathan
UserOwnerUserId
1. USJonathan
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMultiple ManyToOne relationships in Doctrine
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COI think the latter part of your answer will work, I was just half way through implementing it. I was trying to avoid this extra column, but I guess that would leave duplicate foreign keys in there, so looks like its going to be required.
 singulars
 PostPostId
 PO
 UserUserId
 USJackalopeZero

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.