On 9/7/07, Peter Karman <[EMAIL PROTECTED]> wrote:
> On 09/07/2007 01:03 PM, Graham Barr wrote:
>> IMO, default value should only be used during create when a value is
>> not specified by the user. At all other times the method should
>> return whatever value the object holds.
>
> agreed.
>
> IIRC, I was surprised when it didn't work like this.
Well, like I said, I can't make that behavior the default without
breaking existing code, so it'll likely be an off-by-default
per-column attribute. I'll provide a global way to turn it on,
however. Probably:
Rose::DB::Object::Metadata::Column->default_undef_sets_null(1);
which you can put in your common base class or wherever.
-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
