-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Sorry, I should have checked that. 2.13.1 was what we had on that
> developer's machine. Looking around I see 2.11.6 on some machines. :(
That's okay, I still come across boxes with 1.49 :) Hopefully, a newer
version will clear upi your j
On Fri, Feb 25, 2011 at 8:09 PM, Greg Sabino Mullane wrote:
> > Columns coming from DBD::Pg seems to all be Perl strings
> > and then when I encode to json then end up quoted:
>
> What version of DBD::Pg are you using? This issue should
> be fixed as of 2.14.0 (released July 2009)
>
HI Greg,
Sor
On 26/02/2011 01:50, Bill Moseley wrote:
Columns coming from DBD::Pg seems to all be Perl strings and then when I
encode to json then end up quoted:
music=# \d cd;
Table "public.cd"
Column | Type |Modifiers
-+-+
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Columns coming from DBD::Pg seems to all be Perl strings
> and then when I encode to json then end up quoted:
What version of DBD::Pg are you using? This issue should
be fixed as of 2.14.0 (released July 2009)
- --
Greg Sabino Mullane g..
his helps
> From: b...@wards.net
> Date: Fri, 25 Feb 2011 17:56:59 -0800
> Subject: Re: Numeric and string columns.
> To: mose...@hank.org
> CC: dbi-users@perl.org
>
> Sounds like DBD::Pg should know better than to do that!
> But then, DBD::mysql has the same problem. So maybe it
Sounds like DBD::Pg should know better than to do that!
But then, DBD::mysql has the same problem. So maybe it is at the DBI level?
On Fri, Feb 25, 2011 at 5:50 PM, Bill Moseley wrote:
> Columns coming from DBD::Pg seems to all be Perl strings and then when I
> encode to json then end up quoted
