Merge nusphere@work.mysql.com:/home/bk/mysql

@item @code{AUTO_INCREMENT} will not work with negative numbers.

@item @code{INNER}, @code{DELAYED}, @code{RIGHT} and @code{WHEN}

are now reserved words.

@item @code{FLOAT(X)} is now a true floating point type and not a value with

@item @code{FLOAT(X)} is now a true floating-point type and not a value with

a fixed number of decimals.

@item When declaring @code{DECIMAL(length,dec)} the length argument no

longer includes a place for the sign or the decimal point.

If you are using @strong{MySQL} Version 3.23, you can copy the @code{.frm},

@code{.MYI}, and @code{.MYD} files between different architectures that

support the same floating point format.  (@strong{MySQL} takes care of any

support the same floating-point format.  (@strong{MySQL} takes care of any

byte swapping issues.)

The @strong{MySQL} @code{ISAM} data and index files (@file{.ISD} and

@multitable @columnfractions .35 .65

@item @strong{Column reference} @tab @strong{Meaning}

@item @code{col_name} @tab Column @code{col_name}

from whichever table used in the query contains a column of that name

from whichever table used in the query contains a column of that name.

@item @code{tbl_name.col_name} @tab Column @code{col_name} from table

@code{tbl_name} of the current database

@code{tbl_name} of the current database.

@item @code{db_name.tbl_name.col_name} @tab Column @code{col_name} from table

@code{tbl_name} of the database @code{db_name}.  This form is available in

@strong{MySQL} Version 3.22 or later.

from functions that return integers) you may get unexpected results if

the result is larger than @code{9223372036854775807}.

@cindex floating point number

@cindex floating-point number

@tindex FLOAT

@tindex FLOAT(precision)

@item FLOAT(precision) [ZEROFILL]

year @code{2037}.  @strong{MySQL} displays @code{TIMESTAMP} values in

@code{YYYYMMDDHHMMSS}, @code{YYMMDDHHMMSS}, @code{YYYYMMDD}, or @code{YYMMDD}

format, depending on whether @code{M} is @code{14} (or missing), @code{12},

@code{8} or @code{6}, but allows you to assign values to @code{TIMESTAMP}

@code{8}, or @code{6}, but allows you to assign values to @code{TIMESTAMP}

columns using either strings or numbers.  A @code{TIMESTAMP} column is useful

for recording the date and time of an @code{INSERT} or @code{UPDATE}

operation because it is automatically set to the date and time of the most

the ability to control both precision and scale explicitly.

@code{DECIMAL} and @code{NUMERIC} values are stored as strings, rather

than as binary floating point numbers, in order to preserve the decimal

than as binary floating-point numbers, in order to preserve the decimal

precision of those values.  One character is used for each digit of the

value, the decimal point (if @code{scale} > 0), and the @samp{-} sign

(for negative numbers).  If @code{scale} is 0, @code{DECIMAL} and

@multitable @columnfractions .55 .45

@item @strong{Expression} @tab @strong{Return value}

@item expr2 or expr3 returns string @tab string

@item expr2 or expr3 returns a floating point value @tab floating point

@item expr2 or expr3 returns a floating-point value @tab floating-point

@item expr2 or expr3 returns an integer @tab integer

@end multitable

All data is stored with the low byte first. This makes the data machine and

OS independent. The only requirement is that the machine uses two's-complement

signed integers (as every machine for the last 20 years has)

and IEEE floating point format (also totally dominant among mainstream

and IEEE floating-point format (also totally dominant among mainstream

machines). The only area of machines that may not support binary

compatibility are embedded systems (because they sometimes have peculiar

processors).

@item

If you are comparing @code{FLOAT} or @code{DOUBLE} columns with numbers that

have decimals, you can't use @code{=}!  This problem is common in most

computer languages because floating point values are not exact values.

computer languages because floating-point values are not exact values.

@example

mysql> SELECT * FROM table_name WHERE float_column=3.5;

that are part of the collection) and the query. When it is used in a

@code{WHERE} clause (see example above) the rows returned are

automatically sorted with relevance decreasing. Relevance is a non-

negative floating point number. Zero relevance means no similarity.

negative floating-point number. Zero relevance means no similarity.

Relevance is computed based on number of words in the row and number of

unique words in that row, total number of words in the collection,

number of documents (rows), that contain a particular word, etc.

Added optimization of queries where @code{DISTINCT} is only used on columns

from some of the tables.

@item

Allow floating point numbers where there is no sign after the exponent

Allow floating-point numbers where there is no sign after the exponent

(like 1e1).

@item

@code{SHOW GRANTS} didn't always show all column grants.

Fixed bug that a change of all @code{VARCHAR} columns to @code{CHAR} columns

didn't change row type from dynamic to fixed.

@item

Disabled floating point exceptions for FreeBSD to fix core dump when

Disabled floating-point exceptions for FreeBSD to fix core dump when

doing @code{SELECT floor(pow(2,63))}.

@item

Changed @code{mysqld} startup option @code{--delay-key-write} to

ensure that @code{null_column NOT IN (...)} doesn't match

@code{NULL} values.

@item

Fix storage of floating point values in @code{TIME} columns.

Fix storage of floating-point values in @code{TIME} columns.

@item

Changed parsing of @code{TIME} strings to be more strict.  Now the

fractional second part is detected (and currently skipped). The

@item

Fixed optimizer problem on @code{SELECT} when using many overlapping indexes.

@item

Disabled floating point exceptions for FreeBSD to fix core dump when

Disabled floating-point exceptions for FreeBSD to fix core dump when

doing @code{SELECT floor(pow(2,63))}.

@item

Added print of default arguments options to all clients.