[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-sql
Subject:    Re: [SQL] problems with changing the case of turkish characters
From:       the6campbells <the6campbells () gmail ! com>
Date:       2009-12-07 21:28:03
Message-ID: 22431f1b0912071328l6d40cd2dpaf517ff448179287 () mail ! gmail ! com
[Download RAW message or body]

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
>>
>
>

[Attachment #3 (text/html)]

<div>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&#39;d like them in the \
same table in the same database etc. </div> <div> </div>
<div>create table T ( c1 char( ...), c2 char (...) ... ) where c1 may contain thai, \
c2 korean, c3 turkish etc names </div> <div>vs</div>
<div>create table TKO (c1 char(...)), create table TTH (c1 char (...))</div>
<div>vs </div>
<div>different databases etc</div>
<div><br><br> </div>
<div class="gmail_quote">On Mon, Dec 7, 2009 at 4:20 PM, the6campbells <span \
dir="ltr">&lt;<a href="mailto:the6campbells@gmail.com">the6campbells@gmail.com</a>&gt;</span> \
wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px \
0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div>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. </div> <div> </div>
<div>USING CODESET UTF-8 TERRITORY US COLLATE USING SYSTEM</div>
<div>
<div></div>
<div class="h5">
<div> </div>
<div><br><br> </div>
<div class="gmail_quote">On Mon, Dec 7, 2009 at 12:28 PM, Tom Lane <span \
dir="ltr">&lt;<a href="mailto:tgl@sss.pgh.pa.us" \
target="_blank">tgl@sss.pgh.pa.us</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: \
#ccc 1px solid"> <div>the6campbells &lt;<a href="mailto:the6campbells@gmail.com" \
target="_blank">the6campbells@gmail.com</a>&gt; writes:<br>&gt; Just want to clarify \
if there is something I&#39;ve overlooked or if this is a<br>&gt; known issue in PG \
8.4 and 8.3<br> <br>&gt; CREATE DATABASE test<br>&gt;   WITH OWNER = postgres<br>&gt; \
ENCODING = &#39;UTF8&#39;<br>&gt;        LC_COLLATE = &#39;English, United States, \
UTF-8&#39;<br>&gt;        LC_CTYPE = &#39;English, United States, UTF-8&#39;<br> \
<br></div>Not sure why you&#39;d be expecting an English locale to follow \
Turkish<br>case-changing rules.<br><br>                       regards, tom \
lane<br></blockquote></div><br></div></div></blockquote></div><br>



[prev in list] [next in list] [prev in thread] [next in thread]