Bug #5944 | Wrong type returned for aggregate query | ||
---|---|---|---|
Submitted: | 7 Oct 2004 2:29 | Modified: | 13 Oct 2004 16:41 |
Reporter: | Keith Dreibelbis | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / NET | Severity: | S3 (Non-critical) |
Version: | 1.0.0 beta (1.0.0.22722) | OS: | Windows (Windows) |
Assigned to: | Reggie Burnett | CPU Architecture: | Any |
[7 Oct 2004 2:29]
Keith Dreibelbis
[7 Oct 2004 2:31]
Keith Dreibelbis
Also, this bug does not exist in ByteFX 0.76
[13 Oct 2004 16:41]
Reggie Burnett
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Additional info: Keith This is not a bug. Max doesn't return the max value of the columns it is working with. It returns the max value of the type of data it is given. Consider this, select max(2); You may disagree with the choice, but max(), when given integer data, returns the largest integer that MySQL can handle (in this case Int64). So, a user must know to use .GetInt64() when accessing a field that is the result of Max() (or maybe other aggregate functions).