~drizzle-trunk/drizzle/development

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
#############################################################################
# Original Author: JBM                                                      #
# Original Date: Aug/18/2005                                                #
#############################################################################
# TEST: To test the UUID() in rbr                                           #
#############################################################################

# Begin clean up test section
connection master;

--disable_warnings
DROP PROCEDURE IF EXISTS test.p1;
DROP TABLE IF EXISTS test.t1;
--enable_warnings

# Section 1 test 

eval CREATE TABLE test.t1 (a INT, blob_column LONGBLOB, vchar_column VARCHAR(100), PRIMARY KEY(a)) engine=$engine_type;
INSERT INTO test.t1  VALUES(1,UUID(),UUID());
delimiter |;
create procedure test.p1()
begin
  INSERT INTO test.t1  VALUES(2,UUID(),UUID());
  INSERT INTO test.t1  VALUES(3,UUID(),UUID());
end|
delimiter ;|

CALL test.p1();

# Now the same thing with a function

delimiter |;
create function test.fn1(x int)
       returns int
begin
       insert into t1 values (4+x,UUID(),UUID());
       insert into t1 values (5+x,UUID(),UUID());
       return 0;
end|

delimiter ;|
# test both in SELECT and in INSERT
select fn1(0);
eval create table t2 (a int) engine=$engine_type;
insert into t2 values(fn1(2));

sync_slave_with_master;
SHOW CREATE TABLE test.t1;

# Dump the databases and so we can see if they match
# Another method would be to use SELECT INTO OUTFILE on master,
# then LOAD DATA INFILE in slave, and use a query to compare.
# This would have the advantage that it would not assume
# the system has a 'diff'
--exec $MYSQL_DUMP --compact --order-by-primary --skip-extended-insert --no-create-info test > $MYSQLTEST_VARDIR/tmp/rpl_row_UUID_master.sql
--exec $MYSQL_DUMP_SLAVE --compact --order-by-primary --skip-extended-insert --no-create-info test > $MYSQLTEST_VARDIR/tmp/rpl_row_UUID_slave.sql

connection master;
# Let's cleanup

DROP PROCEDURE test.p1;
DROP FUNCTION test.fn1;
DROP TABLE test.t1;
DROP TABLE test.t2;

# Let's compare. Note: If they match test will pass, if they do not match
# the test will show that the diff statement failed and not reject file
# will be created. You will need to go to the mysql-test dir and diff
# the files your self to see what is not matching :-)

diff_files $MYSQLTEST_VARDIR/tmp/rpl_row_UUID_master.sql $MYSQLTEST_VARDIR/tmp/rpl_row_UUID_slave.sql;

# Cleanup dump files.
# Long-term "system rm" is not portable; we could live without
# this cleanup as no other test will use these files and they'll
# be removed at next testsuite run.

# End of 5.0 test case
-- source include/master-slave-end.inc