diff options
| author | unknown <monty@hundin.mysql.fi> | 2002-10-02 13:56:17 +0300 |
|---|---|---|
| committer | unknown <monty@hundin.mysql.fi> | 2002-10-02 13:56:17 +0300 |
| commit | 06fbbd1acb7d01c98d7df5efefa79939920ad0a4 (patch) | |
| tree | db82378be1bc2cf5484e34071c056809f00da2d0 /Docs | |
| parent | 11b0b9447aaff795cbd7e6d12541d898bf029316 (diff) | |
| parent | 8432a3c216c331f2ee0a51e9c8cce14ad30accb4 (diff) | |
| download | mariadb-git-06fbbd1acb7d01c98d7df5efefa79939920ad0a4.tar.gz | |
merge
configure.in:
Auto merged
Diffstat (limited to 'Docs')
| -rw-r--r-- | Docs/manual.texi | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/Docs/manual.texi b/Docs/manual.texi index fc6554a4d9f..6c41b2f68fe 100644 --- a/Docs/manual.texi +++ b/Docs/manual.texi @@ -35217,6 +35217,9 @@ In other words, you can't access the values of the old row from a @code{REPLACE} statement. In some old MySQL versions it appeared that you could do this, but that was a bug that has been corrected. +To be able to use @code{REPLACE} you must have @code{INSERT} and +@code{DELETE} privileges for the table. + When you use a @code{REPLACE} command, @code{mysql_affected_rows()} will return 2 if the new row replaced an old row. This is because one row was inserted and then the duplicate was deleted. @@ -50830,6 +50833,8 @@ Fixed some @code{ORDER BY ... DESC} problems with InnoDB. Fixed an inadvertently changed option (@code{--ignore-space}) back to the original @code{--ignore-spaces} in @code{mysqlclient}. (Both syntaxes will work). +@item +Don't require @code{UPDATE} privilege when using @code{REPLACE}. @end itemize @node News-4.0.4, News-4.0.3, News-4.0.5, News-4.0.x |