unicode regular insensitive matching

Started by Jan Poslusnyalmost 25 years ago3 messagesgeneral
Jump to latest
#1Jan Poslusny
pajout@gingerall.cz

-------- Original Message --------
Subject: unicode regular insensitive matching
Date: Thu, 28 Jun 2001 20:32:08 +0200
From: Jan Poslusny <pajout@gingerall.cz>
Organization: Ginger Alliance
To: pgsql-general@postgresql

I am newbie in postgreSQL and I have this problem with 7.1.2 version:
I configured via
./configure
--enable-locale
--enable-multibyte=UNICODE
--enable-unicode-conversion
--enable-recode
then I succesfully gmake, gmake check, gmake install,
then I initdb -E UNICODE,
then I createdb -E UNICODE.

but

select myfield from mytable where myfield ~* 'MiXeD national-specific
characters' order by myfield

is _NOT_ case insensitive and not ordered according to locales (if I
create another db with LATIN2 charset, all is OK)

Can anybody hint me ?
regards
pajout

#2Peter Eisentraut
peter_e@gmx.net
In reply to: Jan Poslusny (#1)
Re: unicode regular insensitive matching

Jan Poslusny writes:

then I initdb -E UNICODE,
then I createdb -E UNICODE.

select myfield from mytable where myfield ~* 'MiXeD national-specific
characters' order by myfield

is _NOT_ case insensitive and not ordered according to locales (if I
create another db with LATIN2 charset, all is OK)

Unicode is only a character set. Issues like sorting and letter-case are
determined by the locale. You didn't say which locale you used or wanted
to use, what your input was and what ordering you expected, so there's not
a lot we can do for you.

--
Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter

#3Jan Poslusny
pajout@gingerall.cz
In reply to: Peter Eisentraut (#2)
unicode regular insensitive matching 2.

I used czech locales, described in attached pg_bash_profile exactly,
briefly here:
LC_ALL=cs_CZ
LC_COLLATE=cs_CZ
LC_CTYPE=cs_CZ
LC_MONETARY=cs_CZ
LC_NUMERIC=cs_CZ
LC_TIME=cs_CZ

I used unicodeSQL script for db with UNICODE charset and latin2SQL
script for db with LATIN2 charset. I hope attached scripts are
self-describing.

I don't know, what is misconfigured or badly used.

thanks for some hint

Peter Eisentraut wrote:

Show quoted text

Jan Poslusny writes:

then I initdb -E UNICODE,
then I createdb -E UNICODE.

select myfield from mytable where myfield ~* 'MiXeD national-specific
characters' order by myfield

is _NOT_ case insensitive and not ordered according to locales (if I
create another db with LATIN2 charset, all is OK)

Unicode is only a character set. Issues like sorting and letter-case are
determined by the locale. You didn't say which locale you used or wanted
to use, what your input was and what ordering you expected, so there's not
a lot we can do for you.

Attachments:

pg_bash_profiletext/plain; name=pg_bash_profileDownload
unicodeSQLapplication/octet-stream; name=unicodeSQLDownload
latin2SQLapplication/octet-stream; name=latin2SQLDownload