From: | Alexander Litvinov <lan(at)ac-sw(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Eugeny Balakhonov <ccs(at)dubki(dot)ru> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL |
Date: | 2003-08-11 03:35:09 |
Message-ID: | 200308111035.12364.lan@ac-sw.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----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+WKOINIfOYRAuhmAJwMEkdgqXkt6ZhgJsFZfQH2mELRwgCfeDeV
L9TbSItEb0tAC7cI0cKwg6A=
=veHN
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-08-11 03:58:26 | Re: public key functions for postgresql ? |
Previous Message | Bruce Momjian | 2003-08-11 03:00:01 | Re: Conditional row grained replication with DBMirror |