StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5371136
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-03-20T20:04:27.907
FavoriteCount
0
LastActivityDate
2011-03-21T12:17:14.907
LastEditDate
2011-03-21T12:17:14.907
LastEditorUserId
1228
OwnerUserId
1228
ParentId
5371032
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Yes. The WPF binding system will use a <a href="http://msdn.microsoft.com/en-us/library/system.componentmodel.customtypedescriptor.aspx" rel="nofollow">custom type descriptor</a> to interact with the properties of your ViewModel at runtime. I've used this before to make keys in a KeyValueCollection<T> appear as properties on the collection. This has two important benefits. It simplifies binding: <code>DataContext.SomeCollectionProperty[SomeKey]</code> can be simplified to <code>DataContext.SomeCollectionProperty.SomeKey</code> and, if you make a custom type descriptor for the data context, <code>DataContext.SomeKey</code> which is about as simple as it gets. And it fixes what I consider a bug--format strings are rendered even when the property is null. Using a CTD, you can skip null (and DBNull) properties, ensuring that format strings won't be rendered if the property doesn't exist: Imagine you have a <code>double?</code> that you must render as a dollar amount. If you use the following binding: <code>{Binding Price, FormatString='Price: {0:c}'}</code> and the Price is null, you get the following in your UI: <code>Price: $</code>. This is ugly. However, if <code>Price</code> is a PropertyDescriptor-based property on your UI, when the Price is null, you can opt to not to report this property via your CTD. This prevents the format string from being rendered at all. Here's a pretty good link at MSDN about <a href="http://msdn.microsoft.com/en-us/library/ms171819.aspx" rel="nofollow">decorating your types with a CTD</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POStructural design pattern for MVVM View Model?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USWill
UserOwnerUserId
1. USWill
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POStructural design pattern for MVVM View Model?
 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. COI've used this technique before it is a good alternative if you don't have dynamics available to you.
 singulars
 PostPostId
 PO
 UserUserId
 USMichael Brown

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.