[DERBY-6730] Cannot create a Lucene index if a key column's name is case-sensitive

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.11.1.1, 10.12.1.1
• Fix Version/s: 10.12.1.1
• Component/s: SQL, Tools
• Labels: derby_backport_reject_10_10
• Urgency: Normal
• Issue & fix info: Patch Available, Workaround attached
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 08/Sep/14 14:13
• Updated: 09/Sep/16 09:52
• Resolved: 16/Oct/14 19:55

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'
);

Issue Links

• relates to: DERBY-590 How to integrate Derby with Lucene API?