[
https://issues.apache.org/jira/browse/DERBY-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391635#comment-17391635
]
Richard N. Hillegas commented on DERBY-7121:
--------------------------------------------
We seem to be talking past one another.
"SQL00000088-62a30128-017b-0583-e8a3-000016e126" is NOT a constraint. It is a
unique index. Indexes are dropped via the DROP INDEX command.
Constraints and the ALTER TABLE command are defined by the SQL Standard.
Indexes and the CREATE/DROP INDEX commands are NOT defined by the Standard.
Derby, like many other databases, implements constraints by creating internal
indexes. But you cannot use the ALTER TABLE command to drop an index which was
created by the CREATE INDEX command.
Let me know if this is still confusing.
> 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)
