Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>My recommendation is basically what you don't want: create new model classes, but use inheritance to avoid repeating the properties you want. If you are adamantly opposed to creating separate models, you might look into implementing <code>IValidatableObject</code> and have it inspect other properties before validating the properties that you wish to vary.</p> <p><strong>EDIT</strong>: I don't disagree with Tuliper's answer, but to flesh out my suggestions, consider a scenario in which you want to save a user's data. From one form, you are creating a user; from another, you are simply updating (this is a bit of a stretch but it's for purposes of illustration). The "create" form might require the name of a person referring the user, while the "update" form might not. </p> <p>Using inheritance, you could do the following:</p> <pre><code>public class SaveUserModel { public int? UserId { get; set; } ... } public class CreateUserModel : SaveUserModel { [Required] public string ReferredByName { get; set; } } </code></pre> <p>Using <code>IValidatableObject</code>, you could do it this way:</p> <pre><code>public class SaveUserModel : IValidatableObject { public int? UserId { get; set; } public string ReferredByName { get; set; } ... public IEnumerable&lt;ValidationResult&gt; Validate(ValidationContext validationContext) { // if UserId is null, we are creating a user vs. updating if (UserId != null &amp;&amp; string.IsNullOrWhiteSpace(ReferredBySiteUrl)) yield return new ValidationResult("Please specify the name of the person who referred you.", new[] { "ReferredByName" }); } } </code></pre> <p>To reiterate, I am not trying to push my answer. I would be inclined to reuse models if they are exactly the same across different views, but generally there are enough differences to warrant simply creating separate models. In the end, any perceived technical debt alleviated by adhering to DRY in this situation would a bit of a wash; models tend to be easy to maintain.</p>
    singulars
    1. This table or related slice is empty.
    1. POvalidation rules in mvc 3.0
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USegoodberry
    1. USegoodberry
    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. COi am not understand can you explain me or given any example if you have.
      singulars
      1. PO
      1. USmayur Rathod
    2. COAdded examples for purposes of conversation / education.
      singulars
      1. PO
      1. USegoodberry
 

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