validation when setting a column value
dstroma
Currently when I create an instance of a Rose::DB::Object and set a
column value, it validates it and throws an exception immediately if
the value is invalid. Is there a way to only validate on save or
otherwise explicity? This behavior complicates my app because I was
planning on having my controllers create new objects with raw form
input as column values, with validation occuring in my models (RDBO
subclasses). With the current behavior I need validation in two places.
John Ingram
a Rose::DB::Object::Metadata subclass:
sub init_error_mode { 'return' }
John
John Siracusa
The database validation may be looser than your app's validation. If
they're an exact match for your right now, you're lucky, but I
wouldn't plan your design around that being true forever. My
suggestion is to use a form handler package of some kind to do your
application-level data validation, only passing data onto RDBO after
you're sure it's valid. To avoid repeating validation code in the
cases where the db and app constraints match, you can automatically
generate your form constraints based on your RDBO column metadata. (I
think there are a few CPAN packages for doing this.)
(If you want to use RDBO as an "unvalidated data container" to pass
values around inside your app, then I suppose you could avoid putting
any constraints on your columns (length, min/max, etc.) and let the
database do all the validation and data rejection.)
Finally, if your primary concern is with string lengths, this option
may help you keep your column constraints while also not dying on bad
input:
http://search.cpan.org/dist/Rose-DB-Object/lib/Rose/DB/Object/Metadata/Column/Scalar.pm#overflow
-John
dstroma
which is to only want to affect the error handling for the accessor/
mutator methods, not all methods of a Rose::DB::Object. What I really
am trying to do is forcibly set a column value even if it's not valid.
Something like :
$object->timestamp('asdflkjsdj');
unless ($object->save) {
print 'Sorry, ', $object->timestamp, ' is not a valid date';
}
I guess this may not be possible with the way Rose is designed. Any
suggestions?
>
> - Show quoted text -
dstroma
posted.
The database validation that Rose does is indeed looser than my
application validation. But I want all the validation to be done by my
objects themselves, rather than before the objects are created. (This
is the way Rails does it).
In my object classes I override the save() method to do my application
validation before the actual save occurs. Even if I change the error
handling to return as John Ingram suggested, when my own validation is
done the columns that Rose found invalid will be empty and I will not
be able to give friendly information back to the user.
On Mar 23, 5:56 pm, John Siracusa <sirac...@gmail.com> wrote:
>
> -John