Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-6730

Cannot create a Lucene index if a key column's name is case-sensitive

    XMLWordPrintableJSON

    Details

    • Urgency:
      Normal
    • Issue & fix info:
      Patch Available, Workaround attached

      Description

      The workaround is to create a view which gives the columns case-insensitive names. The following script shows this problem:

      connect 'jdbc:derby:memory:db;create=true';
      
      call syscs_util.syscs_register_tool( 'luceneSupport', true );
      
      create schema "s";
      
      create table "s"."t"
      (
          "passageID" int,
          "text" varchar( 32672 )
      );
      
      -- fails because the trailing key id is case-sensitive
      call luceneSupport.createIndex
      (
        '"s"',
        '"t"',
        '"text"',
        null,
        '"passageID"'
      );
      
      create view "s"."t_view" ( passageID, text ) as select * from "s"."t";
      
      -- succeeds on a view with case-insensitive identifiers
      call luceneSupport.createIndex
      (
        '"s"',
        '"t_view"',
        'text',
        null,
        'passageID'
      );
      

        Attachments

        1. derby-6730-02-aa-spacesInKeyName.diff
          6 kB
          Richard N. Hillegas
        2. derby-6730-01-aa-correctCasing.diff
          12 kB
          Richard N. Hillegas

          Issue Links

            Activity

              People

              • Assignee:
                rhillegas Richard N. Hillegas
                Reporter:
                rhillegas Richard N. Hillegas
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: