You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2007/05/29 22:37:16 UTC
[jira] Created: (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.
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.
[jira] Resolved: (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.
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor resolved DERBY-2725.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.4.0.0
10.3.1.1
Merged the fix from main(revision 553834) into Derby 10.3.1.1 codeline (revision 553837)
> 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: Bug
> Components: SQL
> Affects Versions: 10.3.0.0, 10.3.1.1, 10.4.0.0
> Reporter: Mamta A. Satoor
> Assignee: Mamta A. Satoor
> Fix For: 10.3.1.1, 10.4.0.0
>
>
> 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.
[jira] Commented: (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.
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510652 ]
Mamta A. Satoor commented on DERBY-2725:
----------------------------------------
Fixed this bug with checkin 553834 into main with following commit comments ( will merge this soon into Derby 10.3.1.1 codeline)
DERBY-2725
If both the character string operands involved in DataTypeDescriptor.comparable() have collation derivation of NONE, then
such 2 DTDs can't be compared. I am adding code to implement that behavior and added a test case for this.
> 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: Bug
> Components: SQL
> Affects Versions: 10.3.0.0, 10.3.1.1, 10.4.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.
[jira] Updated: (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.
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor updated DERBY-2725:
-----------------------------------
Affects Version/s: 10.4.0.0
10.3.1.1
Issue Type: Bug (was: New Feature)
> 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: Bug
> Components: SQL
> Affects Versions: 10.3.0.0, 10.3.1.1, 10.4.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.
[jira] Closed: (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.
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor closed 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.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2725
> URL: https://issues.apache.org/jira/browse/DERBY-2725
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.0.0, 10.3.1.1, 10.4.0.0
> Reporter: Mamta A. Satoor
> Assignee: Mamta A. Satoor
> Fix For: 10.3.1.1, 10.4.0.0
>
>
> 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.