| Bug #37514 | Insert of Blob data, sometimes the BLOB is corrupt. | ||
|---|---|---|---|
| Submitted: | 19 Jun 2008 5:36 | Modified: | 25 Jun 2008 2:35 |
| Reporter: | Paul Rolfe | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Query Browser | Severity: | S2 (Serious) |
| Version: | 5.0.51a-community edition | OS: | Linux (Fedora Core 6) |
| Assigned to: | Heikki Tuuri | CPU Architecture: | Any |
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
[19 Jun 2008 5:37]
Paul Rolfe
[19 Jun 2008 5:38]
Paul Rolfe
File I inserted. This is what I originally inserted, and comapred to
Attachment: MYSQL_CORRECT_FILE.BIN (application/octet-stream, text), 101 bytes.
[19 Jun 2008 5:39]
Paul Rolfe
Binary Log from the server. Note : The relevant insert is only the last statement.
Attachment: MYSQL_BINLOG_BUG.SQL (text/plain), 6.45 KiB.
[25 Jun 2008 2:36]
Paul Rolfe
SQL script I was using to test char sets
Attachment: anttest.sql (text/plain), 1.24 KiB.
