Noted mysql_fix_extensions script.

change this option, you need to first convert your old table names to

lower case before starting @code{mysqld}.

If you move @code{MyISAM} files from a Windows to a *nix disk, you may

in some cases need to use the @file{mysql_fix_extentions} tool to fix-up

the case of the file extensions in each specified database directory

(lowercase @file{.frm}, uppercase @file{.MYI} and @file{.MYD}).

@file{mysql_fix_extensions} can be found in the @file{script} subdirectory.

@node Variables, Comments, Name case sensitivity, Language Structure

@subsection User Variables

@itemize @bullet

@item

Fixed bug in truncation operator of boolean fulltext search (wrong results

when there are only @code{+word*}'s in the query).

@item

Fixed bug in DROP DATABASE with symlink

@item

Fixed bug in EXPLAIN with LIMIT offset != 0

@item

New feature :

Management of user resources

So far, the only available method of limiting user usage of MySQL

server resources has been setting max_user_connections startup

variable to some non-zero value at MySQL startup. But this method is

strictly a global one and does not allow management of individual

users, which could be  of paricular interest to Interent Service

Providers. 

Therefore, management of three resources is introduced on the

individual user level :

* number of all queries per hour

* number of all updates per hour

* number of connections made per hour

Small clarification : By the  updates in the above sense is considered

any command that changes any table or database. Queries in the above

context comprehend all commands that could be run by user. User in the

above context comprehends a single entry in user table, which is

uniquely identified by user and host columns.

All users are by default not limited in using the above resources,

unless the limits are GRANTed to them. These limits can be granted

ONLY by global GRANT (*.*) and with a following syntax :

GRANT ... WITH MAX_QUERIES_PER_HOUR = N1 MAX_UPDATES_PER_HOUR = N2

MAX_CONNECTIONS_PER_HOUR = N3;

It is not required that all three resources are specified. One or two

can be specified also. N1,N2 and N3 are intergers and should limit

number of times user can execute any command, update command  or can

login that many times per hour.

If user reaches any of the above limits withing one hour, his

connection will be broken or refused and the appropriate error message

shall be issued.

Current values of particular user resources can be flushed (set to

zero) by issuing a grant statement with any of the above limiting

clauses, including a GRANT statement with current value(s) of tha

resource(s).

Also, current values for all users will be flushed if privileges are

reloaded or if a new flush command is issued :

flush user_resources.

Also, current values for all users will be flushed with mysqladmin

reload command.

This new feature is enabled as soon as single user is GRANTed with

some of the limiting GRANT clauses.

As a prerequisite for enabling this features, user table in mysql

database must have the additional columns, just as defined in table

creation scripts mysql_install_db and mysql_install_db.sh in scripts/

directory.

Fixed bug in @code{DROP DATABASE} with symlink.

@item

New configure option --without-query-cache. 

Fixed bug in @code{EXPLAIN} with @code{LIMIT} offset != 0.

@item

Fixed bug in phrase operator @code{"..."} in boolean full-text search.

@item

Fixed bug that caused duplicated rows when using truncation operator

@code{*} in boolean full-text search.

@item

Fixed bug in truncation operator of boolean full-text search (wrong results

when there are only @code{+word*}'s in the query).

@item

Fixed bug in boolean full-text search that caused a crash when an identical

@code{MATCH} expression that did not use an index appeared twice.

@item

Query cache disabled in @code{mysqldump}.

Query cache is now automatically disabled in @code{mysqldump}.

@item

Fixed problem on Windows 98 that made sending of results very slow.

@item

output.

@item

Added @code{--no-beep} and @code{--prompt} options to @code{mysql} command-line client.

@c FIX arjen 2002-05-16 below also needs to be added elsewhere in the manual.

@item New feature: management of user resources

So far, the only available method of limiting user usage of MySQL

server resources has been setting the @code{max_user_connections}

startup variable to a non-zero value. But this method is strictly

global and does not allow for management of individual users, which

could be of paricular interest to Internent Service Providers.

Therefore, management of three resources is introduced on the

individual user level :

@itemize @bullet

@item number of all queries per hour:

any command that cahnges any table or database.

@item number of all updates per hour:

all commands that could be run by a user.

@item number of connections made per hour:

a user is a single entry in the @code{user} table, which is uniquely

identified by its @code{user} and @code{host} columns.

@end itemize

All users are by default not limited in using the above resources,

unless the limits are granted to them. These limits can be granted

@strong{only} via global @code{GRANT (*.*)}, using this syntax:

@example

GRANT ... WITH MAX_QUERIES_PER_HOUR = N1

               MAX_UPDATES_PER_HOUR = N2

               MAX_CONNECTIONS_PER_HOUR = N3;

@end example

It is not required that all three resources are specified.

N1, N2, and N3 are integers and limit the number of times that a user

can perform the corresponding type of command or number of logins,

per hour.

If user reaches any of the above limits withing one hour, his

connection will be terminated or refused and the appropriate error

message shall be issued.

Current usage values for a particular user can be flushed (set to zero)

by issuing a grant statement with any of the above clauses, including

a @code{GRANT} statement with current values.

Also, current values for all users will be flushed if privileges are

reloaded (in the server or using @code{mysqladmin reload})

or if the @code{FLUSH USER_RESOURCES} command is issued.

The feature is enabled as soon as single user is granted with some

some of the limiting @code{GRANT} clauses.

As a prerequisite for enabling this feature, the @code{user} table in

the @code{mysql} database must contain the additional columns, as

defined in the table creation scripts @code{mysql_install_db} and

@code{mysql_install_db.sh} in @file{scripts} subdirectory.

@end itemize

@node News-4.0.1, News-4.0.0, News-4.0.2, News-4.0.x