Hi Doug We have a lot of cases where users fill out a form to create or modify an object and in the process add, retain or delete relationships to various other objects.
The validity of these other objects is not in question, they are in the DB and have already been validated at the point in time when they were created. Validating them again each time they form a new relationship makes no sense - we just want to validate their existence and possibly their status. A simple (and fairly contrived example) is the relationship between a Contract object being created and the user who creating it. I don't the user's password strength checked every time the user submits a new Contract - and a definitely don't want the form validation to present a validation message relating to the user's password on the New Contract form. Thinking now, it would be great if validate could take a list or array of relationship aliases that we wanted validated. If this attribute was missing then the current greedy validation could take place. Cheers Mark -- Mark Stanton Gruden Pty Ltd http://www.gruden.com -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
