Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-1478 Add built in language based ordering and like processing to Derby
  3. DERBY-2703

calling DatabaseMetaData.getColumns() with % for matching column character in a territory based collated db does not work in 1.4.2 jvms

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 10.3.1.4
    • None
    • SQL
    • None
    • have reproduced on ibm142 and sun142 jvms

    Description

      calling DatabaseMetaData.getColumns(null, "APP", "CUSTOMER", "%") returns no rows for a valid APP.CUSTOMER table
      in ibm142 and sun142 jvms, for databases created with territory based collation, fails in all 3 cases we test in the
      CollationTest2.java junit test.

      Since this is a system catalog query I am surprised the result is affected at all by collation, so there may be a derby bug
      in the metadata routines, or elsewhere. Mamta, could you comment if you believe this should work already - or if there
      is more work to do in this area.

      I will soon checkin a test case into the CollationTest2.java unit test that shows this. For now I will either comment out the
      entire test, or if I can figure out how to not run it on 142 I will do that.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mikem Mike Matrigali
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: