-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> Umm, looking at that it strikes me that if someone calls
>
> bind_param( 1, $value, SQL_INTEGER ); # or { TYPE=>SQL_INTEGER }
>
> and the drivers translates that into *just* it's oen private type
> then valuable information has been lost.
>
> Generic code wouldn't know how to interpret pg_type values.
Good point, I've just released DBD::Pg 2.11.1 with that change. It now
outputs 'TYPE' whenever possible (when a SQL_* type was passed in
or when we can figure out an equivalent type if not). If all else fails,
we fall back to using 'pg_type' with the value passed to bind_param.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200810140024
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAkj0Hx0ACgkQvJuQZxSWSshLwgCg3IyJ194QMYpIg6lQTtqZsuMj
XdwAmwVkdqODL8eeHLYo0aJl1o2MCmr3
=WoWG
-----END PGP SIGNATURE-----
