Bug #4187 GREATEST function does not return 1, 0 or NULL - Move from Comparison Operators
Submitted: 17 Jun 2004 14:24 Modified: 6 Jul 2004 5:03
Reporter: Michael Kaye Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version: OS:
Assigned to: Paul DuBois CPU Architecture:Any

[17 Jun 2004 14:24] Michael Kaye 
Description:
The "GREATEST" operator is in the wrong section. Also the 

Comparison operators are ones that "result in a value of 1 (TRUE), 0 (FALSE), or NULL."

How to repeat:
see http://dev.mysql.com/doc/mysql/en/Comparison_Operators.html

Suggested fix:
Split comparison operators section and have a subsection on ones that return a boolean/null, and one that returns values/null. 

Change documentation to specify that this page is not to do with comparison operators.

Move integer operators to "Numeric Functions"
[23 Jun 2004 17:36] Dean Ellis 
Verifying this, as the various functions returning other values do violate the chapter's own definition of comparison functions.  Thank you for noting it.
[6 Jul 2004 5:03] Paul DuBois 
Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant
product(s).

Additional info:

I retitled the section from "Operators" to "Functions and Operators"
and clarified that, even for functions that don't return 1/0/NULL,
they are based on comparisons that result in 1/0/NULL.

Can't move functions like LEAST()/GREATEST() to "Numeric
Functions", because they can return values of other types.