HPE NonStop SQL/MX Error – 1059 Request failed. Dependent constraint constraint-name exists.

In this blog post, let’s learn about the error message “1059 Request failed. Dependent constraint constraint-name exists.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1059 Request failed. Dependent constraint constraint-name exists.

Reason for the Error

You attempted to drop a table that has a referential constraint or a check constraint that refers to another table.

Solution

Either drop all constraints that refer to other tables and then drop the table, or reissue the DROP TABLE statement, specifying the CASCADE option

Leave A Reply

Your email address will not be published. Required fields are marked *

You May Also Like

In this blog post, let’s learn about the client error message “EngineNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “EngineVersionNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “IncorrectDBClusterLockMode with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022