Hello
It's look like SQL_ASCII support diacritic chars now. First you haveto encode from bytea to text
postgres=# SELECT encode(convert('ján', 'UNICODE', 'SQL_ASCII'),'escape'); encode-------- ján(1 row)
you wontpostgres=# SELECT to_ascii(encode(convert_to('ján','latin2'),'escape'),'latin2'); to_ascii---------- jan(1 row)
RegardsPavel Stehule
convert do conversion from text to bytea type. For diacriticelimination use to_ascii function:
postgres=# select to_ascii(convert('Příliš žlutý kůň' usingutf8_to_iso_8859_2),'latin2'); to_ascii------------------ Prilis zluty kun(1 row)
On 12/12/2007, Jan Sunavec <jan.sunavec@xxxxxxxxx> wrote:> Hi all>> I have problem with "convert" function. Previous behaviour was> SELECT convert('ján', 'UNICODE', 'SQL_ASCII');> =======================================> jan>> In postgresql 8.3 is quite new behaviour.> SELECT convert('ján', 'UNICODE', 'SQL_ASCII');> ======================================> "j\241n">> This, drives me crazy. I mean, this is not useable for non english> country. I don't need convert to \241 characters. I understand that> someone need this behavour. But there should be possibility switch to> "normal" behaviour.>> John>> ---------------------------(end of broadcast)---------------------------> TIP 9: In versions below 8.0, the planner will ignore your desire to> choose an index scan if your joining column's datatypes do not> match>
---------------------------(end of broadcast)---------------------------TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your message can get through to the mailing list cleanly
