StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14666609
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-02T21:16:39.213
FavoriteCount
0
LastActivityDate
2013-02-02T21:38:17.710
LastEditDate
2013-02-02T21:38:17.710
LastEditorUserId
1193333
OwnerUserId
1193333
ParentId
14666142
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The first case is good for simplicity. If you extend your model you will have to do changes on less places. It is not less secure. You can bypass creating or binding the hidden input fields by several ways. Use <code>BindAttribute</code> to bypass binding of property: <pre><code>ActionResult Create([Bind(Exclude = "RootCategoryId")] SubCategoryHelper thisSubCategory) {//....} </code></pre> Or <code>ScaffoldColumnAttribute</code> on the model class property (e.g. when you use edit templates): <pre><code>[ScaffoldColumn(false)] public int RootCategoryId {get; set;} </code></pre> Or just simple do not expose it (as you did in your example using the <code>Html.HiddenInput</code> helper). <hr> The second approach, you have described, is often called ViewModel pattern. It encourages seperation of your Presentation and Domain layer. The advantage is, that your domain model will not be polluted with presentation layer specific code (like various display attributes etc.). Hovewer it brings another overhead of mapping between domain models and view models. There is probably no genarel rule of thumb. It depends on type of your appliction. If it is basically some simple data driven CRUD application, you can easily stay with the first one. Nevertheless, when your application becomes larger, you will definetly appreciate the freedom of your hands on separate layers. And if your BLL code is used with some other kind of "client" (web service, desktop etc.) except the ASP MVC I would defintely go with the second option. I also suggest to read this great article: <a href="http://blog.ploeh.dk/2012/02/09/IsLayeringWorthTheMapping.aspx" rel="nofollow">Is layering worth mapping</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat Is The Best Practice To Deal With MVC Post Models?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmipe34
UserOwnerUserId
1. USmipe34
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhat Is The Best Practice To Deal With MVC Post Models?
 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
 VTAcceptedByOriginator
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.