On 7/8/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> I'm trying to pass a null value in for a bigint column.
>
> pg keeps complaining because its getting a 0. doing a data::dumper,
> I'm seeing the column with
> value=> [0]
> _a => undef
> _p=> undef
> sign=> '+'
>
> tailing the pg log, rose sends a 0
> I'm explicitly setting this col to undef, and it is not a 'not_null' col
I added a test for this in SVN and can't reproduce it. My column defs:
bint4 BIGINT,
bint4 => { type => 'bigint' },
The tests (edited):
$o = MyPgObject->new;
$o->bint4(555);
$o->save;
$o = MyPgObject->new(id => $o->id)->load;
is($o->bint4, 555, "bigint null 2 - $db_type");
$o->bint4(undef);
$o->save;
$o = MyPgObject->new(id => $o->id)->load;
is($o->bint4, undef, "bigint null 3 - $db_type");
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Rose-db-object mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rose-db-object
