[GENERAL] COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion

Hi all, I ran into this problem and want to share and have a confirmation. I tried to use COPY function to load bulk data. I craft myself a UNICODE file from a MSSQL db. I can't load it into the postgresql. I always get the error: CONTEXT: COPY vd, line 1, column vdnum: "1" The problem is

Re: [GENERAL] COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion

David Gagnon [EMAIL PROTECTED] writes: So am I right ? Is Postgresql using UTF-8 and don`t really understand UNICODE file (UCS-2)? Is there a way I can make the COPY command with a UNICODE UCS-2 encoding Postgres only supports UTF-8, not any other encoding of Unicode. Sorry.

Re: [GENERAL] COPY command use UTF-8 encoding and NOT

Am Mittwoch, den 06.04.2005, 18:12 -0400 schrieb David Gagnon: Hi all, I ran into this problem and want to share and have a confirmation. I tried to use COPY function to load bulk data. I craft myself a UNICODE file from a MSSQL db. I can't load it into the postgresql. I always get

Re: [GENERAL] COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion

On Apr 6, 2005 10:22 PM, Tom Lane [EMAIL PROTECTED] wrote: David Gagnon [EMAIL PROTECTED] writes: So am I right ? Is Postgresql using UTF-8 and don`t really understand UNICODE file (UCS-2)? Is there a way I can make the COPY command with a UNICODE UCS-2 encoding Postgres only supports