| Bug #28904 | ON UPDATE CURRENT_TIMESTAMP does not work properly with ON DUPLICATE KEY | ||
|---|---|---|---|
| Submitted: | 5 Jun 2007 19:04 | Modified: | 23 Jun 2007 8:44 |
| Reporter: | Andrei Nazarenko | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S2 (Serious) |
| Version: | 5.0.41 | OS: | Linux (SuSE 10.1) |
| Assigned to: | Evgeny Potemkin | CPU Architecture: | Any |
| Tags: | ON DUPLICATE KEY, ON UPDATE CURRENT_TIMESTAMP, timestamp | ||
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
