Bug #56001 | Creation of foreign keys when attempted on a MyISAM table | ||
---|---|---|---|
Submitted: | 16 Aug 2010 9:00 | Modified: | 6 Feb 2013 20:58 |
Reporter: | Roel Van de Paar | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S1 (Critical) |
Version: | 5.2.25, 5.2.26 | OS: | Any |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
[16 Aug 2010 9:00]
Roel Van de Paar
[16 Aug 2010 9:59]
Roel Van de Paar
Looks serious: When trying to reproduce the same on 5.2.26, I am able to consistently make WorkBench "hang" using 100% of one CPU core in my system **even when using InnoDB**. Video soon.
[16 Aug 2010 10:52]
Roel Van de Paar
CPU Hang is a separate issue, will log a separate bug for this later.
[16 Aug 2010 13:44]
Johannes Taxacher
as wb already recognizes that a myisam table doesn't use FKs (only ADD INDEX statement is created) we it should rather generate a warning or some sort of information to explain to the user why the FK he just created in the editor is vanished after a "successful update" to the database. the CPU-stalling issue is a different problem -> created separate Bug #56014
[26 Aug 2010 0:34]
Alfredo Kojima
Apparently stripping of foreign keys is being done on real model.
[30 Nov 2010 19:24]
Alfredo Kojima
FK tab should be disabled when editing a live object unless storage engine is InnoDB.
[6 Feb 2013 20:58]
Alfredo Kojima
Closing old bug, already implemented