PostgreSQL

[Eugeny Balakhonov]

Hello, all!

I have a good question for PostgreSQL FAQ.

How to use string functions (like UPPER()/LOWER()) for non-latin strings?
Why UPPER() function doesn't work with my UNICODE PostgreSQL database whichcontains non-latin characters (like cyrillic)?
How to make case insensetive search by text field which contains non-latin characters?

Thanks for your answers!

Best regards
Eugeny

[Bruce Momjian]

Not sure. I thought it would work.

---------------------------------------------------------------------------

Eugeny Balakhonov wrote:

Hello, all!

I have a good question for PostgreSQL FAQ.

How to use string functions (like UPPER()/LOWER()) for non-latin strings?
Why UPPER() function doesn't work with my UNICODE PostgreSQL database which contains non-latin characters (like cyrillic)?
How to make case insensetive search by text field which contains non-latin characters?

Thanks for your answers!

Best regards
Eugeny

--
Bruce Momjian | http://candle.pha.pa.us
pg***@candle.pha.pa.us | [phone]
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Alexander Litvinov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I confirm this behavour: cyrilic words are not changed by lower()/upper()
functions, nor catched by ilike.

I am using :
=> SELECT version();
version
- ---------------------------------------------------------------
PostgreSQL 7.2.2 on i686-pc-linux-gnu, compiled by GCC 2.95.2
(1 row)

Nothing special was done during database creation (no encoding selected).

Not sure. I thought it would work.

How to use string functions (like UPPER()/LOWER()) for non-latin strings?
Why UPPER() function doesn't work with my UNICODE PostgreSQL database
which contains non-latin characters (like cyrillic)? How to make case
insensetive search by text field which contains non-latin characters?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/Nw7wV+WKOINIfOYRAuhmAJwMEkdgqXkt6ZhgJsFZfQH2mELRwg CfeDeV
L9TbSItEb0tAC7cI0cKwg6A=
=veHN
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match