| Bug #43102 | The mysql Monitor dies on the command after inserting a trigger | ||
|---|---|---|---|
| Submitted: | 23 Feb 2009 8:38 | Modified: | 25 Feb 2009 10:56 |
| Reporter: | Ketil Vestby | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S3 (Non-critical) |
| Version: | 5.1.31-community, 5.0.51a-24 and 5.0.67-0ubuntu6 | OS: | Linux (Debian Stable, Ubuntu Intrepid) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | trigger | ||
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
[25 Feb 2009 9:11]
Ketil Vestby
[25 Feb 2009 9:12]
Ketil Vestby
The result of the Linux console, when inserting todays SQL statements
Attachment: linux-console-snapshot.jpg (image/jpeg, text), 161.38 KiB.
[25 Feb 2009 9:13]
Ketil Vestby
Reproduced in Windows, using MySQL 5.1.31-community in XP
Attachment: windows-console-snapshot.jpg (image/jpeg, text), 138.40 KiB.
[25 Feb 2009 9:15]
Ketil Vestby
Second reproduction in Windows, with the same result as in Linux
Attachment: windows-console-snapshot_1.jpg (image/jpeg, text), 143.21 KiB.
[25 Feb 2009 9:24]
Ketil Vestby
Log messages from Windows
Attachment: windows-log-messages.jpg (image/jpeg, text), 203.98 KiB.
[25 Feb 2009 9:24]
Ketil Vestby
Log messages from Linux
Attachment: linux-logs.jpg (image/jpeg, text), 45.83 KiB.
