| Bug #31020 | ARCHIVE tables with AUTO_INCREMENT ain't dumped in a backward compatible way | ||
|---|---|---|---|
| Submitted: | 14 Sep 2007 6:22 | Modified: | 12 Oct 2007 17:36 |
| Reporter: | Asuka Kenji Siu Ching Pong (Basic Quality Contributor) (OCA) | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: Backup | Severity: | S3 (Non-critical) |
| Version: | 5.1.21-beta-community | OS: | Any |
| Assigned to: | Brian Aker | CPU Architecture: | Any |
| Tags: | archive, auto_increment, mysqldump, primary key | ||
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
