Databases
StackOverflow2013
Postsdbo
POEF 5 Database First using custom validation
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEF 5 Database First using custom validation
    primarykey
    data
    text
    <p>In order to experience the new features of Entity Framework I created a new MVC 4 internet application.<br/> I connected it to an existing database and generated the Model classes with the dbContext generator.</p> <p>By running the application I got some validation errors while editing a form. As example for a DateTime field the system was complaining if the date was inserted as "12/10/2012" instead of 2012-10-12 (as in the SQ Server notation). <br/>I tried to find the validation code in the project, but I could not find it anywhere in the generated code.</p> <p>One of my model classes is the following:</p> <pre><code>public partial class Artist { public Artist() { } public int Id { get; set; } public string Name { get; set; } public Nullable&lt;System.DateTime&gt; DateOfBirth { get; set; } public virtual Countries Countries { get; set; } } </code></pre> <p>How can I customize the validation errors if using the Database first approach? <br/>If I decor the models with my validation attributes, then they would be erased once the model classes are generated again.</p> <p>Moreover in a "real world" project where the use of an existing database is mandatory, what would be the best approach with the development of the model classes? <br/>Extending the classes automatically generated by adding partial classes with the same name?</p> <p>EDIT (Introduced part of the View):</p> <pre><code>@using (Html.BeginForm()) { @Html.ValidationSummary(false) &lt;fieldset&gt; &lt;legend&gt;Movie&lt;/legend&gt; &lt;div class="editor-label"&gt; @Html.LabelFor(model =&gt; model.Name) &lt;/div&gt; &lt;div class="editor-field"&gt; @Html.EditorFor(model =&gt; model.Name) @Html.ValidationMessageFor(model =&gt; model.Name) &lt;/div&gt; &lt;div class="editor-label"&gt; @Html.LabelFor(model =&gt; model.DateOfBirth) &lt;/div&gt; &lt;div class="editor-field"&gt; @Html.EditorFor(model =&gt; model.DateOfBirth) @Html.ValidationMessageFor(model =&gt; model.DateOfBirth) &lt;/div&gt; &lt;p&gt; &lt;input type="submit" value="Create" /&gt; &lt;/p&gt; &lt;/fieldset&gt; } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USFrancesco
    1. USFrancesco
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEF 5 Database First using custom validation
      1. USmillimoose
      1. VTFavorite
    2. VO
      singulars
      1. POEF 5 Database First using custom validation
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat does your view look like? There should be no problem entering a date in MM/DD/YYYY format, as this is converted to a DateTime in .net before it's sent to SQL Server. Thus, you must be doing something a bit wonky in your view. Unless you're trying to enter a date in DD/MM/YYYY format, in which case it's a globalization issue which is a totally different problem. The example you gave should not have given any validation error, though, since it's valid either way (though obviously may not give the results you want if using DD/MM/YYYY)
      singulars
      1. POEF 5 Database First using custom validation
      1. USErik Funkenbusch
    2. COYou can add validation constraints using the Fluent API:http://msdn.microsoft.com/en-us/data/gg193959.aspx
      singulars
      1. POEF 5 Database First using custom validation
      1. USmillimoose
    3. CO@millimoose - those constraints will only work on the database, not on MVC validation.
      singulars
      1. POEF 5 Database First using custom validation
      1. USErik Funkenbusch
 

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