Since long time ago I’m not writing posts about the usage of NHibernate.Validator. I wrote the post “Diving in NHibernate.Validator” because I saw some wrong examples, and even a wrong usage in another framework using NHV.
Yesterday, talking with José Romaniello, I have realized how much poor is our documentation and how few are our examples.
I have decided to begin a new series of posts on NHV.
Writing the series perhaps I’ll make public some of my classes and, perhaps, this mean I’ll re-think some piece of code introducing new features in NHV.
The initial list of titles is:
- Extending Loquacious configuration
- Fine grained and polymorphic validation
- The "Satisfy" way of custom Validators
- Extending ValidationDef
- Customizing Failure messages (base, Interpolator)
- NHibernate & NHibernate.Validator
If you are interested in something special this is the right moment to let me know.
UPDATE : I'm not sure if I want continue updating the above list with links; please use "Validator" tag to see all posts about NHibernate.Validator.
Guide and may be pitfalls on how to run validators that want access the database.
ReplyDeleteFor ex: validate that customer's "Lastname + Firstname" are unique.
The usage of resources files for the error messages, I think it's included on the "Customizing Failure messages" point, but I just want make it explicit.
ReplyDeleteThanks for yours contributions Fabio!
@Walter
ReplyDeleteYes.
I agree with mememem, a guide for validators that access the database to search for duplicate records would be very useful as I have been having plenty of issues with getting the setup correct and keep ending up with a large recursive validator.
ReplyDeleteI don't understand what you mean ?
ReplyDeleteThis post
http://fabiomaulo.blogspot.com/2009/10/validation-through-persistence.html
and this other post
http://fabiomaulo.blogspot.com/2009/10/validation-through-persistence-not.html
are not enough as "guide" ?