Martin J. Evans wrote:
> Hi,
>
> With reference to the rt I created "Support binding of integers so they
> are returned as IVs" at http://rt.cpan.org/Public/Bug/Display.html?id=49818
>
> I am now at the point where being unable to bind columns to results-sets
> in DBD::Oracle with a bind type of
On Mon, Oct 26, 2009 at 03:03:43PM +, Martin Evans wrote:
>
> I cannot say why you changed DBD::Pg for JSON::XS but I can say why I
> want integers back from Oracle instead of strings when I ask for
> integers and the column is an integer. I don't think it is square pegs
> into round holes.
>
On Sun, Oct 25, 2009 at 10:24:57PM -0700, David E. Wheeler wrote:
> On Oct 24, 2009, at 2:50 PM, Tim Bunce wrote:
>
>> Callbacks are handled by the method dispatcher so all method names are
>> valid (so don't bother trying to list them in the docs :)
>>
>> Plus the two special cases for connect_cac
Greg Sabino Mullane wrote:
>
>> I could do what DBD::Pg does here (and have to verify it works) but
>> Oracle integers can be very large - too big to fit in an IV in some
>> cases.
>
> Ah yes, I forgot that Oracle doesn't really have an
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> I could do what DBD::Pg does here (and have to verify it works) but
> Oracle integers can be very large - too big to fit in an IV in some
> cases.
Greg Sabino Mullane wrote:
>
>> With reference to the rt I created "Support binding of integers so they
>> are returned as IVs" at http://rt.cpan.org/Public/Bug/Display.html?id=49818
>
> If I'm understanding you correctly, this was recently 'fixed' in DBD::Pg,
> to accomodate JSON::XS as well. Fo
