On Wednesday, December 21, 2011 3:16:42 pm Josh Kupershmidt wrote:
> On Tue, Dec 20, 2011 at 7:47 PM, Adrian Klaver
wrote:
> > As far as I know you did not get an answer, which is not the same as
> > there being no answer:) I think you will find that the escaping is
> > handled for you.
>
> I am
On Wed, Dec 21, 2011 at 06:16:42PM -0500, Josh Kupershmidt wrote:
> On Tue, Dec 20, 2011 at 7:47 PM, Adrian Klaver
> wrote:
> > As far as I know you did not get an answer, which is not the same as there
> > being
> > no answer:) I think you will find that the escaping is handled for you.
>
> I
On Tue, Dec 20, 2011 at 7:47 PM, Adrian Klaver wrote:
> As far as I know you did not get an answer, which is not the same as there
> being
> no answer:) I think you will find that the escaping is handled for you.
I am rather dubious of the claim that "escaping is handled for you"
with copy_from(
On Tuesday, December 20, 2011 3:56:14 pm Josh Kupershmidt wrote:
>
> This is really a question for the DBD::Pg folks, I think. Looking at:
> http://search.cpan.org/~turnstep/DBD-Pg-2.16.1/Pg.pm#COPY_support
>
> It doesn't look like there is support for escaping COPY data. But
> incidentally, I
On Mon, Dec 19, 2011 at 6:56 AM, Roger Leigh wrote:
> I'd like to switch to COPY, which should be orders of
> magnitude faster. I see that DBD::Pg has an interface for
> this, which looks just fine. My problem is with how to
> escape the data. I need to use whatever escaping rules
> are in use
