StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7590359
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-09-28T22:22:51.673
FavoriteCount
0
LastActivityDate
2011-09-28T22:22:51.673
LastEditDate
LastEditorUserId
0
OwnerUserId
343266
ParentId
7588795
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Let's ask different question: what if your application should present categories in tree-view control, which upon expanding category node will list all products? When you want to display all products there's no other way than ... actually querying database and loading all products. That's actually pretty common real-life scenario and one of easiest approaches is indeed to simply have <code>Category.Products</code> property. Of course there's nothing wrong with having such property, but the real question is how you should manage those objects. Luckily, you don't have to pull all the products with single category pull. <code>Category.Products</code> can be marked to load lazily (as opposed to eagerly, more information can be found <a href="http://nhforge.org/wikis/howtonh/lazy-loading-eager-loading.aspx" rel="nofollow">here</a>). What this means is, loading category won't query database for its products. Instead, NHibernate will create <a href="http://en.wikipedia.org/wiki/Proxy_pattern" rel="nofollow">proxy</a> object for <code>Products</code>, which can be initialized later - when they are actually needed (think user expanding category node). <hr> And to answer your question... If single product is bound to exactly one category, then it's good real-life one-to-many relation example. However, if product can be described by more than one category, it's many-to-many relation then.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOne to many mapping. NHibernate
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USk.m
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.