Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-2678 Derby should follow SQL standards when operand(s) in the collation operation have collation derivation of NONE
  3. DERBY-2793

Ensure LIKE predicate follows correct rules for determing collation

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Reopened
    • Major
    • Resolution: Unresolved
    • None
    • None
    • SQL
    • Normal

    Description

      The current code in LikeEscapeOperatorNode seems to only check that the collations are identical. That is not the correct mechanism for determing collation which is based upon SQL spec Section 9.13 "Collation determination" or item 12 in the DERBY-1478 wiki page.

      http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478

      I think it's also essential that the (somewhat complex) logic to implement collation determination is in a single method, not repeated multiple times for each collation.

      There is a TODO in LikeEscapeOperatorNode that might be related to this.

      Attachments

        Issue Links

          relates to

          Improvement - An improvement or enhancement to an existing feature or task. DERBY-2875 Check if collation determination logic can be consolidated in one central place rather than multiple places in the compile package

          • Major - Major loss of function.
          • Open

          Activity

            People

              mamtas Mamta A. Satoor
              djd Daniel John Debrunner
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated: