Hi everyone,
We have some columns that are NULL but with a specified default value
(for example "0").
deleted => { type => 'integer', default => '0' },
Sometimes we need to set it to undef/NULL (a valid value), but RDBO
unhelpfully resets that to the default value ("0").
Why does it override my explicit request to make it NULL?
As an example, the following code
warn "setting $k to undef\n" if not defined $v;
$fl->$k($v);
warn "$k is defined!\n" if not defined $v and defined
$fl->$k;
outputs
"setting deleted to undef
deleted is defined!"
when $v is undef.
- ask
--
http://develooper.com/ - http://askask.com/
-------------------------------------------------------------------------
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
