Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 19 Jun 2013 10:19:20 +0000 (UTC)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12612982.1350917599597.139617.1371637160103@arcas>
In-Reply-To: <JIRA.12612982.1350917599597@arcas>
References: <JIRA.12612982.1350917599597@arcas>
Subject: [jira] [Updated] (DERBY-5959) Territory-based collation is not
 robust against changes in the collation rules
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-5959?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik updated DERBY-5959:
---------------------------------

              Urgency: Normal
    Affects Version/s: 10.5.1.1
                       10.5.2.0
                       10.5.3.0
                       10.6.1.0
                       10.6.2.1
                       10.7.1.1
                       10.8.1.2
                       10.8.2.2
                       10.8.3.0
                       10.9.1.0
               Labels: derby_triage10_11  (was: )

Triaged for 10.11. An issue back to introduction of territory based collati=
on.
               =20
> Territory-based collation is not robust against changes in the collation =
rules
> -------------------------------------------------------------------------=
-----
>
>                 Key: DERBY-5959
>                 URL: https://issues.apache.org/jira/browse/DERBY-5959
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0, 10.6.2.1, 10=
.7.1.1, 10.8.1.2, 10.8.2.2, 10.8.3.0, 10.9.1.0, 10.10.1.1
>            Reporter: Knut Anders Hatlen
>              Labels: derby_triage10_11
>
> When accessing a database with territory-based collation, Derby will use =
the collation rules of the collator returned by Collator.getInstance(databa=
seLocale). However, there is no guarantee that those rules are consistent a=
cross different JVM vendors and versions. This means that the ordering coul=
d vary, and inconsistencies could sneak into the indexes.
> One example is that Oracle's JDK changed the collation rules for Turkish =
between Java 5 and Java 6, so if you run the following script
> connect 'jdbc:derby:memory:db;territory=3Dtr_TR;collation=3DTERRITORY_BAS=
ED;create=3Dtrue';
> create table t(c char(2));
> insert into t values '=C4=B1a', 'Ia', 'ia', '=C4=B0a', '=C4=B1b', 'Ib', '=
ib', '=C4=B0b';
> select * from t order by c;
> you'll get different results on Java 5 and on Java 6 and later.
> Java 5 will order the results like this:
> ij> select * from t order by c;
> C  =20
> ----
> =C4=B1a =20
> Ia =20
> ia =20
> =C4=B0a =20
> =C4=B1b =20
> Ib =20
> ib =20
> =C4=B0b =20
> 8 rows selected
> Java 6 and later order them like this like this:
> ij> select * from t order by c;
> C  =20
> ----
> =C4=B1a =20
> Ia =20
> =C4=B1b =20
> Ib =20
> ia =20
> =C4=B0a =20
> ib =20
> =C4=B0b =20
> 8 rows selected

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira