From 3f619478f796eddbba6e39502fe941b285dd97b1 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 20:00:34 +0200 Subject: Adding upstream version 1:10.11.6. Signed-off-by: Daniel Baumann --- mysql-test/suite/sql_sequence/binlog.test | 40 +++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 mysql-test/suite/sql_sequence/binlog.test (limited to 'mysql-test/suite/sql_sequence/binlog.test') diff --git a/mysql-test/suite/sql_sequence/binlog.test b/mysql-test/suite/sql_sequence/binlog.test new file mode 100644 index 00000000..70d28038 --- /dev/null +++ b/mysql-test/suite/sql_sequence/binlog.test @@ -0,0 +1,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; -- cgit v1.2.3