| Bug #47453 | InnoDB incorrectly changes TIMESTAMP columns when JOINed during an UPDATE | ||
|---|---|---|---|
| Submitted: | 19 Sep 2009 13:46 | Modified: | 18 Jun 2010 1:28 |
| Reporter: | Peter Waltner | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: DML | Severity: | S2 (Serious) |
| Version: | 5.1.30, 5.1.45, 5.5.2-m2 | OS: | Any |
| Assigned to: | Georgi Kodinov | CPU Architecture: | Any |
| Tags: | innodb, join, timestamp, UPDATE | ||
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 Sep 2009 14:49]
Peter Waltner
[19 Sep 2009 15:29]
Peter Waltner
A workaround by protecting the UPDATE with the addition to the WHERE clause.
Attachment: BUG_47453_Workaround_1.sql (application/octet-stream, text), 1.98 KiB.
[19 Sep 2009 15:42]
Peter Waltner
Results from the workaround posted above. Note that it is important to wait >1s as documented in the workaround example.
Attachment: BUG_47453_Workaround_1_output.txt (text/plain), 4.82 KiB.
[17 Mar 2010 11:14]
Andrii Nikitin
another testcase
Attachment: bug47453.sql (application/octet-stream, text), 3.00 KiB.
