[
https://issues.apache.org/jira/browse/DERBY-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391727#comment-17391727
]
Walter Weinmann commented on DERBY-7121:
----------------------------------------
Hi Richard - I managed to solve my problem by naming my unique keys. Then I can
simply ignore the "unknown" ones with the getIndexInfo method. Thanks for the
help.
> DROP UNIQUE KEY not working
> ---------------------------
>
> Key: DERBY-7121
> URL: https://issues.apache.org/jira/browse/DERBY-7121
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.15.2.0
> Environment: Own Docker Image based on Ubuntu 20.04, please see here:
> https://hub.docker.com/repository/docker/konnexionsgmbh/apache_derby
> Reporter: Walter Weinmann
> Priority: Major
> Attachments: IssueApacheDerby.pdf
>
>
> I try to drop the FOREIGN KEY, PRIMARY KEY and UNIQUE KEY constraints before
> the INSERT. To do this, I use the DatabaseMetaData class from JDBC. When
> dropping the UNIQUE KEY I get the following error message:
> {{java.sql.SQLSyntaxErrorException: ALTER TABLE failed. There is no
> constraint 'KXN_SCHEMA.SQL00000166-6f554487-017a-f4fd-c9dc-000016e126' on
> table '"KXN_SCHEMA". "COUNTRY_STATE"'.}}
> Details about the error and the database environment can be found in the
> attached PDF document.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
