| MySQL Error 1025 when Dropping Unique Constraint |
| Sunday, 13 January 2008 00:00 | |||
|
So today I ran across a very cryptic error message, although after poking around for a bit the solution ended up being rather simple. I was trying to drop a unique constraint from my database as follows:
Solution In the end, my problem was solved by dropping the foreign keys on the given table, dropping the unique constraint, and then adding the foreign keys back in. This solution seemed a little strange to me, but after thinking it over, my guess is that the unique constraint may have also been serving to help enforce certain foreign keys. Still, I wonder why MySQL couldn't automatically handle this scenario?
|




