Bug #95078 | workbench can`t run sql file larger than 2giga | ||
---|---|---|---|
Submitted: | 22 Apr 2019 21:12 | Modified: | 30 Apr 2019 7:54 |
Reporter: | mohamed atef | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 8.0.15 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | workbench can`t run sql file larger than 2giga |
[22 Apr 2019 21:12]
mohamed atef
[23 Apr 2019 12:25]
MySQL Verification Team
Hello Mohamed, Thank you for the report and feedback. Verified as described. thanks, Umesh
[29 Apr 2019 7:27]
Mike Lischke
Posted by developer: This is not a bug but a (pretty normal) limitation, about which the user is even being warned. The warning dialog even gives you an alternative way to run the SQL script without opening it in the SQL editor. If you ignore that you have to live with the consequences.
[30 Apr 2019 7:53]
Mike Lischke
Posted by developer: I see now, thanks for the screen shots (btw. you could create an animated gif or avi/mov file to show the issue conveniently, just for your info). The actual bug is not that Workbench refuses (or warns) when a large file is opened, but in this specific case it fails to show the warning entirely. This is indeed a bug and must be fixed. Thanks for bringing this up!