[DERBY-2651] Embedded and client behave differently for IJ command "show indexes"

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.2.2.0, 10.3.1.4
• Component/s: JDBC, Network Client
• Labels: derby_triage10_9
• Urgency: Normal
• Issue & fix info: Repro attached
• Bug behavior facts: Embedded/Client difference
• Assignee: Unassigned
• Reporter: Jorgen Loland
• Created: 15/May/07 09:29
• Updated: 02/May/13 02:29

Description

The column "NON_UNIQUE" is not the same when IJ command "show indexes" is run in embedded and client mode. In embedded, "NON_UNIQUE" has the values true/false, while client has 1/0.

Embed:
---8<----
ij> connect 'jdbc:derby:testdb;create=true';
ij> SET SCHEMA APP;
ij> CREATE TABLE t1 (i int primary key, i2 int);
ij> CREATE INDEX idx1 ON APP.t1 (i2);

ij> SHOW INDEXES IN APP;
TABLE_NAME |COLUMN_NAME |NON_U&|TYPE|ASC&|CARDINA&|PAGES
----------------------------------------------------------------------------
T1 |I |false |3 |A |NULL |NULL
T1 |I2 |true |3 |A |NULL |NULL

Client:
---8<----
ij> connect 'jdbc:derby://localhost/testdb;create=true';
ij> SHOW INDEXES IN APP;
TABLE_NAME |COLUMN_NAME |NON_U&|TYPE|ASC&|CARDINA&|PAGES
----------------------------------------------------------------------------
T1 |I |0 |3 |A |NULL |NULL
T1 |I2 |1 |3 |A |NULL |NULL

Issue Links

• depends upon: DERBY-499 Expose BOOLEAN datatype to end users
• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
• is related to: DERBY-2609 The tests in ij7.sql are only performed in embedded mode.