mirror of
https://github.com/MariaDB/server.git
synced 2026-04-26 18:25:30 +02:00
Fix invalid Texinfo formatting and rephrase text.
Also copied note to 'know bugs and misfeatures' section.
This commit is contained in:
parent
3c6f77d54c
commit
8bad6162d1
1 changed files with 10 additions and 5 deletions
|
|
@ -3464,6 +3464,11 @@ that in MySQL Server, @code{VARCHAR} columns are treated the same way.
|
|||
@item
|
||||
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
|
||||
@code{safe_mysqld} redirects all messages from @code{mysqld} to the
|
||||
@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
|
|||
@code{MAX()} may take a string argument; in such cases they return the
|
||||
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
|
||||
mysql> SELECT student_name, MIN(test_score), MAX(test_score)
|
||||
-> FROM student
|
||||
-> GROUP BY student_name;
|
||||
@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()
|
||||
@item SUM(expr)
|
||||
Returns the sum of @code{expr}. Note that if the return set has no rows,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue