Bug #782 | HANDLER locks table for writing | ||
---|---|---|---|
Submitted: | 2 Jul 2003 9:16 | Modified: | 3 Jul 2003 4:36 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S2 (Serious) |
Version: | 4.0.13 | OS: | Linux (Redhat Linux) |
Assigned to: | Sergei Golubchik | CPU Architecture: | Any |
[2 Jul 2003 9:16]
[ name withheld ]
[3 Jul 2003 4:36]
Sergei Golubchik
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Manual states only that the table is not locked for reading on HANDLER OPEN. And that HANDLER can do dirty reads in two "HANDLER ... READ" commands, if the table was modified in-between. Manual does NOT say that one atomic HANDLER command can perform dirty reads or does not lock the table - and in fact it does lock.