Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Validation errors directly stemming from user actions on your model (e.g. too short a password)<br> is at home as close to the model as possible.</p> <p>General error messages of the "no data found" kind are easier addressed through having a dedicated Error View of some sort.</p> <p><hr/> <b>Added:</b> </p> <p>If I understand you correct, you prefer to stick with one view; be it validation gold or burning SQL servers ;-)</p> <p>Not madly MVC2 experienced mysef, but being consistent and always create own models, never what you might be served by what(not) ORM you're using (Linq&lt;->SQL, EF) should give you the fine-graininess you need. </p> <p>If my memory serves me correct I think the <a href="http://nerddinner.codeplex.com/SourceControl/changeset/view/52406" rel="nofollow noreferrer">Nerddinner</a> could be enlightening; and if you really<br> want to take the plunge, why don't go <a href="http://www.digitallycreated.net/Blog/54/deep-inside-asp.net-mvc-2-model-metadata-and-validation" rel="nofollow noreferrer">Deep Inside ASP.NET MVC 2 Model Metadata and Validation</a></p> <p><hr/> I've gotten my MVC mainly from books, but the blogosphere has definitely started producing golden material on the more "foreign" parts of ASP.NET MVC.<br> My real aha moment regarding the M of MVC came while reading<br> Steve Michelotti's <a href="http://geekswithblogs.net/michelotti/archive/2009/10/25/asp.net-mvc-view-model-patterns.aspx" rel="nofollow noreferrer">ASP.NET MVC View Model Patterns</a> (a great source for MVC2 info all round)</p>
    singulars
    1. This table or related slice is empty.
    1. POWhere to store feedback UI data in ASP.NET MVC 2?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMorten Bergfall
    1. USMorten Bergfall
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthanks morten, that was my first thought. however, it's not really ab error, and I don't want to have to add an extra click, I don't think it's a nice user experience. with this in mind, whats the right thing to do? also could you address the whole question? cheers
      singulars
      1. PO
      1. USandy
    2. CO"If I understand you correct, you prefer to stick with one view; be it validation gold or burning SQL servers": nope, I'm talking about scenarios where it is neither an error nor a validation issue. The Model as I understand is "data" abstracted from the view, that the controller and view pass around to each other. My feedback data feels like it shouldn't be in the model...
      singulars
      1. PO
      1. USandy
    3. COthe other way around; the Model, or ViewModel, is (meant to be) to be your blueprint for how the data you pass to the View is structured.
      singulars
      1. PO
      1. USMorten Bergfall
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload