Bug #3742 Foreign keys: DROP CONSTRAINT as a compatibility alias for DROP FOREIGN KEY

Submitted: 13 May 2004 12:41 Modified: 31 Jan 2020 13:41
Reporter: Matthias Urlichs Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: DDL Severity:S4 (Feature request)
Version:4.1 OS:Any (-)
Assigned to: CPU Architecture:Any

[13 May 2004 12:41] Matthias Urlichs 
Description:
Please add ALTER TABLE ... DROP CONSTRAINT as an alias for DROP FOREIGN KEY.
(Compatibility with some other databases.)

How to repeat:
See crashme.

Suggested fix:
bk pull bk://server/public/tmp/mysql41
[13 May 2004 13:27] Matthias Urlichs 
Now that pull adress was Just Plain Stupid.

Try bk://smurf.noris.de/tmp/mysql41 instead.
[2 Dec 2005 18:02] Valeriy Kravchuk 
Thank you for a reasonable feature request. I agree that ALTER TABLE ... DROP CONSTRAINT <constraint_name> | PRIMARY KEY ... syntax should be added for compatibility with other RDBMSes.
[20 Oct 2006 13:31] Roland Bouman 
I agree too, it seems like a small change and it would make MySQL a step further towards standards compliance.
[21 Oct 2006 7:56] Matthias Urlichs 
Obviously, that bitkeeper address doesn't work any more.

But the change is simple enough. ;-)
[31 Jan 2020 13:41] Erlend Dahl 
Implemented in MySQL 8.0.19.

WL#12798 Implement ALTER TABLE ... DROP/ALTER CONSTRAINT syntax.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.055 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.