Bug #51637 | Loading an SQL script into Workbench causes program failure | ||
---|---|---|---|
Submitted: | 2 Mar 2010 11:25 | Modified: | 26 May 2010 7:21 |
Reporter: | Keith Macdonald | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S1 (Critical) |
Version: | 5.2.16 OSS beta | OS: | Windows (running on Vista) |
Assigned to: | CPU Architecture: | Any |
[2 Mar 2010 11:25]
Keith Macdonald
[2 Mar 2010 11:28]
Valeriy Kravchuk
Thank you for the problem report. Please, send the results of SHOW CREATE TABLE for that client table. Is it empty when you try to run the script?
[2 Mar 2010 11:30]
Keith Macdonald
I've just realised it's fine if the script only has a few lines, but the full version has 361 lines, and that's when Workbench crashes.
[2 Mar 2010 11:42]
Keith Macdonald
Hi Valeriy I ran this "show create table migration.client" This is the table 'client', 'CREATE TABLE `client` ( `ID` bigint(20) NOT NULL, `CODE` varchar(256) character set latin1 collate latin1_bin NOT NULL, `DESCRIPTION` varchar(256) character set latin1 collate latin1_bin default NULL, `NAME` varchar(256) character set latin1 collate latin1_bin NOT NULL, PRIMARY KEY (`ID`), UNIQUE KEY `CLIENT_U1` (`CODE`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1' The full version of my INSERTs script starts with TRUNCATE TABLE migration.client I can cause the same problem to happen like this: If I start with a blank SQL Statement window and paste-in just the first 50 lines, I can execute and it runs OK. It still works when I add the next 50 lines. But when I paste-in the remaining 260 lines, it crashes immediately, even before I had a chance to try executing the insert statements. I can see no strange control or binary characters in the text.
[2 Mar 2010 13:31]
MySQL Verification Team
Probably related to bug: http://bugs.mysql.com/bug.php?id=51324?.
[4 Mar 2010 12:55]
Susanne Ebrecht
Please try to increase innodb_buffer_pool_size.
[4 Mar 2010 14:34]
Keith Macdonald
How can I increase the innodb_buffer_pool_size?
[5 Mar 2010 10:08]
Susanne Ebrecht
http://dev.mysql.com/doc/refman//5.1/en/server-system-variables.html
[17 Mar 2010 11:52]
Keith Macdonald
Sorry, that did not cure the problem. I have had to go back to using MySQL Query Browser. That might be an obsolete product, but at least it does not crash when I open text script files.
[21 Mar 2010 23:16]
John Redford
MySQL Workbench Error 3/21/2010 5:47 PM Vista Deluxe Home Edition 64 bit SP2 This appears just after the SQL script is loaded. It's a MySQL backup file. I get the error "Unknown exception caught in c:\documents and settings\mysql\mysql-workbench-oss-5.2.16\backend\windows\wbprivate.wr\src\Wb.h at line 1087 Press OK, then another complaint "Unknown exception caught in c:\documents and settings\mysql\mysql-workbench-oss-5.2.16\backend\windows\wbprivate.wr\src\Wb.h at line 1087"
[26 Apr 2010 7:21]
Sveta Smirnova
Thank you for the feedback. This looks like duplicate of bug #51815 fixed in version 5.2.17. Please upgrade to current version 5.2.19, try with it and inform us if problem still exists at your side.
[26 May 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".