Bug #65707 | Alter Table option does nothing | ||
---|---|---|---|
Submitted: | 22 Jun 2012 8:41 | Modified: | 12 Jul 2012 14:11 |
Reporter: | Jean-Yves Rouffiac | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 5.2.40 | OS: | MacOS (10.7.4) |
Assigned to: | CPU Architecture: | Any | |
Tags: | ALTER TABLE, Lion, os x, sql editor |
[22 Jun 2012 8:41]
Jean-Yves Rouffiac
[3 Jul 2012 2:04]
Alfredo Kojima
There are log files in ~/Library/Logs/DiagnosticReports and ~/Library/Application Support/MySQL/Workbench/logs/
[3 Jul 2012 7:55]
Jean-Yves Rouffiac
Thanks. I closed down WB, started it up to again to get a fresh set of logs and here is what I have ~/Library/Application Support/MySQL/Workbench/login wb.log: 08:47:55 [INF][ Workbench]: Starting up Workbench 08:47:55 [INF][ Workbench]: Loading main window 08:47:55 [INF][ WBContext]: WbContext::init 08:47:56 [WRN][ grt]: Could not load db.mysql.editors.wbp.dylib: Duplicate module MySQLEditorsModule Could not load wb.mode$ MySQL Workbench CE for Mac OS X version 5.2.40 revision 8790 Configuration Directory: /Users/jrouffiac/Library/Application Support/MySQL/Workbench Data Directory: /Applications/MySQLWorkbench.app/Contents/Resources Cairo Version: 1.9.1 OS: Darwin 11.4.0 CPU: 4x Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz, 8.0 GB RAM 08:47:59 [INF][ SSH tunnel]: Starting tunnel I am also getting a *lot* of the following when I look at the older log files even though I have only gone through the Server Admin wizard 2 times: 10:54:35 [WRN][ ]: Trying to turn past the last page of the wizard I don't have any Workbench-related logs in ~/Library/Logs/DiagnosticReports Hope this helps.
[3 Jul 2012 13:08]
Alfredo Kojima
Did you try opening the ALTER table editor before getting the log files?
[3 Jul 2012 13:46]
Jean-Yves Rouffiac
Yes.
[3 Jul 2012 14:51]
Jean-Yves Rouffiac
Hi ALfredo I have found the reason: there was a database in the /usr/local/mysql/data directory called 'mysql.old' When I moved that database out of the directory, it worked again. I figured this out by reading through http://bugs.mysql.com/bug.php?id=62686 and seeing the reference to corrupt system tables. Maybe a check could be done by Workbench to make sure it is looking at the correct 'mysql' database if more than one database exists in the data folder which starts with those characters? Thanks very much for assisting me with this issue by the way - as ever, I am hugely indebted to all the people who make MySQL and the associated products such a great suite of tools.
[12 Jul 2012 14:11]
Alfredo Kojima
There's nothing we can do about that from WB, we can only work with MySQL server responses.