"as long as deep validation is switched on"
Is this on by default and where can I check it? It could be the casue of my problem.
James Hughes | Senior Software Engineer | Kainos | M: +353 (0)877 931 634 |
j.hughes@...
P Please consider the environment and do not print this mail unless necessary
________________________________
From: Peter Ledbrook [mailto:
peter@...]
Sent: Thu 15/05/2008 12:39
To:
user@...
Subject: Re: [grails-user] Adding Unqiueness Constraint To List
2008/5/15 Jean-Noël Rivasseau <
elvanor@...>:
> Ok, so your results are the same as mine - I did not have the
> impression that validation was cascading either.
>
> I don't think it's a bug, as validation cascading can probably become
> costly. It would be nice to have the choice in a configuration option
> - you can maybe raise a JIRA about that.
I think there's a logic bug in Grails: even if you have a "belongsTo"
field set, the validation does not cascade. In my opinion it should
(as long as deep validation is switched on). I haven't raised an issue
yet, though.
Cheers,
Peter
--
Software Engineer
G2One, Inc.
http://www.g2one.com/---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email ---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email