summaryrefslogtreecommitdiff
path: root/mysql-test/r/ps_6bdb.result
diff options
context:
space:
mode:
authorunknown <mleich@mysql.com>2004-12-13 21:00:43 +0100
committerunknown <mleich@mysql.com>2004-12-13 21:00:43 +0100
commit86abd1fc21ed0c968cf4bcc4d886909fab40c893 (patch)
tree3be59cd34bba6c611154da5b92ac083a51b1e9d0 /mysql-test/r/ps_6bdb.result
parent1c4b001ca1e6260d9b18fb9ae1501a4cb8bfc60b (diff)
downloadmariadb-git-86abd1fc21ed0c968cf4bcc4d886909fab40c893.tar.gz
Small bug fix
ps-modify1 used the user variables @1, @2, @100 set within ps_query and ps_modify. That architecture was wrong, because the dependence of ps_modify1 on ps_query and ps_modify makes the test script maintenance and the use of these test cases during bug fixing/ debugging of single sub test cases very uncomfortable. Therefore these user variables (@1, @2, @100) are also set within ps-modify1. The result files of the test cases ps_2myisam, ps_3innodb, ps_4heap, ps_6bdb, ps_7ndb will be affected by that change and show 3 additional lines, but nothing else will change. mysql-test/include/ps_modify1.inc: Initialization of three user variables, with values derived from ps_query and ps_modify mysql-test/r/ps_2myisam.result: updated result set mysql-test/r/ps_3innodb.result: updated result set mysql-test/r/ps_4heap.result: updated result sset mysql-test/r/ps_6bdb.result: updated result set mysql-test/r/ps_7ndb.result: updated result set
Diffstat (limited to 'mysql-test/r/ps_6bdb.result')
-rw-r--r--mysql-test/r/ps_6bdb.result3
1 files changed, 3 insertions, 0 deletions
diff --git a/mysql-test/r/ps_6bdb.result b/mysql-test/r/ps_6bdb.result
index 5f2419bdda5..baf273c84c0 100644
--- a/mysql-test/r/ps_6bdb.result
+++ b/mysql-test/r/ps_6bdb.result
@@ -1671,6 +1671,9 @@ a b
1003 duplicate three
1004 duplicate four
delete from t1 where a >= 1000 ;
+set @1=1 ;
+set @2=2 ;
+set @100=100 ;
set @float=1.00;
set @five='five' ;
drop table if exists t2;