From: | David Blewett <david(at)dawninglight(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Add encoding support to COPY |
Date: | 2009-07-15 15:51:46 |
Message-ID: | 9d1f8d830907150851u555e8445w4424584a9d14410@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Today on IRC, someone was wondering what the preferred method of
exporting data in a specific encoding via COPY was. They reply was
wrapping the COPY command in "set client_encoding='foo';", which made
me wonder how hard it would be to add an additional WITH parameter to
the actual COPY statement to specify the encoding, a la:
[ [ WITH ]
[ BINARY ]
[ OIDS ]
[ DELIMITER [ AS ] 'delimiter' ]
[ ENCODING [ AS ] 'charset' ]
[ NULL [ AS ] 'null string' ]
[ CSV [ HEADER ]
[ QUOTE [ AS ] 'quote' ]
[ ESCAPE [ AS ] 'escape' ]
[ FORCE QUOTE column [, ...] ]
Any objections? It seems like a cleaner solution client side than
issuing multiple calls to set the client_encoding. If there are no
objections, I can attempt to prepare a patch for the next commitfest.
David Blewett
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-07-15 16:04:15 | Re: Add encoding support to COPY |
Previous Message | Tom Lane | 2009-07-15 14:53:24 | Re: more than one index in a single heap pass? |