Re: Escaping input from COPY - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Escaping input from COPY
Date
Msg-id 201112201647.20325.adrian.klaver@gmail.com
Whole thread Raw
In response to Re: Escaping input from COPY  (Josh Kupershmidt <schmiddy@gmail.com>)
Responses Re: Escaping input from COPY
List pgsql-general
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 recently brought up the same problem with psycopg2 on
> the psycopg list, and it seems there's no existing solution there,
> either.

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.

> Going out on a limb, I'm guessing that connectors don't offer
> this support because there is no function in libpq for them to wrap,
> and they don't want to kludge their own.
>
> Anyone else think it might be a good idea for libpq to offer some
> function to escape text to be used by COPY?
>
> Josh

--
Adrian Klaver
adrian.klaver@gmail.com

pgsql-general by date:

Previous
From: Culley Harrelson
Date:
Subject: Re: design help for performance
Next
From: Tom Lane
Date:
Subject: Re: out of memory error with loading pg_dumpall