MySQL Bugs: #62198: I opened a SQL dump file in Workbench to update my database

Bug #62198	I opened a SQL dump file in Workbench to update my database
Submitted:	17 Aug 2011 19:30	Modified:	26 Aug 2011 16:22
Reporter:	Jon Fisher	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.34	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	crasg, sql script

Description:
I opened a SQL dump file in Workbench to update my database, and once I selected the file Workbench hung and then crashed.

How to repeat:
Try importing data via a sql file in workbench

Suggested fix:
?

Could you please provide the output of Help->System Info and the size of the dump file?. Thanks.

The file size is 93 MB. I closed Workbench, reopened, and tried again and it worked fine. My system info is as follows:
MySQL Workbench CE for Windows version 5.2.34

Configuration Directory: C:\Users\jon_fisher\AppData\Roaming\MySQL\Workbench

Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE

Cairo Version: 1.8.8

Rendering Mode: OpenGL is not available on this system, so GDI is used for rendering.

OS: Microsoft Windows 7  Service Pack 1 (build 7601), 64-bit

CPU: 4x Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, 7.9 GiB RAM

Active video adapter: Intel(R) HD Graphics Family

Installed video RAM: -248 MB

Current video mode: 1600 x 900 x 4294967296 colors

Used bit depth: 32

Driver version: 8.15.10.2321

Installed display drivers: igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumdx32,igd10umd32,igd10umd32

Current user language: English (United States)

Hi Jon,

What do you mean with "opened a dump"?
did you try import it?

Thanks in advance!

I mean I opened Workbench, connected to my database, and used the File | Open SQL script command. The file I was opening was a dump / export of a database provided to me from my DBA. Since I don't have access to the production database I get an export of it every two weeks for the last few years. This is the first time I've hit an error, although to be fair I only recently upgraded from the older MySQL Query Browser to workbench.

Thanks a lot for your report Jon.
The loading of dump files will be supported through a new feature in future 
releases.
As a work arround you can use the: "File -> "Execute SQL FIle..." option in WB, or the "Data Export and Restore" on the Adminitrator.

Defect duplicated of 60780.