decode_montyspeak();

@item

MySQL allows you to store some wrong date values into @code{DATE} and

@code{DATETIME} columns (like 2000-02-31 or 2000-02-00).  The idea is

that it's not the SQL server job to vaildate date.  If MySQL can store a

that it's not the SQL server job to validate date.  If MySQL can store a

date and retrieve exactly the same date, then MySQL will store the

date. If the date is totally wrong (outside of MySQL abilty to store

it), MySQL Server will store the special 0000-00-00 date value in the

column.

date. If the date is totally wrong (outside the server's ability to store

it), then the special date value 0000-00-00 will be stored in the column.

@item

If you set an @code{ENUM} column to an unsupported value, it will be set to

@item @code{lower_case_table_names}

If set to 1 table names are stored in lowercase on disk and table

names will be case-insensitive.

name comparisons will be case-insensitive.

From version 4.0.2, this option also applies to database names.

@xref{Name case sensitivity}.

The binary log contains all information that is available in the update

log in a more efficient format. It also contains information about how long

every query that updated the database took.  It doesn't contain queries that

doesn't modify any data.  If you want to log all queries (for example to

each query took that updated the database.  It doesn't contain queries that

don't modify any data.  If you want to log all queries (for example to

find a problem query) you should use the general query log. @xref{Query log}.

The binary log is also used when you are replicating a slave from a master.

@item @code{slave_compressed_protocol=#} @tab

If 1, then use compression on the slave/client protocol if both

slave and master supports this.

slave and master support this.

@item @code{slave_net_timeout=#} @tab

Number of seconds to wait for more data from the master before aborting

@end example

Note that the week number is different from what the @code{WEEK()} function

would return (@code{0}) as the week function returns the week in the

would return (@code{0}) as @code{WEEK()} returns the week in the

context of the given year.

@findex HOUR()

which contain a NULL column.

Starting from version 3.23.50 the InnoDB parser allows you to

use backquotes (`) around table and column names in the above

definition but the InnoDB parser is not yet aware of possible

variable @code{lower_case_table_names} you give in @file{my.cnf}.

use backquotes (`) around table and column names in the

@code{FOREIGN KEY ... REFERENCES ...} clause

but the InnoDB parser is not yet aware of the option

@code{lower_case_table_names} you can specify in @file{my.cnf}.

An example:

@example

are:

@itemize @bullet

@item

If MySQL can store it and retrieve a date, the wrong date is accepted

If MySQL can store and retrieve a given date, the wrong date is accepted

for @code{DATE} and @code{DATETIME} columns.

@item

All days values between 0-31 are accepted for any date.  This makes it

If the date cannot be converted to any reasonable value, a @code{0} is

stored in the @code{DATE} field, which will be retrieved as

@code{0000-00-00}.  This is both a speed and convinient issue as we

belive that the databases responsiblity etrive the same date you stored

(even if the data was not logicall correct in all cases). We think it is

up to the application to check the dates, and not the server.

@code{0000-00-00}.  This is both a speed and convenience issue as we

believe that the database's responsiblity is to retrieve the same date

you stored (even if the data was not logically correct in all cases).

We think it is up to the application to check the dates, and not the server.

@node Problems with NULL, Problems with alias, Using DATE, Query Issues

@appendixsubsec Problems with @code{NULL} Values

@item

Big code cleanup in replication code.

@item

If one specifies @code{--code-file}, call @code{setrlmit()} to change allowed

core file size to unlimited, to be able to generate core files.

If the @code{--code-file} option is specified, the server calls

@code{setrlimit()} to set the maximum allowed core file size to unlimited,

so core files can be generated.

@item

Fixed bug in query cache after temporary table creation.

@item

@code{HEX(string)} now returns the characters in @code{string} converted to

hexadecimal.

@item

Fixed problem with @code{GRANT} when using @code{lower_case_table_names == 1}.

Fixed problem with @code{GRANT} when using @code{lower_case_table_names=1}.

@item

Changed @code{SELECT ... IN SHARE MODE} to

@code{SELECT ... LOCK IN SHARE MODE} (as in MySQL 3.23).

"Foutief argumenttype voor variabele '%-.64s'",

"Variabele '%-.64s' kan alleen worden gewijzigd, niet gelezen",

"Foutieve toepassing/plaatsing van '%s'",

"Deze versie van MySQL ondersteunt nog geen '%s',"

"Deze versie van MySQL ondersteunt nog geen '%s'",