pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Alexander Litvinov <lan@ac-sw.com>
Cc: Eugeny Balakhonov <ccs@dubki.ru>
Cc: pgsql-general@postgresql.org
Subject: Re: PostgreSQL
Date: Sun, 17 Aug 2003 00:50:45 -0400 (EDT)
Message-ID: <200308170450.h7H4ojt11396@candle.pha.pa.us> (raw)
In-Reply-To: <200308111035.12364.lan@ac-sw.com>


Added to TODO:

	* Fix upper()/lower() to work for multibyte encodings


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

Alexander Litvinov wrote:
[ PGP not available, raw data follows ]
> -----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-----
> 
[ End of raw data]

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (68+ messages)  latest in thread

Message-ID: <200308170450.h7H4ojt11396@candle.pha.pa.us>
Permalink:  ../200308170450.h7H4ojt11396@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200308170450.h7H4ojt11396@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: pgman@candle.pha.pa.us, lan@ac-sw.com, ccs@dubki.ru
  Subject: Re: PostgreSQL
  In-Reply-To: <200308170450.h7H4ojt11396@candle.pha.pa.us>
  References: <200308111035.12364.lan@ac-sw.com> <200308170450.h7H4ojt11396@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox