Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id D39F7909490 for ; Mon, 7 Dec 2009 17:37:35 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 35238-01-2 for ; Mon, 7 Dec 2009 21:37:26 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mail.postgresql.org (Postfix) with ESMTP id 98B619094CE for ; Mon, 7 Dec 2009 17:28:05 -0400 (AST) Received: by bwz5 with SMTP id 5so3921438bwz.3 for ; Mon, 07 Dec 2009 13:28:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=Xs88sMdLHf4gfECwrX6Q3frHltygKaNcIS77r3fAoYY=; b=pKeZTm6/TV0/meIaZATc4N7KEP7wnjMgcGFHHJ4AyJEdz29XTz91DrZUIUPrgeRa2W lSOUYntA7pE3hMuSqQ0e9ZLFOiCacwbO0mUnSxZs763iLqdadCDywifDMNwED69xWJx6 030D8RK3TNqknnBRNClqR8Aj1PmWv/uCHpeYs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=j6Oe9W8Tb+055d5k56EjMzA6LIJmjO1WIJVuhy8caX6y2GuKumL0qCAUUrxQSGJ/XS aIHZWhHE23bDPQ9VL1zcTaxCt7vAWco2GXhYjTK/d6F0mKvYsDwzp2pdKaTR6TAM18l2 zg+bS9JiMlwSFOdsIykKqs05jMMUhGxI7rSj8= MIME-Version: 1.0 Received: by 10.204.152.4 with SMTP id e4mr541824bkw.169.1260221283202; Mon, 07 Dec 2009 13:28:03 -0800 (PST) In-Reply-To: <22431f1b0912071320i3adfede7qe6dc8b22f2ea0f4f@mail.gmail.com> References: <22431f1b0912070912p10c3191flaab6cee97e5ab63f@mail.gmail.com> <6882.1260206888@sss.pgh.pa.us> <22431f1b0912071320i3adfede7qe6dc8b22f2ea0f4f@mail.gmail.com> Date: Mon, 7 Dec 2009 16:28:03 -0500 Message-ID: <22431f1b0912071328l6d40cd2dpaf517ff448179287@mail.gmail.com> Subject: Re: problems with changing the case of turkish characters From: the6campbells To: Tom Lane Cc: pgsql-sql@postgresql.org Content-Type: multipart/alternative; boundary=0015175df034ec7866047a2a2102 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.598 tagged_above=-10 required=5 tests=BAYES_00=-2.599, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200912/18 X-Sequence-Number: 33456 --0015175df034ec7866047a2a2102 Content-Type: text/plain; charset=ISO-8859-1 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 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 wrote: > >> the6campbells 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 >> > > --0015175df034ec7866047a2a2102 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
to clarify. just trying to ensure I understand what PG 8.4 and 8.3 pro= vide where you may have data from alternate languages where ideally you'= ;d like them in the same table in the same database etc.
=A0
create table T ( c1 char( ...), c2 char (...) ... ) where c1 may conta= in thai, c2 korean, c3 turkish etc names
vs
create table TKO (c1 char(...)), create table TTH (c1 char (...))
vs
different databases etc


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


=A0
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 clari= fy if there is something I've overlooked or if this is a
> known = issue in PG 8.4 and 8.3

> CREATE DATABASE test
> =A0 WITH OWNER =3D postgres
> = =A0 =A0 =A0 =A0ENCODING =3D 'UTF8'
> =A0 =A0 =A0 =A0LC_COLLAT= E =3D 'English, United States, UTF-8'
> =A0 =A0 =A0 =A0LC_CTY= PE =3D 'English, United States, UTF-8'

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

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0regards, tom lane


--0015175df034ec7866047a2a2102--