Re: COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion
От
Tom Lane
Тема
Re: COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion
Дата
Msg-id
6448.1112826122@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
Re: COPY command use UTF-8 encoding and NOT Tino Wildenhain <tino@wildenhain.de>
Improvement for COPY command .. unless it already exists (If yes
please tell me!) David Gagnon <dgagnon@siunik.com>
Re: Improvement for COPY command .. unless it already exists (If yes please tell me!) Tom Lane <tgl@sss.pgh.pa.us>
Re: Improvement for COPY command .. unless it already exists David Gagnon <dgagnon@siunik.com>
Re: Improvement for COPY command .. unless it already exists Sean Davis <sdavis2@mail.nih.gov>
Re: COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion Tom Lane <tgl@sss.pgh.pa.us>
David Gagnon 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. regards, tom lane
В списке pgsql-general по дате отправления
