Bug #54560 | Docs for REPLACE are not accurate | ||
---|---|---|---|
Submitted: | 16 Jun 2010 18:58 | Modified: | 22 Jun 2010 18:28 |
Reporter: | Mark Callaghan | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.1, 4.1, 5.0, 5.6.99 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | innodb, REPLACE |
[16 Jun 2010 18:58]
Mark Callaghan
[16 Jun 2010 19:16]
Sveta Smirnova
Thank you for the report. Verified as described.
[22 Jun 2010 18:28]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. After discussing with Runtime, added this to REPLACE section: It is possible that in the case of a duplicate-key error, a storage engine may perform the REPLACE as an update rather than a delete plus insert, but the semantics are the same. There are no user-visible effects other than a possible difference in how the storage engine increments Handler_xxx status variables.