[
https://issues.apache.org/jira/browse/DERBY-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780127#action_12780127
]
Bryan Pendleton commented on DERBY-1358:
----------------------------------------
Should we close this as "won't fix"? It sounds like the documentation describes
the intent of the code accurately. Although there may not be a unique constraint
on the internal schema to enforce this, it sounds like we believe that
CONGLOMERATEID
is the unique identifier for the conglomerate rows, and the only cases where
this might
not be true are some situations where older databases were upgraded?
> Reference Manual incorrectly says that SYSCONGLOMERATES.CONGLOMERATEID is a
> unique identifier for the conglomerate.
> -------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1358
> URL: https://issues.apache.org/jira/browse/DERBY-1358
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.0.2.0, 10.1.1.0
> Reporter: Mamta A. Satoor
>
> CONGLOMERATEID is not a unique identifier for the SYSCONGLOMERATES and there
> is no unique key defined SYSCONGLOMERATES.CONGLOMERATEID. Reference Manual ->
> Derby System Tables -> SYCONGLOMERATES needs to be fixed to reflect that.
> Related thread on this can be found at
> http://www.nabble.com/-Derby-655-+%3A+getImportedKeys+returns+duplicate+rows+in+some+cases-t1673189.html#a4535887
> titled "[DERBY-655] : getImportedKeys returns duplicate rows in some cases".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
