[DERBY-2725] 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.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.1.4, 10.4.1.3
• Fix Version/s: 10.3.1.4, 10.4.1.3
• Component/s: SQL
• Assignee: Mamta A. Satoor
• Reporter: Mamta A. Satoor
• Created: 29/May/07 20:36
• Updated: 06/Jul/07 11:19
• Resolved: 06/Jul/07 11:19

Description

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.

Issue Links

• is part of: DERBY-2678 Derby should follow SQL standards when operand(s) in the collation operation have collation derivation of NONE
• relates to: DERBY-1478 Add built in language based ordering and like processing to Derby