Databases
StackOverflow2013
Postsdbo
POUsing MVC and fluent Nhibernate, how do I validate unique fields on my ViewModel before I bind them to my Domain Object and Save them?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing MVC and fluent Nhibernate, how do I validate unique fields on my ViewModel before I bind them to my Domain Object and Save them?
    primarykey
    data
    text
    <p>I have a website where I allow users to create new Part records. I'm trying to figure out the best way to validate specific fields for uniqueness. I want to make sure that somebody doesn't try to add a Part with PartNumber 1234 if that PartNumber already exists on a different Part. </p> <p>The Web Application is using Asp.net MVC with fluent nHibernate for mapping my objects to the database. I'm using Castle validation on my view models for things like ValidateNonEmpty, ValidateRange, etc. Should I use the <a href="http://erichauser.net/2008/08/28/castle-validator-enhancements/" rel="nofollow noreferrer">ValidateSelf</a> method to query the repository to see if that part number already exists? Something doesn't feel right about using my Repository on the ViewModel. </p> <p>Would it be better for me to place that logic on the controller action? That doesn't seem right because I expect my ViewModel to already be Validated at the point (during ModelBind).</p> <p>Or maybe its none of the above. Thanks for any help on this one.</p> <p><strong>UPDATE</strong> Ok, not sure if this will help, but here is what my Save action looks like for a typical Create Action in my project:</p> <pre><code>public ActionResult Create(PartViewModel viewModel) { //I think I'd like to know if its Valid by this point, not on _repository.Save if(ModelState.IsValid) { try { var part = _partCreateViewModelMap.MapToEntity(viewModel); _repository.Save(part); return Redirect("~/Part/Details/" + part.Id); } catch (Exception e) { // skip on down... } } // return view to edit return View(viewModel); } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSecretDeveloper
    1. USshanabus
    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
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsing MVC and fluent Nhibernate, how do I validate unique fields on my ViewModel before I bind them to my Domain Object and Save them?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUsing MVC and fluent Nhibernate, how do I validate unique fields on my ViewModel before I bind them to my Domain Object and Save them?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUsing MVC and fluent Nhibernate, how do I validate unique fields on my ViewModel before I bind them to my Domain Object and Save them?
      1. USmxmissile
      1. VTFavorite
    1. COremember that anther user cold add a part with PartNumber 1234 after you have done the check for the first user trying to add that part, before you have updated the database.
      singulars
      1. POUsing MVC and fluent Nhibernate, how do I validate unique fields on my ViewModel before I bind them to my Domain Object and Save them?
      1. USIan Ringrose
    2. CO@Ian, thats a great point. There will only be a few users with the responsibility of adding parts. At this point I'm much more worried about duplicate parts in general than duplicate parts at the same time. There is a much lower probability of that happening but it is a great observation.
      singulars
      1. POUsing MVC and fluent Nhibernate, how do I validate unique fields on my ViewModel before I bind them to my Domain Object and Save them?
      1. USshanabus
 

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