Commit 8bad6162 authored by unknown's avatar unknown

Fix invalid Texinfo formatting and rephrase text.

Also copied note to 'know bugs and misfeatures' section.

parent 3c6f77d5
...@@ -3464,6 +3464,11 @@ that in MySQL Server, @code{VARCHAR} columns are treated the same way. ...@@ -3464,6 +3464,11 @@ that in MySQL Server, @code{VARCHAR} columns are treated the same way.
@item @item
You can only have up to 255 @code{ENUM} and @code{SET} columns in one table. You can only have up to 255 @code{ENUM} and @code{SET} columns in one table.
@item
In @code{MIN()}, @code{MAX()} and other aggregate functions, MySQL
currently compares @code{ENUM} and @code{SET} columns by their string
value rather than by the string's relative position in the set.
@item @item
@code{safe_mysqld} redirects all messages from @code{mysqld} to the @code{safe_mysqld} redirects all messages from @code{mysqld} to the
@code{mysqld} log. One problem with this is that if you execute @code{mysqld} log. One problem with this is that if you execute
...@@ -33868,17 +33873,17 @@ Returns the minimum or maximum value of @code{expr}. @code{MIN()} and ...@@ -33868,17 +33873,17 @@ Returns the minimum or maximum value of @code{expr}. @code{MIN()} and
@code{MAX()} may take a string argument; in such cases they return the @code{MAX()} may take a string argument; in such cases they return the
minimum or maximum string value. @xref{MySQL indexes}. minimum or maximum string value. @xref{MySQL indexes}.
There is one inconsistency in MySQL in handling @code[ENUM] and @code[SET]
types when it comes to @code{MIN()}, @code{MAX()} and other aggregating
functions. MySQL will compare values based on string values of the columns,
instead of it's relative position. This will be fixed in future.
@example @example
mysql> SELECT student_name, MIN(test_score), MAX(test_score) mysql> SELECT student_name, MIN(test_score), MAX(test_score)
-> FROM student -> FROM student
-> GROUP BY student_name; -> GROUP BY student_name;
@end example @end example
In @code{MIN()}, @code{MAX()} and other aggregate functions, MySQL
currently compares @code{ENUM} and @code{SET} columns by their string
value rather than by the string's relative position in the set.
This will be rectified.
@findex SUM() @findex SUM()
@item SUM(expr) @item SUM(expr)
Returns the sum of @code{expr}. Note that if the return set has no rows, Returns the sum of @code{expr}. Note that if the return set has no rows,
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment