StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
609911
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-03-04T09:51:11.097
FavoriteCount
0
LastActivityDate
2009-03-04T09:51:11.097
LastEditDate
LastEditorUserId
0
OwnerUserId
66392
ParentId
609881
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<p>Following the DDD let's separate your entities from the logic that operates on them. Personally, I have used Repository pattern to create one generic repository as well as some specialized repositories that operate on my entities. The reposotory can operate on constructor-given ObjectContext or will create a new one (from configuration) when none is specified.</p> <p>My example IRepository interface:</p> <pre><code>public interface IRepository<T> where T : class { /// <summary> /// Return all instances of type T. /// </summary> /// <returns></returns> IQueryable<T> All(); /// <summary> /// Return all instances of type T that match the expression exp. /// </summary> /// <param name="exp"></param> /// <returns></returns> IEnumerable<T> Find(Func<T, bool> exp); /// <summary>Returns the single entity matching the expression. /// Throws an exception if there is not exactly one such entity.</summary> /// <param name="exp"></param><returns></returns> T Single(Func<T, bool> exp); /// <summary>Returns the first element satisfying the condition.</summary> /// <param name="exp"></param><returns></returns> T First(Func<T, bool> exp); /// <summary> /// Mark an entity to be deleted when the context is saved. /// </summary> /// <param name="entity"></param> void Delete(T entity); /// <summary> /// Create a new instance of type T. /// </summary> /// <returns></returns> T CreateInstance(); /// <summary>Persist the data context.</summary> void SaveAll(); } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEntity constructors - Entity framework
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStwk
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. 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
  VTUpMod
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.