| Bug #24778 | Innodb: No result when using ORDER BY | ||
|---|---|---|---|
| Submitted: | 2 Dec 2006 16:17 | Modified: | 24 Apr 2007 0:58 |
| Reporter: | Christian Hammers (Silver Quality Contributor) (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.0.32-BK, 5.0.27 | OS: | Linux (Debian GNU/Linux Sid) |
| Assigned to: | Martin Hansson | CPU Architecture: | Any |
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
[2 Dec 2006 16:18]
Christian Hammers
[2 Dec 2006 16:18]
Christian Hammers
Queries
Attachment: t.select (application/octet-stream, text), 453 bytes.
[6 Feb 2007 8:49]
Martin Hansson
A (more) minimal schema and data to reveal the bug.
Attachment: initial-build.mini.sql (text/x-sql), 1.88 KiB.
[6 Feb 2007 8:50]
Martin Hansson
A (more) minimal query to go with the minimized schema.
Attachment: t.select.mini.sql (text/x-sql), 344 bytes.
[20 Mar 2007 8:47]
Martin Hansson
This is alternative fix for the bug that allows for sorting on any table in the plab
Attachment: test_if_skip_sort_order.patch (text/x-patch), 828 bytes.
