Bug #9355 | Locked aliases not recognized during queries | ||
---|---|---|---|
Submitted: | 23 Mar 2005 12:12 | Modified: | 28 Mar 2005 17:50 |
Reporter: | Huns | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S2 (Serious) |
Version: | 4.0.20-log | OS: | Linux (Debian/kernel 2.4.29) |
Assigned to: | Sergei Golubchik | CPU Architecture: | Any |
[23 Mar 2005 12:12]
Huns
[28 Mar 2005 17:50]
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 Additional info: See the manual for LOCK TABLES. http://dev.mysql.com/doc/mysql/en/lock-tables.html In particular, note the following: " if you lock a table using an alias, you must refer to it in your queries using that alias: mysql> LOCK TABLE t AS myalias READ; mysql> SELECT * FROM t; ERROR 1100: Table 't' was not locked with LOCK TABLES mysql> SELECT * FROM t AS myalias; " See, "SELECT * FROM t AS myalias" and *not* "SELECT * FROM myalias". As you cannot alias a table in INSERT (no syntax like INSERT INTO TABLE t1 AS myalias) there's no way you can insert into a table that was locked by alias.