| Bug #70793 | Temp table in stored proc on read replica behaves erratically | ||
|---|---|---|---|
| Submitted: | 31 Oct 2013 16:25 | Modified: | 1 Nov 2013 18:51 | 
| Reporter: | Whit Marbut | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) | 
| Version: | 5.5.27 | OS: | Linux (Ubuntu 12.04 LTS) | 
| Assigned to: | CPU Architecture: | Any | |
| Tags: | linux, readonly, stored procedure, temporary table, ubuntu | ||
   [31 Oct 2013 16:25]
   Whit Marbut        
  
 
   [31 Oct 2013 16:39]
   Whit Marbut        
  Meant to paste CREATE TEMPORARY TABLE my_temp (id INT(11), person_name VARCHAR(255)) into the PASS example and not INSERT INTO my_temp (id, person_name) VALUES (2, 'testing_a_bug');
   [1 Nov 2013 3:15]
   Whit Marbut        
  This problem can be abated by using the `TEMPORARY` keyword in the `DROP TABLE` command. See http://stackoverflow.com/a/19719174/701368
   [1 Nov 2013 18:51]
   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 DROP TABLE without word "TEMPORARY" fails even if used without stored procedure. This is not a bug.
