| Bug #7425 | inconsistent sort order on unsigned columns result of substraction | ||
|---|---|---|---|
| Submitted: | 20 Dec 2004 12:35 | Modified: | 10 Mar 2005 18:57 |
| Reporter: | Martin Friebe (Gold Quality Contributor) (SCA) | ||
| Status: | Closed | ||
| Category: | Server | Severity: | S3 (Non-critical) |
| Version: | 4.1.7 (probably others) | OS: | Any (any) |
| Assigned to: | Bugs System | Target Version: | |
[20 Dec 2004 12:35]
Martin Friebe
[9 Mar 2005 15:51]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/22844
[9 Mar 2005 15:54]
Timour Katchaounov
The reported problems were due to two completely unrelated omissions. 1) The file sort procedure didn't correctly create the sort key in make_sortkey() when the sortkey was an unsigned integer. 2) The name resolution procedure for column references inside a HAVING clause did not propagate the unsigned_flag of the resolved references.
[10 Mar 2005 12:52]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/22887
[10 Mar 2005 17:03]
Timour Katchaounov
Pushed in 4.1.11 and 5.0.3.
[10 Mar 2005 18:57]
Paul DuBois
Noted in 4.1.11, 5.0.3 changelogs.
