StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6421241
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-06-21T06:29:57.813
FavoriteCount
0
LastActivityDate
2011-06-22T15:51:03.467
LastEditDate
2011-06-22T15:51:03.467
LastEditorUserId
117625
OwnerUserId
117625
ParentId
6416891
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
We use <code>partial</code> implementations frequently but I don't find it to be code smell. In fact, I think it is a lot better than wrapping them with more code. At that point, you might as well skip RIA and write your own WCF change tracker... but I digress. If you want a rich domain model, then <code>partial</code> implementations are one great way to accomplish that. The default code generator creates partial methods for the most meaningful points in a WCF RIA entity's life cycle. By implementing these partials, you move away from the <a href="http://martinfowler.com/bliki/tags/domain%20driven%20design.html" rel="nofollow">Anemic Domain Model</a>. As you stated above, you can implement an interface and create your own methods and properties. IOW you are not limited to implementing the <code>partial</code> stubs. If all else fails, <a href="http://jeffhandley.com/archive/2010/10/28/RiaServicesT4WalkUp.aspx" rel="nofollow">modify the default code generator</a> to your liking. I did to remove <code>sealed</code> from every entity to make testing easier. UPDATE: Here is my code to remove <code>sealed</code> <pre><code>[DomainServiceClientCodeGenerator(typeof (CustomClientCodeGenerator), "C#")] public class CustomClientCodeGenerator : CSharpClientCodeGenerator { private EntityGenerator _entityGenerator; protected override EntityGenerator EntityGenerator { get { return _entityGenerator ?? (_entityGenerator = new CustomEntityGenerator()); } } private class CustomEntityGenerator : CSharpEntityGenerator { public override string TransformText() { return base.TransformText().Replace("sealed ", string.Empty); } } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORIA Services extending code-generated entity model partial classes
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USEd Chapel
UserOwnerUserId
1. USEd Chapel
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORIA Services extending code-generated entity model partial classes
 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.