Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The best way to do this on the server side, is to have your model implement <strong>IValidatableObject</strong> and then do the following:</p> <pre><code>public class BankPageModel : System.ComponentModel.DataAnnotations.IValidatableObject { public bool AccountRequired { get; set; } public Account NewAccount { get; set; } public IEnumerable&lt;ValidationResult&gt; Validate(ValidationContext validationContext) { // only perform validation here if account required is checked if (this.AccountRequired) { // check your regex here for account if (!RegEx.IsMatch(this.NewAccount.AccountCode, "EXPRESSION")) { yield return new ValidationResult("Error"); } } } } </code></pre> <p>Doing things this way helps keep your controllers lean and encapsulates all validation logic in your model. This method could also be verified client side with <a href="http://www.asp.net/mvc/tutorials/older-versions/javascript/creating-a-mvc-3-application-with-razor-and-unobtrusive-javascript" rel="nofollow">unobtrusive javascript</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to validate properties in 2 different situations in mvc 2 app?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPaul Aldred-Bann
    1. USPaul Aldred-Bann
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to validate properties in 2 different situations in mvc 2 app?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COso you suggest making a custom one of these for every custom validation scenario you encounter? Sounds like a whole lot of little class files around that are very tightly coupled to your model (might have to change both when you make a change) but it does a nice job of encapsulation for unit testing. Interesting
      singulars
      1. PO
      1. USJohn Culviner
    2. CO@JohnCulviner Well that depends on the developer really. Personally I like to have my controllers lean so if (ModelState.IsValid) { do this } else { do that } - this link elaborates further: http://codebetter.com/iancooper/2008/12/03/the-fat-controller/ I typically don't use data annotations on my model properties, instead I do ALL of my model validation in the Validate override of IValidatableObject. I feel it gives me far more flexibility over validating, and I find it easier to read. But as I say, this is my preference - I've worked with developers who hate models and love controllers.
      singulars
      1. PO
      1. USPaul Aldred-Bann
    3. CO@JohnCulviner oh, just to clarify having re-read your comment. I wouldn't have this validation code in a separate file, it would be contained within the model class itself as an overridden method. So each model object in your project would have its own, self-contained validation logic which would be included in the ModelState.IsValid check in your controller. You'd just perform checks in the order you need to, and yield return the results. This would appear as a list of issues to your user on the page.
      singulars
      1. PO
      1. USPaul Aldred-Bann
 

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