StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6476997
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-06-25T09:32:41.503
FavoriteCount
0
LastActivityDate
2011-06-25T09:32:41.503
LastEditDate
LastEditorUserId
0
OwnerUserId
82062
ParentId
6455138
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> Repository Coordination? </blockquote> Aggregate roots should draw transactional boundaries. Therefore - multiple repositories should rarely be involved. If they are - that usually happens when You are creating new aggregate root (as opposed to modifying its state). <hr> <blockquote> Business Logic that Involves Repositories? </blockquote> Yes, checking if username is distinct might live in service layer. Because User usually is an aggregate root and aggregate roots live in global context (there is nothing that "holds" them). I personally put that kind of logic in repository or just check directly through ORM. As for checking password usage - that's a concern of user itself and should live underneath User object. Something like this: <pre><code>class User{ void Login(){ LoggedOn=DateTime.Now; ... } bool HasLoggedInLast90Days(){ return (DateTime.Now-LoggedOn).Days<=90; } } </code></pre> <hr> <blockquote> Business Logic that Involves Multiple Entities? </blockquote> Aggregate root should manage their entity collections. <pre><code>class Customer{ void OrderProduct(Product product){ Orders.Add(new Order(product)); //<-- } } </code></pre> But remember that aggregate root should not micro-control its entities. E.g. this is bad: <pre><code>class Customer{ void IsOrderOverdue(Order order){ return Orders.First(o=>o==order)....==...; } } </code></pre> Instead use: <pre><code>class Order{ void IsOverdue(){ return ...; } } </code></pre> <hr> <blockquote> Mapping? </blockquote> I suppose mapping to dto`s live in service layer. My mapping classes lives next to view model classes in web project.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat types of code are appropriate for the service layer?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USArnis Lapsa
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhat types of code are appropriate for the service layer?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.