mirror of
https://github.com/MariaDB/server.git
synced 2025-05-13 01:01:44 +03:00
A few style/spelling fixups.
This commit is contained in:
parent
1b2f82ecd8
commit
3dcf2214c2
@ -14135,8 +14135,9 @@ though.
|
||||
|
||||
@item --core-file
|
||||
Write a core file if @code{mysqld} dies. For some systems you must also
|
||||
specify @code{--core-file-size} to @code{safe_mysqld}. @xref{safe_mysqld, ,
|
||||
@code{safe_mysqld}}. Note that on some system like Solaris, you will
|
||||
specify @code{--core-file-size} to @code{safe_mysqld}.
|
||||
@xref{safe_mysqld, ,@code{safe_mysqld}}.
|
||||
Note that on some systems like Solaris, you will
|
||||
not get a core file if you are also using the @code{--user} option.
|
||||
|
||||
@item -h, --datadir=path
|
||||
@ -29907,8 +29908,8 @@ have any of the values shown here. The index of each value is also shown:
|
||||
|
||||
An enumeration can have a maximum of 65535 elements.
|
||||
|
||||
Starting from 3.23.51 end space are automaticly deleted from enum values
|
||||
when the table is created.
|
||||
Starting from 3.23.51 trailing spaces are automatically deleted from
|
||||
@code{ENUM} values when the table is created.
|
||||
|
||||
Lettercase is irrelevant when you assign values to an @code{ENUM} column.
|
||||
However, values retrieved from the column later have lettercase matching the
|
||||
@ -29925,9 +29926,9 @@ mysql> SELECT enum_col+0 FROM tbl_name;
|
||||
If you store a number into an @code{ENUM}, the number is treated as an
|
||||
index, and the value stored is the enumeration member with that index.
|
||||
(However, this will not work with @code{LOAD DATA}, which treats all
|
||||
input as strings.). Becasue of this, it's not advisable to store
|
||||
numbers in an enum string (You will be confused sooner or later if you
|
||||
do this).
|
||||
input as strings.)
|
||||
It's not advisable to store numbers in an @code{ENUM} string because
|
||||
it will make things confusing.
|
||||
|
||||
@code{ENUM} values are sorted according to the order in which the enumeration
|
||||
members were listed in the column specification. (In other words,
|
||||
@ -29966,8 +29967,8 @@ any of these values:
|
||||
|
||||
A @code{SET} can have a maximum of 64 different members.
|
||||
|
||||
Starting from 3.23.51 end space are automaticly deleted from @code{SET}
|
||||
values when the table is created.
|
||||
Starting from 3.23.51 trailing spaces are automatically deleted from
|
||||
@code{SET} values when the table is created.
|
||||
|
||||
MySQL stores @code{SET} values numerically, with the low-order bit
|
||||
of the stored value corresponding to the first set member. If you retrieve a
|
||||
@ -55871,7 +55872,7 @@ The trace file is made with the @strong{DBUG} package by Fred Fish.
|
||||
|
||||
@cindex gdb, using
|
||||
|
||||
On most system you can also start @code{mysqld} from @code{gdb} to get
|
||||
On most systems you can also start @code{mysqld} from @code{gdb} to get
|
||||
more information if @code{mysqld} crashes.
|
||||
|
||||
With some older @code{gdb} versions on Linux you must use @code{run
|
||||
|
Loading…
x
Reference in New Issue
Block a user