StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14354901
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-01-16T09:22:22.467
FavoriteCount
0
LastActivityDate
2013-01-16T09:28:16.103
LastEditDate
2013-01-16T09:28:16.103
LastEditorUserId
411632
OwnerUserId
411632
ParentId
14354759
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
In an object-oriented program relations are expressed as associations. That is: <ul> <li>If Product has Orders then Product must have a collection of Orders.</li> <li>If an Order is for a Product, the Order must have a property Product.</li> <li>and so on.</li> </ul> In object-oriented programming you don't associate by an identifier: you don't need this because this is a different world ruled by hierarchical data. Honestly, if you follow what I said before, NHibernate will be a very powerful tool as it'll be able of loading objects and properties without your intervention. Think about "getting all orders of some product": you're not going to intentionally execute an SQL Join but you're going to access to the <code>Orders</code> property of <code>Product</code> and NHibernate will translate this access to the database world. This is the point of using an OR/M. It's not just "I map tables as is". It's about joining two very different worlds: the object-oriented hierarchical world with relational data with no pain. <strike>Check this very old (2004!) CodeProject article and how it creates the Northwind SQL Server database-based model: <ul> <li><a href="http://www.codeproject.com/Articles/8773/NHibernate-in-real-world-applications" rel="nofollow">http://www.codeproject.com/Articles/8773/NHibernate-in-real-world-applications</a></li> </ul> Don't pay attention to how maps the model to the database but to the model design.</strike> Check this article, it's more modern than the other one: <ul> <li><a href="http://litemedia.info/introduction-to-nhibernate" rel="nofollow">http://litemedia.info/introduction-to-nhibernate</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAdvice on database model for ecommerce with custom products
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMatías Fidemraizer
UserOwnerUserId
1. USMatías Fidemraizer
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. COThanks, do you have any advice on the database model for product with differing attributes and how to map these?
 singulars
 PostPostId
 PO
 UserUserId
 USCogslave
2. CO@Alex Maybe, but I believe I should know the environment and what's behind your project in order to take a good decision.
 singulars
 PostPostId
 PO
 UserUserId
 USMatías Fidemraizer

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.