StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9931670
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-29T18:56:59.443
FavoriteCount
0
LastActivityDate
2012-03-29T18:56:59.443
LastEditDate
LastEditorUserId
0
OwnerUserId
651789
ParentId
9931323
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
In my experience, <code>Model</code> objects don't have to (and probably shouldn't) know that they are being constructed in a <code>View</code>. Often, <code>Model</code> objects are entities that should never be allowed to be in an invalid state. <code>ViewModel</code> objects are the things that construct the <code>Model</code> objects. So, since you never want to create a person who is very old or very young, and every person needs a name, your <code>Person</code> class might look like this: <pre><code>public class Person { public int Age { get; private set; } public string Name { get; private set; } public Person(int age, string name) { if (age < 0 || age > 150) throw new ArgumentOutOfRangeException(); if (string.IsNullOrEmpty(name)) throw new ArgumentNullException(); Age = age; Name = name; } } </code></pre> And your <code>PersonViewModel</code> might look like this:: <pre><code>class PersonViewModel : INotifyPropertyChanged { private int _Age; private int _Name; public int Age { get { return _Age; } set { if (_Age.Equals(value)) return; _Age = value; RaisePropertyChanged("Age"); } } public string Name { get { return _Name; } set { if (_Name.Equals(value)) return; _Name = value; RaisePropertyChanged("Name"); } } public Person CreatePerson() { return new Person(_Age, _Name); } } </code></pre> You can then put whatever values you want in your <code>PersonViewModel</code> without worrying about creating an invalid <code>Person</code> object. You can also implement validation in the <code>PersonViewModel</code> that may be more strict than the validation in the <code>Person</code> class (for example, restricting the age range to adults over 18 years old (see <a href="http://msdn.microsoft.com/en-us/library/system.componentmodel.idataerrorinfo.aspx" rel="nofollow">IDataErrorInfo</a>)).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGet notified when properties change in the Model
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USken
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. 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.