Re: Escaping input from COPY

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: Josh Kupershmidt <schmiddy(at)gmail(dot)com>, Roger Leigh <rleigh(at)codelibre(dot)net>
Subject: Re: Escaping input from COPY
Date: 2011-12-21 00:47:19
Message-ID: 201112201647.20325.adrian.klaver@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)klaver(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2011-12-21 01:16:35 Re: out of memory error with loading pg_dumpall
Previous Message Culley Harrelson 2011-12-21 00:36:55 Re: design help for performance