[
https://issues.apache.org/jira/browse/DERBY-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland updated DERBY-2651:
---------------------------------
Assignee: (was: Jørgen Løland)
That's a good point, Knut. Maybe it's better to postpone this issue until the
client can handle booleans, and then make the behaviour consistently correct.
Like you say, it should be a small task to duplicate the tests, even though it
would be more elegant not to... I'll unassign from this issue for now.
> Embedded and client behave differently for IJ command "show indexes"
> --------------------------------------------------------------------
>
> Key: DERBY-2651
> URL: https://issues.apache.org/jira/browse/DERBY-2651
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.2.2.0, 10.3.0.0
> Reporter: Jørgen Løland
> Priority: Minor
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
