Postgres Pro
Downloads
Home   >   mailing lists

Thread: problems with changing the case of turkish characters

problems with changing the case of turkish characters

From
the6campbells
Date:
Just want to clarify if there is something I've overlooked or if this is a known issue in PG 8.4 and 8.3
 
 
CREATE DATABASE test
  WITH OWNER = postgres
       ENCODING = 'UTF8'
       LC_COLLATE = 'English, United States, UTF-8'
       LC_CTYPE = 'English, United States, UTF-8'
 
 
select ('İsteği') from tversion
"İsteği" was expecting "isteği"
 
select upper('iışğüçö') from tversion
"IıŞĞÜÇÖ"
 
select lower ('İIŞĞÜÇÖ') from tversion
"İişğüçö"
 
 

Re: problems with changing the case of turkish characters

From
Tom Lane
Date:
the6campbells <the6campbells@gmail.com> writes:
> Just want to clarify if there is something I've overlooked or if this is a
> known issue in PG 8.4 and 8.3

> CREATE DATABASE test
>   WITH OWNER = postgres
>        ENCODING = 'UTF8'
>        LC_COLLATE = 'English, United States, UTF-8'
>        LC_CTYPE = 'English, United States, UTF-8'

Not sure why you'd be expecting an English locale to follow Turkish
case-changing rules.
        regards, tom lane

Re: problems with changing the case of turkish characters

From
the6campbells
Date:
so where would I define something akin to what I can do in DB2 LUW where collate using system means to sort by the codeset. ie. without english, united states in LC_COLLATE.
 
USING CODESET UTF-8 TERRITORY US COLLATE USING SYSTEM
 


 
On Mon, Dec 7, 2009 at 12:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
the6campbells <the6campbells@gmail.com> writes:
> Just want to clarify if there is something I've overlooked or if this is a
> known issue in PG 8.4 and 8.3

> CREATE DATABASE test
>   WITH OWNER = postgres
>        ENCODING = 'UTF8'
>        LC_COLLATE = 'English, United States, UTF-8'
>        LC_CTYPE = 'English, United States, UTF-8'

Not sure why you'd be expecting an English locale to follow Turkish
case-changing rules.

                       regards, tom lane

Re: problems with changing the case of turkish characters

From
the6campbells
Date:
to clarify. just trying to ensure I understand what PG 8.4 and 8.3 provide where you may have data from alternate languages where ideally you'd like them in the same table in the same database etc.
 
create table T ( c1 char( ...), c2 char (...) ... ) where c1 may contain thai, c2 korean, c3 turkish etc names
vs
create table TKO (c1 char(...)), create table TTH (c1 char (...))
vs
different databases etc


 
On Mon, Dec 7, 2009 at 4:20 PM, the6campbells <the6campbells@gmail.com> wrote:
so where would I define something akin to what I can do in DB2 LUW where collate using system means to sort by the codeset. ie. without english, united states in LC_COLLATE.
 
USING CODESET UTF-8 TERRITORY US COLLATE USING SYSTEM
 


 
On Mon, Dec 7, 2009 at 12:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
the6campbells <the6campbells@gmail.com> writes:
> Just want to clarify if there is something I've overlooked or if this is a
> known issue in PG 8.4 and 8.3

> CREATE DATABASE test
>   WITH OWNER = postgres
>        ENCODING = 'UTF8'
>        LC_COLLATE = 'English, United States, UTF-8'
>        LC_CTYPE = 'English, United States, UTF-8'

Not sure why you'd be expecting an English locale to follow Turkish
case-changing rules.

                       regards, tom lane