Bug #55905 | Transactional temporary tables do not work under --read-only, Part II | ||
---|---|---|---|
Submitted: | 11 Aug 2010 7:56 | Modified: | 11 Aug 2010 10:38 |
Reporter: | Holger Thiel | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Security: Privileges | Severity: | S2 (Serious) |
Version: | 5.1.49 (InnoDB Plugin) | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | innodb, read-only, replication, temporary tables, transactions |
[11 Aug 2010 7:56]
Holger Thiel
[11 Aug 2010 8:04]
Holger Thiel
It seems to be again a storage issue. mysql> CREATE TEMPORARY TABLE `tmptbl`.`peterstable`( step varchar(50), reactiontime bigint, type varchar(50) ) ENGINE=MyISAM; Query OK, 0 rows affected (0.00 sec) mysql> insert into `tmptbl`.`peterstable` values ('LINE_TERMINATION_CONFIRMED', 4, 'WITA_LINE_TERMINATION'); Query OK, 1 row affected (0.00 sec)
[11 Aug 2010 10:38]
Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Fix of bug #33669 had not been pushed into 5.1 tree. See comment "[21 Jan 12:26] Konstantin Osipov" for details.