StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHibernate unidirectional one to many association - why is a join table better?
primarykey
Id
1307203
data
AcceptedAnswerId
1307218
AnswerCount
2
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-08-20T16:03:32.657
FavoriteCount
14
LastActivityDate
2011-02-15T17:03:44.613
LastEditDate
LastEditorUserId
0
OwnerUserId
143351
ParentId
0
PostTypeId
1
Score
32
ViewCount
25481
LastEditorDisplayName
text
Body
In this document (scroll down to the Unidirectional section): <a href="http://docs.jboss.org/hibernate/stable/annotations/reference/en/html_single/#entity-mapping-association-collections" rel="noreferrer">http://docs.jboss.org/hibernate/stable/annotations/reference/en/html_single/#entity-mapping-association-collections</a> it says that a unidirectional one-to-many association with a join table is much preferred to just using a foreign key column in the owned entity. My question is, why is it much preferred?
Tags
<hibernate><one-to-many><foreign-keys><associations>
Title
Hibernate unidirectional one to many association - why is a join table better?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USUrLicht
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTDuplicate
3. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHibernate unidirectional one to many association - why is a join table better?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POHibernate unidirectional one to many association - why is a join table better?
 UserUserId
 USrichever
 VoteTypeVoteTypeId
 VTFavorite
3. VO
 singulars
 PostPostId
 POHibernate unidirectional one to many association - why is a join table better?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COsee http://stackoverflow.com/questions/2092611/why-is-it-recommended-to-avoid-unidirectional-one-to-many-association-on-a-forei
 singulars
 PostPostId
 POHibernate unidirectional one to many association - why is a join table better?
 UserUserId
 USAdrien Be

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.