Bug #6202 DROP TABLE failure with misleading error message
| Submitted: | 21 Oct 2004 18:57 | Modified: | 15 Feb 2005 16:27 |
|---|---|---|---|
| Reporter: | Peter Gulutzan | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 5.0.2-alpha-debug | OS: | Linux (SuSE 8.2) |
| Assigned to: | CPU Architecture: | Any |
[21 Oct 2004 18:57]
Peter Gulutzan
[21 Oct 2004 19:21]
MySQL Verification Team
Verified against latest BK source.
[18 Nov 2004 23:01]
Chad Funk
I agree with Peter. I had to search the bug database to figure out what was wrong. I had a drop table if exists and it says "unknown" ... frustrating. Thanks, --Chad
[19 Nov 2004 14:30]
Heikki Tuuri
Hi! This was fixed in 4.1.6. The fix has probably propagated to 5.0, too. Regards, Heikki InnoDB: Change error code to HA_ERR_ROW_IS_REFERENCED if we cannot DROP a parent table referenced by a FOREIGN KEY constraint; this error number is less misleading than the previous number HA_ERR_CANNOT_ADD_FOREIGN, but misleading still.
[15 Feb 2005 13:41]
Alexander Barkov
It looks this bug was fixed while ago, but noone closed the bug report. Dear doc team, please verify whether it was documented.
[15 Feb 2005 16:27]
Paul DuBois
It was documented in the 4.1.6 change notes but there was no bug number. I added it.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.