| Bug #26232 | review of bug #20944 / proof of concept attached | ||
|---|---|---|---|
| Submitted: | 9 Feb 2007 17:28 | Modified: | 15 Feb 2007 18:36 |
| Reporter: | Martin Friebe (Gold Quality Contributor) (OCA) | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
| Version: | 4.1.22, 5.0.34, 5.0.36-BK | OS: | Linux (Linux) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Contribution, Optimizer, qc, range | ||
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
[11 Feb 2007 0:28]
Martin Friebe
[11 Feb 2007 20:37]
Martin Friebe
2nd try / works with all but one test: mysqldump
Attachment: range.patch (text/x-patch), 6.77 KiB.
[13 Feb 2007 23:38]
Martin Friebe
passes all tests (except expected explain changes) + minor perfomance tweak
Attachment: range1.patch (text/x-patch), 8.02 KiB.
