summaryrefslogtreecommitdiff
path: root/mysql-test/r/trigger.result
diff options
context:
space:
mode:
authorAlexander Nozdrin <alexander.nozdrin@oracle.com>2011-03-10 11:07:57 +0300
committerAlexander Nozdrin <alexander.nozdrin@oracle.com>2011-03-10 11:07:57 +0300
commit5653a71d3ec08e64098b430fcd7def790e249fa3 (patch)
tree5fa3a4d25f85e9fca1dd6180886d6e2bd4399afb /mysql-test/r/trigger.result
parent0b7e6f81afe24f4734b3d8ce5d85411609f8d3a0 (diff)
downloadmariadb-git-5653a71d3ec08e64098b430fcd7def790e249fa3.tar.gz
Patch for Bug#11765684 (58674: SP-cache does not detect changes in
pre-locking list caused by triggers). The thing is that CREATE TRIGGER / DROP TRIGGER may actually change pre-locking list of (some) stored routines. The SP-cache does not detect such changes. Thus if sp_head-instance is cached in SP-cache, subsequent executions of the cached sp_head will use inaccurate pre-locking list. The patch is to invalidate SP-cache on CREATE TRIGGER / DROP TRIGGER.
Diffstat (limited to 'mysql-test/r/trigger.result')
-rw-r--r--mysql-test/r/trigger.result1
1 files changed, 0 insertions, 1 deletions
diff --git a/mysql-test/r/trigger.result b/mysql-test/r/trigger.result
index b24c5b87fa0..11e0d7313b7 100644
--- a/mysql-test/r/trigger.result
+++ b/mysql-test/r/trigger.result
@@ -821,7 +821,6 @@ drop trigger t1_bi;
create trigger t1_bi after insert on t1 for each row insert into t3 values (new.id);
execute stmt1;
call p1();
-ERROR 42S02: Table 'test.t3' doesn't exist
deallocate prepare stmt1;
drop procedure p1;
drop table t1, t2, t3;