Oracle 5.0 Reference Manual page 1180

Table of Contents

Advertisement

only for those columns for which you have the
set to their implicit default values if strict SQL mode is not enabled. In strict mode, the statement is
rejected if any of the omitted columns have no default value. (Standard SQL requires you to have the
[577]
INSERT
Section 11.1.7, "Data Type Default
13.7.1.4.
RENAME USER
RENAME USER
[,
old_user
The
RENAME USER
CREATE USER
if any old account does not exist or any new account exists. Each account name uses the format
described in
RENAME USER 'jeffrey'@'localhost' TO 'jeff'@'127.0.0.1';
If you specify only the user name part of the account name, a host name part of
RENAME USER
RENAME USER
user created. This includes stored programs or views for which the
user. Attempts to access such objects may produce an error if they execute in definer security context.
(For information about security context, see
Views".)
The privilege changes take effect as indicated in
The
RENAME USER
13.7.1.5.
Syntax
REVOKE
REVOKE
priv_type
[,
priv_type
ON [object_type]
FROM
user
REVOKE ALL PRIVILEGES, GRANT OPTION
FROM
user
The
REVOKE
Each account name uses the format described in
example:
REVOKE INSERT ON *.* FROM 'jeffrey'@'localhost';
If you specify only the user name part of the account name, a host name part of
For details on the levels at which privileges exist, the permissible
values, and the syntax for specifying users and passwords, see
To use the first
the privileges that you are revoking.
To revoke all privileges, use the second syntax, which drops all global, database, table, column, and
routine privileges for the named user or users:
REVOKE ALL PRIVILEGES, GRANT OPTION FROM
To use this
[578]
UPDATE
Account Management Statements
privilege on all columns.)
Syntax
old_user
TO
new_user
TO new_user] ...
statement renames existing MySQL accounts. To use it, you must have the global
[576]
privilege or the
Section 6.2.3, "Specifying Account
causes the privileges held by the old user to be those held by the new user. However,
does not automatically drop or invalidate databases or objects within them that the old
statement was added in MySQL 5.0.2.
[(column_list)]
[(column_list)]] ...
priv_level
[, user] ...
[, user] ...
statement enables system administrators to revoke privileges from MySQL accounts.
syntax, you must have the
REVOKE
syntax, you must have the global
REVOKE
privilege for the
mysql
[577]
INSERT
Section 5.1.7, "Server SQL
Values", discusses implicit default values.
[578]
privilege for the
UPDATE
Names". For example:
Section 18.5, "Access Control for Stored Programs and
Section 6.2.6, "When Privilege Changes Take
Section 6.2.3, "Specifying Account
GRANT OPTION
user
[, user] ...
CREATE USER
database.
1160
privilege. The omitted columns are
Modes", discusses strict mode.
database. An error occurs
mysql
is used.
'%'
attribute names the old
DEFINER
Names". For
is used.
'%'
and
priv_type
priv_level
Section 13.7.1.3,
"GRANT
[577]
privilege, and you must have
[576]
privilege or the
Effect".
Syntax"

Advertisement

Table of Contents
loading

This manual is also suitable for:

Mysql 5.0

Table of Contents