StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2388135
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-03-05T16:11:42.713
FavoriteCount
0
LastActivityDate
2010-03-05T16:33:20.230
LastEditDate
2010-03-05T16:33:20.230
LastEditorUserId
286958
OwnerUserId
286958
ParentId
2378867
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I have had a case like yours. I had Configuration class which can be either Global Configuration, Project Specific Configuration, or User Specific Configuration. What I did was this: <ol> <li>I map the Parent like I normally would in any case to all possible parents (except global, it means applied to all so no parents)</li> </ol> <blockquote> <pre><code>< class name="ConfigurationDomain" table="configuration"> < property name="ProjectId" column="project_id" type="int" insert="false" update="false" /> < property name="UserId" column="user_id" type="int" insert="false" update="false" /> < many-to-one name="Project" column="project_id" lazy="false" /> < many-to-one name="User" column="estimator_id" lazy="false" /> < /class> </code></pre> </blockquote> <ol start="2"> <li>I map the configuration as collection in every possible parents</li> </ol> <blockquote> <pre><code>< class name="UserDomain" table="user"> < set name="ConfigurationList" lazy="true" cascade="all-delete-orphan"> < key column="user_id" /> < one-to-many class="ConfigurationDomain" /> < /set> < /class> < class name="ProjectDomain" table="user"> < set name="ConfigurationList" lazy="true" cascade="all-delete-orphan"> < key column="project_id" /> < one-to-many class="ConfigurationDomain" /> < /set> < /class> </code></pre> </blockquote> Just like that and it worked for me. How do I access configuration of, say, a user with id 55 is this: I don't use someUser.ConfigurationList since it's slow. I only map the parent so that I can do this in HQL (it's much faster): <pre><code>select c from ConfigurationDomain c where c.UserId=55 </code></pre> And to get Global Configuration I would do this: <pre><code>select c from ConfigurationDomain c where (c.UserId IS NULL) and (c.ProjectId IS NULL) </code></pre> On reflection, I think you can even remove the collection mapping if you decide to use HQL. NOTE: I've used Criteria in my early days with NHibernate, but then I found HQL is somewhat more powerful for me, other might have different opinion in this.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONHibernate entity loose coupling
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJaya Wijaya
UserOwnerUserId
1. USJaya Wijaya
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.