If all the operands involved in collation operation have a collation derivation
of NONE, then Derby should throw an exception for that as per the SQL standards.
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: DERBY-2725
URL: https://issues.apache.org/jira/browse/DERBY-2725
Project: Derby
Issue Type: New Feature
Components: SQL
Affects Versions: 10.3.0.0
Reporter: Mamta A. Satoor
Assignee: Mamta A. Satoor
The collation methods in Derby should follow the rules defined by SQL spec in
Section 9.13 Collation determination Syntax Rules 2 and 3e.
According to those rules,
1)****at least one operand**** shall have a declared type collation (that means
if the comparison is sysChar1|userChar1 > sysChar2|userChar2, then such a
comparison will fail because both sides of > operator have collation derivation
of NONE.
Derby doesn't yet enforce this rule of having atleast one operand with non-NONE
collation derivation when working with collation operation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
