David Blewett wrote:
I think that I was the one who wondered about that. Our use case is related to moving data between different servers which have different encodings. Ofcourse the encoding should be an option only when COPY involves files.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
-- Nagy Karoly Gabriel Expert Software Group SRL (o__ 417495 Sanmartin nr. 205 //\' Bihor, Romania V_/_ Tel./Fax: +4 0259 317 142, +4 0259 317 143
begin:vcard fn:Nagy Karoly Gabriel n:Nagy;Karoly Gabriel org:Expert Software Group;R&D adr:;;Bld. Felix 205;Sanmartin;Bihor;417495;Romania email;internet:nagy.kar...@expert-erp.net title:CVO x-mozilla-html:FALSE url:http://www.expert-erp.net version:2.1 end:vcard
smime.p7s
Description: S/MIME Cryptographic Signature
