Re: UNICODE
От | Jean-Michel POURE |
---|---|
Тема | Re: UNICODE |
Дата | |
Msg-id | 4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr обсуждение исходный текст |
Ответ на | Re: UNICODE (Marko Kreen <marko@l-t.ee>) |
Ответы |
Re: UNICODE
|
Список | pgsql-hackers |
I only want this query to work under Unicode: SELECT * FROM test WHERE source_content ILIKE '%accepté%'. >* If client_encoding == server_encoding, the bytes are put into > DB as-is - no conversion is done. > >So are you absolutely sure you have on client side UTF8 strings? PostgreSQL is compiled with UNICODE and LOCALE support. Unicode is used on both ends (PostgreSQL and psql). >Unfortunately you cant use client_encoding=latin1 as PostgreSQL >refuses the do the conversion between them. (I am with 7.1.3) According to the on-line manual, only MULE provides instant transcoding. >Eg. I did the following: > >* created db with encoding = UNICODE >* Put your example into test.sql >* iconv -f latin1 -t utf8 test.sql > test2.sql >* psql < test2.sql > >and it worked as it should... Nice to hear it works when transcoding files to UTF-8. It shows it is not a back-end problem. As for me, I typed INSERT INTO source_content VALUES ('Permis de conduire accepté') in Psql. Psql does not insert the data and I have to kill it manually. Can you reproduce this? Best regards, Jean-Michel POURE
В списке pgsql-hackers по дате отправления: