Bug #56748 | SQL Editor creates text drop-outs after opening SQL script file | ||
---|---|---|---|
Submitted: | 13 Sep 2010 13:01 | Modified: | 23 Sep 2010 12:03 |
Reporter: | Harald Werr | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S2 (Serious) |
Version: | 5.2.27 | OS: | Windows (XP Professional SP3) |
Assigned to: | CPU Architecture: | Any | |
Tags: | drop-outs, file content, huge files, regression, sql editor, text mutilation, text truncation |
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix>
- On windows use WinZip or a similar utility to split the large file
[13 Sep 2010 13:07]
Harald Werr
[14 Sep 2010 16:51]
Harald Werr
Original anonymized Test DB, dumped with MySQL Administrator
Attachment: MySQLAdmin_Anonymized_DB_Dump_for_Bug_56748.zip (application/octet-stream, text), 473.90 KiB.
[14 Sep 2010 16:52]
Harald Werr
Mutilated DB Dump, as created by "Save script as..." of the SQL-Editor
Attachment: MySQLAdmin_Anonymized_DB_Dump_for_Bug_56748_saved.zip (application/octet-stream, text), 473.91 KiB.
[15 Sep 2010 13:38]
Harald Werr
Another version of the anonymized DB dump, now without special characters (behaves well)
Attachment: MySQLAdmin_Anonymized_DB_Dump_for_Bug_56748_without_umlauts.zip (application/octet-stream, text), 473.91 KiB.