StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PONHibernate mapping message logic
primarykey
Id
7436572
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-09-15T19:43:16.267
FavoriteCount
0
LastActivityDate
2011-09-15T20:16:15.427
LastEditDate
LastEditorUserId
0
OwnerUserId
761244
ParentId
0
PostTypeId
1
Score
0
ViewCount
45
LastEditorDisplayName
text
Body
I made some classes that represents my messages logic: <ul> <li>Message - representation of THE message :)</li> <li>MessageBoxBase - base class for all 3 kind of messagebox</li> <li>MessageInbox - representing inbox</li> <li>MessageOutbox - representing outbox</li> <li>MessageCustombox - user defined message box</li> <li>MessageBoxItem - message item in any messagebox with such data as IsReaded etc.</li> <li>MessageBoxCollection - Collection of messageboxes - Inbox, Outbox and List of CustomBoxes - only that 3 properties.</li> </ul> Finally in my agregate root User have MessageboxCollection, and I can use it somewhat like that: <pre><code>myUser.MessageBoxes.Inbox.Add(...) myUser.MessageBoxes.Outbox.Items.... </code></pre> <img src="https://i.stack.imgur.com/fLMEi.png" alt="Diagram of that classes"> I dont have any DB structure right now and I'm open on sugestion, but I was thinking about something like that: <ul> <li>MessageInInbox - UserId,MessageId, IsReaded etc.</li> <li>MessageInOutBox - Same as in Inbox</li> <li>MessageInCustomBox - UserId,MessageId, CustomBoxId and so on</li> <li>CustomBox - BoxId, UserId, BoxName etc.</li> <li>Message - plain message row, subject, content, author etc.</li> </ul> One I'm sure is that I don't want to create in DB row for each Inbox/Outbox for each user like it is in CustomBox case (something like unnecessary dictionary for inboxes and outboxes per user). And in that point I have a problem - how the hell to map that ? :) Have any suggestions? Maybe my domain is crappy? I'm waiting for yours response :)
Tags
<nhibernate><nhibernate-mapping>
Title
NHibernate mapping message logic
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmgibas
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
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.