Derby
  1. Derby
  2. DERBY-1478

Add built in language based ordering and like processing to Derby

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.1.2.1
    • Fix Version/s: 10.4.1.3
    • Component/s: SQL
    • Labels:
      None

      Description

      It would be good for Derby to have built in Language based ordering based on locale specific Collator.

      Language based ordering is an important feature for international deployment. DERBY-533 offers one implementation option for this but according to the discussion in that issue National Character Types carry a fair amount of baggage with them especially in the form of concerns about conversion to and from datetime and number types. Rick mentioned SQL language for collations as an option for language based ordering. There may be other options too, but I thought it worthwhile to add an issue for the high level functional concern, so the best choice can be made for implementation without assuming that National Character Types is the only solution.

      For possible 10.1 workaround and examples see:
      http://wiki.apache.org/db-derby/LanguageBasedOrdering

      1. DERBY-1478_FunctionalSpecV1.html
        5 kB
        Mamta A. Satoor
      2. DERBY-1478_FunctionalSpecV2.html
        5 kB
        Mamta A. Satoor
      3. DERBY-1478_FunctionalSpecV3.html
        5 kB
        Mamta A. Satoor
      4. DERBY-1478_FunctionalSpecV4.html
        6 kB
        Mamta A. Satoor
      5. DERBY-1478_FunctionalSpecV5.html
        6 kB
        Mamta A. Satoor

        Issue Links

        1.
        Accept the new collation attribute and store it as a database property. Will be used for language based collation ordering. Sub-task Closed Mamta A. Satoor
         
        2.
        Compare character datatypes with different collation ordering. Sub-task Closed Mamta A. Satoor
         
        3.
        Enable collation based ordering for CHAR data type. Sub-task Closed Mamta A. Satoor
         
        4.
        Enable collation based ordering for VARCHAR, LONG VARCHAR and CLOB data types. Sub-task Closed Mamta A. Satoor
         
        5.
        Document language based ordering which will be implemented by code related sub-tasks of DERBY-1478. Sub-task Closed Laura Stewart
         
        6.
        implement pushing collation info to store, storing collation info in store metadata, and creating templates based on store metadata Sub-task Closed Mike Matrigali
         
        7.
        Create initial testing framework for Junit Collation testing Sub-task Closed Kathey Marsden
         
        8.
        calling DatabaseMetaData.getColumns() with % for matching column character in a territory based collated db does not work in 1.4.2 jvms Sub-task Closed Unassigned
         
        9.
        fix like clauses with trailing % Sub-task Closed Mike Matrigali
         
        10.
        disable dynamic like optimization for collated databases Sub-task Closed Mike Matrigali
         
        11.
        throw error if non-matching collation ids in like. Sub-task Closed Mike Matrigali
         
        12.
        Make sure that all the DTDs for character string types have correct collation assigned to them. Sub-task Closed Mamta A. Satoor
         
        13.
        Ensure the DataTypeDescriptor.comparable() implements the correct rules for determing the collation to use. Sub-task Closed Unassigned
         
        14.
        Address testing todo items in CollationTest.java Sub-task Closed Kathey Marsden
         

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Mamta A. Satoor
              Reporter:
              Kathey Marsden
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development