Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <28813554.1182887245977.JavaMail.jira@brutus>
Date: Tue, 26 Jun 2007 12:47:25 -0700 (PDT)
From: "Daniel John Debrunner (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-2876) Ensure the
 DataTypeDescriptor.comparable() implements the correct rules for determing
 the collation to use.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ensure the DataTypeDescriptor.comparable() implements the correct rules for determing the collation to use.
-----------------------------------------------------------------------------------------------------------

                 Key: DERBY-2876
                 URL: https://issues.apache.org/jira/browse/DERBY-2876
             Project: Derby
          Issue Type: Sub-task
          Components: SQL
    Affects Versions: 10.3.0.0, 10.3.1.0, 10.3.1.1, 10.4.0.0
            Reporter: Daniel John Debrunner


The current implementation of comparable requires that collation type *and* derivation must match for the types to be comparable.
This is not correct according to SQL Standard 9.13, e.g. with non-matching types and one derivation of implicit and one of none, then the types are comparable.

Possibly this method is not the correct location for this functionality, as no indication can be given of the correct collation to use, just if they are comparable or not.

Would be fixed by a correct implementation of the 9.13 rules under DERBY-2875, but that's marked as an improvement.
This issue is to record the fact that the comparision logic is currently incorrect and so DERBY-1478 is not yet complete.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.