[MDEV-9084] Calling a stored function from a nested select from temporary table causes unpredictable behavior Created: 2015-11-05 Updated: 2017-04-20 Resolved: 2017-01-06 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Temporary, Stored routines |
| Affects Version/s: | 10.0.21, 10.0, 10.1 |
| Fix Version/s: | 10.0.29, 10.1.21 |
| Type: | Bug | Priority: | Major |
| Reporter: | Mark Punak | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | upstream-fixed | ||
| Environment: |
CentOS 7.1 |
||
| Issue Links: |
|
||||||||
| Description |
|
Using a Stored Procedure, creating a table and populating the table in a single statement, using a nested select as virtual table for the data, and having that nested select obtain data from a temporary table and call a stored function, causes the references to the temporary table to be lost on all runs after the first. Sequential calls fail with "1146 .Table test,tmpValues doesn't exist' Code to setup the test and duplicate as follows:
--------------------- Work arounds exist as follows:
|
| Comments |
| Comment by Elena Stepanova [ 2015-11-05 ] | |||||||||||||||||
|
Thanks for the report and the test case. Here is the revision where the problem appeared in MySQL:
|