mysql-test/suite/sql_sequence/binlog.test


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

--source include/have_sequence.inc
--source include/have_binlog_format_mixed_or_row.inc
--source include/binlog_start_pos.inc

#
# Testing binary logging of sequences
#

--disable_query_log
reset master; # get rid of previous tests binlog
--enable_query_log

create or replace sequence s1 cache 3;
--disable_ps2_protocol
select next value for s1, minimum_value from s1 where maximum_value> 1;
select next value for s1, minimum_value from s1 where maximum_value> 2;
select next value for s1, minimum_value from s1 where maximum_value> 3;
select next value for s1, minimum_value from s1 where maximum_value> 4;
--enable_ps2_protocol

#
# Alter sequence
#
alter sequence s1 maxvalue 1000;

# MDEV-24617 OPTIMIZE on a sequence causes unexpected
# ER_BINLOG_UNSAFE_STATEMENT The test below verifies no unsafe
# warnings anymore for any relavant commands that like OPTIMIZE can
# not produce ROW format events therefore the unsafe warning either.
optimize table s1;
analyze table s1;
repair table s1;
check table s1;
rename table s1 to tmp_s;
rename table tmp_s to s1;

drop sequence s1;

--let $binlog_file = LAST
source include/show_binlog_events.inc;