[
http://issues.apache.org/jira/browse/DERBY-1577?page=comments#action_12427514 ]
Kathey Marsden commented on DERBY-1577:
---
Yes, I like DERBY-1669 better as it states the core problem that there is not
a way to differentiate between a
[
http://issues.apache.org/jira/browse/DERBY-1577?page=comments#action_12427392 ]
Jorg Janke commented on DERBY-1577:
---
A work-around is to use DatabaseMetaData.getPrimaryKeys().
The cause is that in most database systems, the constraint name
[
http://issues.apache.org/jira/browse/DERBY-1577?page=comments#action_12427405 ]
Kathey Marsden commented on DERBY-1577:
---
Thanks Jorg,
I am glad you were able to find a solution for your application. Would it be ok
to close out this
[
http://issues.apache.org/jira/browse/DERBY-1577?page=comments#action_12427409 ]
Daniel John Debrunner commented on DERBY-1577:
--
Is this the same issue as DERBY-543?
DatabaseMetaData.getIndexInfo provides misleading/confusing
[
http://issues.apache.org/jira/browse/DERBY-1577?page=comments#action_12427428 ]
Jorg Janke commented on DERBY-1577:
---
Yes DERBY-543 is basically the same - my suggestion would to use the same name
for the index as for the constraint. But,
[
http://issues.apache.org/jira/browse/DERBY-1577?page=comments#action_12424942 ]
Kathey Marsden commented on DERBY-1577:
---
I think that the name of the backing index created is in fact different than
the primary key, so I think it is
