From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: DBD::Pg returns 1/0 for boolean field ... |
Date: | 2005-11-07 13:01:15 |
Message-ID: | 3e14564a674680c2b4cf85a667261cb1@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Am I doing something wrong, that DBD::Pg is "converting" it
> to 1's and 0's? Or is this expected?
That's expected: in Perl (and many other languages), both raw 't'
and 'f' are considered "true", so DBD::Pg does some mapping. Very
handy when you are passing things back and forth. You can turn this
behavior off with the pg_bool_tf attribute like this:
$dbh->{pg_bool_tf} = 1;
The default is 0. I'm going to move the explanation for this higher
up on the DBD::Pg docs page.
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200511070758
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFDb1AZvJuQZxSWSsgRAj5VAKDSgrNIeTUAlDNEjs1mfQ7ygqkSewCfdkEv
A8jdzpObzN5D8xA4dYIjmZ8=
=l8T8
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Jon Clements | 2005-11-08 14:21:01 | PLPythonU & Out of Memory - Importing Query |
Previous Message | Marc G. Fournier | 2005-11-07 05:17:35 | DBD::Pg returns 1/0 for boolean field ... |