I've started adding the "undef sets null" functionality. It's controlled through the new undef_sets_null boolean column attribute, which is false by default to maintain backwards compatibility. You can change the default at several higher levels as well:
* For all columns of a particular column class: My::DB::Object::Metadata::Column::Foo->default_undef_sets_null(1); * For all columns used in a particular RDBO-derived class: My::DB::Object->meta->undef_sets_null(1); * For all RDBO-derived classes that use a particular metadata class: My::DB::Object::Metadata->default_undef_sets_null(1); It's implemented only for scalar, integer, varchar, and character columns right now, with more to come. Give it a spin in SVN and let me know if you have any suggestions. -John ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
