mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-19 21:42:35 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test/r/mysqlbinlog.result

193 lines
6.7 KiB
Text
Raw Normal View History

Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
set timestamp=1000000000;
Making DROP TABLE IF EXISTS, DROP DATABASE IF EXISTS, DELETE FROM, UPDATE be logged to binlog even if they changed nothing, and a test for this. This is useful when users use these commands to clean up their master and slave by issuing one command on master (assume master and slave have slightly different data for some reason and you want to clean up both). Note that I have not changed multi-table DELETE and multi-table UPDATE because their error-reporting mechanism is more complicated.
2004-06-09 16:07:01 +02:00
drop table if exists t1,t2;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
create table t1 (word varchar(20));
create table t2 (id int auto_increment not null primary key);
insert into t1 values ("abirvalg");
insert into t2 values ();
Make it possible to run mysql-test-run.pl with default test suite in different vardir.
2006-01-24 08:30:54 +01:00
load data infile '../std_data_ln/words.dat' into table t1;
load data infile '../std_data_ln/words.dat' into table t1;
load data infile '../std_data_ln/words.dat' into table t1;
load data infile '../std_data_ln/words.dat' into table t1;
load data infile '../std_data_ln/words.dat' into table t1;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
insert into t1 values ("Alas");
flush logs;
--- Local --
Post-merge fixes, some quite complex. client/mysqlbinlog.cc and sql/log_event.cc merged manually by guilhem.
2004-04-28 12:08:54 +02:00
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
post-review fixes. Now ROLLBACK is done in Format_description_log_event
2005-02-17 13:52:16 +01:00
ROLLBACK;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
use test;
After merge fixes Note: The following tests fails - fulltext (Sergei has promised to fix) - rpl_charset (Guilhem should fix) - rpl_timezone (Dimitray has promised to fix) Sanja needs to check out the calling of close_thread_tables() in sp_head.cc
2004-07-15 03:19:07 +02:00
SET TIMESTAMP=1000000000;
Now merge is done. For previous commit I had run only rpl* tests, here the other ones had a few surprises. Latest status: - all tests pass - all replication tests pass with Valgrind This is the final-final commit & push. Doc remains.
2003-12-20 00:38:30 +01:00
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=1, @@session.unique_checks=1;
SET @@session.sql_mode=0;
BUG#16217 forced to introduce a separate mysql client command to adopt its internal charset to one associated with currently being handled query. To note such a query can come from interactive client either. There was a discussion within replication team and Monty who's suggestion won. It avoids straightforward parsing of all `set' queries that could affect client side character set. According to the idea, mysql client does not parse `set' queries but rather cares of `charset new_cs_name' command. This command is generated by mysqlbinlog in form of exclaiming comment (Lars' suggestion) so that enlightened clients like `mysql' knows what to do with it. Interactive human can switch between many multi-byte charsets during the session providing the command explicitly. To note that setting new internal mysql's charset does not trigger sending any `SET' sql statement to the server.
2006-02-09 15:23:09 +01:00
/*!\C latin1 */;
WL#1062 "log charset info into all Query_log_event": we store 7 bytes (1 + 2*3) in every Query_log_event. In the future if users want binlog optimized for small size and less safe, we could add --binlog-no-charset (and binlog-no-sql-mode etc): charset info is something by design optional (even if for now we don't offer possibility to disable it): it's not a binlog format change. We try to reduce the number of get_charset() calls in the slave SQL thread to a minimum by caching the charset read from the previous event (which will often be equal to the one of the current event). We don't use SET ONE_SHOT for charset-aware repl (we still do for timezones, will be fixed later). No more errors if one changes the global value of charset vars on master or slave (as we log charset info in all Query_log_event). Not fixing Load_log_event as it will be rewritten soon by Dmitri. Testing how mysqlbinlog behaves in rpl_charset.test. mysqlbinlog needs to know where charset file is (to be able to convert a charset number found in binlog (e.g. in User_var_log_event) to a charset name); mysql-test-run needs to pass the correct value for this option to mysqlbinlog. Many result udpates (adding charset info into every event shifts log_pos in SHOW BINLOG EVENTS). Roughly the same job is to be done for timezones :)
2005-02-03 16:22:16 +01:00
SET @@session.character_set_client=8,@@session.collation_connection=8,@@session.collation_server=8;
Making DROP TABLE IF EXISTS, DROP DATABASE IF EXISTS, DELETE FROM, UPDATE be logged to binlog even if they changed nothing, and a test for this. This is useful when users use these commands to clean up their master and slave by issuing one command on master (assume master and slave have slightly different data for some reason and you want to clean up both). Note that I have not changed multi-table DELETE and multi-table UPDATE because their error-reporting mechanism is more complicated.
2004-06-09 16:07:01 +02:00
drop table if exists t1,t2;
SET TIMESTAMP=1000000000;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
create table t1 (word varchar(20));
SET TIMESTAMP=1000000000;
create table t2 (id int auto_increment not null primary key);
SET TIMESTAMP=1000000000;
insert into t1 values ("abirvalg");
SET INSERT_ID=1;
SET TIMESTAMP=1000000000;
insert into t2 values ();
WL#874 "Extended LOAD DATA". Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event
2005-03-16 02:32:47 +01:00
SET TIMESTAMP=1000000000;
Make it possible to run mysql-test-run.pl with default test suite in different vardir.
2006-01-24 08:30:54 +01:00
load data LOCAL INFILE 'MYSQLTEST_VARDIR/tmp/SQL_LOAD_MB-1-0' INTO table t1;
WL#874 "Extended LOAD DATA". Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event
2005-03-16 02:32:47 +01:00
SET TIMESTAMP=1000000000;
Make it possible to run mysql-test-run.pl with default test suite in different vardir.
2006-01-24 08:30:54 +01:00
load data LOCAL INFILE 'MYSQLTEST_VARDIR/tmp/SQL_LOAD_MB-2-0' INTO table t1;
WL#874 "Extended LOAD DATA". Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event
2005-03-16 02:32:47 +01:00
SET TIMESTAMP=1000000000;
Make it possible to run mysql-test-run.pl with default test suite in different vardir.
2006-01-24 08:30:54 +01:00
load data LOCAL INFILE 'MYSQLTEST_VARDIR/tmp/SQL_LOAD_MB-3-0' INTO table t1;
WL#874 "Extended LOAD DATA". Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event
2005-03-16 02:32:47 +01:00
SET TIMESTAMP=1000000000;
Make it possible to run mysql-test-run.pl with default test suite in different vardir.
2006-01-24 08:30:54 +01:00
load data LOCAL INFILE 'MYSQLTEST_VARDIR/tmp/SQL_LOAD_MB-4-0' INTO table t1;
Added clarification comment regarding added ROLLBACK to mysqlbinlog output
2005-09-21 14:27:41 +02:00
# End of log file
Tell the user that this ROLLBACK is added by mysqlbinlog (so that he does not wonder if it's present in binlog). This was brought up by Salle - thanks Salle.
2005-09-30 10:58:24 +02:00
ROLLBACK /* added by mysqlbinlog */;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
--- Broken LOAD DATA --
Post-merge fixes, some quite complex. client/mysqlbinlog.cc and sql/log_event.cc merged manually by guilhem.
2004-04-28 12:08:54 +02:00
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
use test;
SET TIMESTAMP=1000000000;
Now merge is done. For previous commit I had run only rpl* tests, here the other ones had a few surprises. Latest status: - all tests pass - all replication tests pass with Valgrind This is the final-final commit & push. Doc remains.
2003-12-20 00:38:30 +01:00
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=1, @@session.unique_checks=1;
SET @@session.sql_mode=0;
BUG#16217 forced to introduce a separate mysql client command to adopt its internal charset to one associated with currently being handled query. To note such a query can come from interactive client either. There was a discussion within replication team and Monty who's suggestion won. It avoids straightforward parsing of all `set' queries that could affect client side character set. According to the idea, mysql client does not parse `set' queries but rather cares of `charset new_cs_name' command. This command is generated by mysqlbinlog in form of exclaiming comment (Lars' suggestion) so that enlightened clients like `mysql' knows what to do with it. Interactive human can switch between many multi-byte charsets during the session providing the command explicitly. To note that setting new internal mysql's charset does not trigger sending any `SET' sql statement to the server.
2006-02-09 15:23:09 +01:00
/*!\C latin1 */;
WL#1062 "log charset info into all Query_log_event": we store 7 bytes (1 + 2*3) in every Query_log_event. In the future if users want binlog optimized for small size and less safe, we could add --binlog-no-charset (and binlog-no-sql-mode etc): charset info is something by design optional (even if for now we don't offer possibility to disable it): it's not a binlog format change. We try to reduce the number of get_charset() calls in the slave SQL thread to a minimum by caching the charset read from the previous event (which will often be equal to the one of the current event). We don't use SET ONE_SHOT for charset-aware repl (we still do for timezones, will be fixed later). No more errors if one changes the global value of charset vars on master or slave (as we log charset info in all Query_log_event). Not fixing Load_log_event as it will be rewritten soon by Dmitri. Testing how mysqlbinlog behaves in rpl_charset.test. mysqlbinlog needs to know where charset file is (to be able to convert a charset number found in binlog (e.g. in User_var_log_event) to a charset name); mysql-test-run needs to pass the correct value for this option to mysqlbinlog. Many result udpates (adding charset info into every event shifts log_pos in SHOW BINLOG EVENTS). Roughly the same job is to be done for timezones :)
2005-02-03 16:22:16 +01:00
SET @@session.character_set_client=8,@@session.collation_connection=8,@@session.collation_server=8;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
insert into t1 values ("Alas");
Added clarification comment regarding added ROLLBACK to mysqlbinlog output
2005-09-21 14:27:41 +02:00
# End of log file
Tell the user that this ROLLBACK is added by mysqlbinlog (so that he does not wonder if it's present in binlog). This was brought up by Salle - thanks Salle.
2005-09-30 10:58:24 +02:00
ROLLBACK /* added by mysqlbinlog */;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
--- --database --
Post-merge fixes, some quite complex. client/mysqlbinlog.cc and sql/log_event.cc merged manually by guilhem.
2004-04-28 12:08:54 +02:00
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
post-review fixes. Now ROLLBACK is done in Format_description_log_event
2005-02-17 13:52:16 +01:00
ROLLBACK;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
SET INSERT_ID=1;
Added clarification comment regarding added ROLLBACK to mysqlbinlog output
2005-09-21 14:27:41 +02:00
# End of log file
Tell the user that this ROLLBACK is added by mysqlbinlog (so that he does not wonder if it's present in binlog). This was brought up by Salle - thanks Salle.
2005-09-30 10:58:24 +02:00
ROLLBACK /* added by mysqlbinlog */;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
--- --position --
Post-merge fixes, some quite complex. client/mysqlbinlog.cc and sql/log_event.cc merged manually by guilhem.
2004-04-28 12:08:54 +02:00
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
use test;
SET TIMESTAMP=1000000000;
Now merge is done. For previous commit I had run only rpl* tests, here the other ones had a few surprises. Latest status: - all tests pass - all replication tests pass with Valgrind This is the final-final commit & push. Doc remains.
2003-12-20 00:38:30 +01:00
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=1, @@session.unique_checks=1;
SET @@session.sql_mode=0;
BUG#16217 forced to introduce a separate mysql client command to adopt its internal charset to one associated with currently being handled query. To note such a query can come from interactive client either. There was a discussion within replication team and Monty who's suggestion won. It avoids straightforward parsing of all `set' queries that could affect client side character set. According to the idea, mysql client does not parse `set' queries but rather cares of `charset new_cs_name' command. This command is generated by mysqlbinlog in form of exclaiming comment (Lars' suggestion) so that enlightened clients like `mysql' knows what to do with it. Interactive human can switch between many multi-byte charsets during the session providing the command explicitly. To note that setting new internal mysql's charset does not trigger sending any `SET' sql statement to the server.
2006-02-09 15:23:09 +01:00
/*!\C latin1 */;
WL#1062 "log charset info into all Query_log_event": we store 7 bytes (1 + 2*3) in every Query_log_event. In the future if users want binlog optimized for small size and less safe, we could add --binlog-no-charset (and binlog-no-sql-mode etc): charset info is something by design optional (even if for now we don't offer possibility to disable it): it's not a binlog format change. We try to reduce the number of get_charset() calls in the slave SQL thread to a minimum by caching the charset read from the previous event (which will often be equal to the one of the current event). We don't use SET ONE_SHOT for charset-aware repl (we still do for timezones, will be fixed later). No more errors if one changes the global value of charset vars on master or slave (as we log charset info in all Query_log_event). Not fixing Load_log_event as it will be rewritten soon by Dmitri. Testing how mysqlbinlog behaves in rpl_charset.test. mysqlbinlog needs to know where charset file is (to be able to convert a charset number found in binlog (e.g. in User_var_log_event) to a charset name); mysql-test-run needs to pass the correct value for this option to mysqlbinlog. Many result udpates (adding charset info into every event shifts log_pos in SHOW BINLOG EVENTS). Roughly the same job is to be done for timezones :)
2005-02-03 16:22:16 +01:00
SET @@session.character_set_client=8,@@session.collation_connection=8,@@session.collation_server=8;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
insert into t1 values ("Alas");
Added clarification comment regarding added ROLLBACK to mysqlbinlog output
2005-09-21 14:27:41 +02:00
# End of log file
Tell the user that this ROLLBACK is added by mysqlbinlog (so that he does not wonder if it's present in binlog). This was brought up by Salle - thanks Salle.
2005-09-30 10:58:24 +02:00
ROLLBACK /* added by mysqlbinlog */;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
--- Remote --
Post-merge fixes, some quite complex. client/mysqlbinlog.cc and sql/log_event.cc merged manually by guilhem.
2004-04-28 12:08:54 +02:00
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
post-review fixes. Now ROLLBACK is done in Format_description_log_event
2005-02-17 13:52:16 +01:00
ROLLBACK;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
use test;
SET TIMESTAMP=1000000000;
Now merge is done. For previous commit I had run only rpl* tests, here the other ones had a few surprises. Latest status: - all tests pass - all replication tests pass with Valgrind This is the final-final commit & push. Doc remains.
2003-12-20 00:38:30 +01:00
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=1, @@session.unique_checks=1;
SET @@session.sql_mode=0;
BUG#16217 forced to introduce a separate mysql client command to adopt its internal charset to one associated with currently being handled query. To note such a query can come from interactive client either. There was a discussion within replication team and Monty who's suggestion won. It avoids straightforward parsing of all `set' queries that could affect client side character set. According to the idea, mysql client does not parse `set' queries but rather cares of `charset new_cs_name' command. This command is generated by mysqlbinlog in form of exclaiming comment (Lars' suggestion) so that enlightened clients like `mysql' knows what to do with it. Interactive human can switch between many multi-byte charsets during the session providing the command explicitly. To note that setting new internal mysql's charset does not trigger sending any `SET' sql statement to the server.
2006-02-09 15:23:09 +01:00
/*!\C latin1 */;
WL#1062 "log charset info into all Query_log_event": we store 7 bytes (1 + 2*3) in every Query_log_event. In the future if users want binlog optimized for small size and less safe, we could add --binlog-no-charset (and binlog-no-sql-mode etc): charset info is something by design optional (even if for now we don't offer possibility to disable it): it's not a binlog format change. We try to reduce the number of get_charset() calls in the slave SQL thread to a minimum by caching the charset read from the previous event (which will often be equal to the one of the current event). We don't use SET ONE_SHOT for charset-aware repl (we still do for timezones, will be fixed later). No more errors if one changes the global value of charset vars on master or slave (as we log charset info in all Query_log_event). Not fixing Load_log_event as it will be rewritten soon by Dmitri. Testing how mysqlbinlog behaves in rpl_charset.test. mysqlbinlog needs to know where charset file is (to be able to convert a charset number found in binlog (e.g. in User_var_log_event) to a charset name); mysql-test-run needs to pass the correct value for this option to mysqlbinlog. Many result udpates (adding charset info into every event shifts log_pos in SHOW BINLOG EVENTS). Roughly the same job is to be done for timezones :)
2005-02-03 16:22:16 +01:00
SET @@session.character_set_client=8,@@session.collation_connection=8,@@session.collation_server=8;
After merge fixes Note: The following tests fails - fulltext (Sergei has promised to fix) - rpl_charset (Guilhem should fix) - rpl_timezone (Dimitray has promised to fix) Sanja needs to check out the calling of close_thread_tables() in sp_head.cc
2004-07-15 03:19:07 +02:00
drop table if exists t1,t2;
SET TIMESTAMP=1000000000;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
create table t1 (word varchar(20));
SET TIMESTAMP=1000000000;
create table t2 (id int auto_increment not null primary key);
SET TIMESTAMP=1000000000;
insert into t1 values ("abirvalg");
SET INSERT_ID=1;
SET TIMESTAMP=1000000000;
insert into t2 values ();
WL#874 "Extended LOAD DATA". Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event
2005-03-16 02:32:47 +01:00
SET TIMESTAMP=1000000000;
Make it possible to run mysql-test-run.pl with default test suite in different vardir.
2006-01-24 08:30:54 +01:00
load data LOCAL INFILE 'MYSQLTEST_VARDIR/tmp/SQL_LOAD_MB-1-2' INTO table t1;
WL#874 "Extended LOAD DATA". Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event
2005-03-16 02:32:47 +01:00
SET TIMESTAMP=1000000000;
Make it possible to run mysql-test-run.pl with default test suite in different vardir.
2006-01-24 08:30:54 +01:00
load data LOCAL INFILE 'MYSQLTEST_VARDIR/tmp/SQL_LOAD_MB-2-2' INTO table t1;
WL#874 "Extended LOAD DATA". Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event
2005-03-16 02:32:47 +01:00
SET TIMESTAMP=1000000000;
Make it possible to run mysql-test-run.pl with default test suite in different vardir.
2006-01-24 08:30:54 +01:00
load data LOCAL INFILE 'MYSQLTEST_VARDIR/tmp/SQL_LOAD_MB-3-2' INTO table t1;
WL#874 "Extended LOAD DATA". Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event
2005-03-16 02:32:47 +01:00
SET TIMESTAMP=1000000000;
Make it possible to run mysql-test-run.pl with default test suite in different vardir.
2006-01-24 08:30:54 +01:00
load data LOCAL INFILE 'MYSQLTEST_VARDIR/tmp/SQL_LOAD_MB-4-2' INTO table t1;
Added clarification comment regarding added ROLLBACK to mysqlbinlog output
2005-09-21 14:27:41 +02:00
# End of log file
Tell the user that this ROLLBACK is added by mysqlbinlog (so that he does not wonder if it's present in binlog). This was brought up by Salle - thanks Salle.
2005-09-30 10:58:24 +02:00
ROLLBACK /* added by mysqlbinlog */;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
--- Broken LOAD DATA --
Post-merge fixes, some quite complex. client/mysqlbinlog.cc and sql/log_event.cc merged manually by guilhem.
2004-04-28 12:08:54 +02:00
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
use test;
SET TIMESTAMP=1000000000;
Now merge is done. For previous commit I had run only rpl* tests, here the other ones had a few surprises. Latest status: - all tests pass - all replication tests pass with Valgrind This is the final-final commit & push. Doc remains.
2003-12-20 00:38:30 +01:00
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=1, @@session.unique_checks=1;
SET @@session.sql_mode=0;
BUG#16217 forced to introduce a separate mysql client command to adopt its internal charset to one associated with currently being handled query. To note such a query can come from interactive client either. There was a discussion within replication team and Monty who's suggestion won. It avoids straightforward parsing of all `set' queries that could affect client side character set. According to the idea, mysql client does not parse `set' queries but rather cares of `charset new_cs_name' command. This command is generated by mysqlbinlog in form of exclaiming comment (Lars' suggestion) so that enlightened clients like `mysql' knows what to do with it. Interactive human can switch between many multi-byte charsets during the session providing the command explicitly. To note that setting new internal mysql's charset does not trigger sending any `SET' sql statement to the server.
2006-02-09 15:23:09 +01:00
/*!\C latin1 */;
WL#1062 "log charset info into all Query_log_event": we store 7 bytes (1 + 2*3) in every Query_log_event. In the future if users want binlog optimized for small size and less safe, we could add --binlog-no-charset (and binlog-no-sql-mode etc): charset info is something by design optional (even if for now we don't offer possibility to disable it): it's not a binlog format change. We try to reduce the number of get_charset() calls in the slave SQL thread to a minimum by caching the charset read from the previous event (which will often be equal to the one of the current event). We don't use SET ONE_SHOT for charset-aware repl (we still do for timezones, will be fixed later). No more errors if one changes the global value of charset vars on master or slave (as we log charset info in all Query_log_event). Not fixing Load_log_event as it will be rewritten soon by Dmitri. Testing how mysqlbinlog behaves in rpl_charset.test. mysqlbinlog needs to know where charset file is (to be able to convert a charset number found in binlog (e.g. in User_var_log_event) to a charset name); mysql-test-run needs to pass the correct value for this option to mysqlbinlog. Many result udpates (adding charset info into every event shifts log_pos in SHOW BINLOG EVENTS). Roughly the same job is to be done for timezones :)
2005-02-03 16:22:16 +01:00
SET @@session.character_set_client=8,@@session.collation_connection=8,@@session.collation_server=8;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
insert into t1 values ("Alas");
Added clarification comment regarding added ROLLBACK to mysqlbinlog output
2005-09-21 14:27:41 +02:00
# End of log file
Tell the user that this ROLLBACK is added by mysqlbinlog (so that he does not wonder if it's present in binlog). This was brought up by Salle - thanks Salle.
2005-09-30 10:58:24 +02:00
ROLLBACK /* added by mysqlbinlog */;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
--- --database --
Post-merge fixes, some quite complex. client/mysqlbinlog.cc and sql/log_event.cc merged manually by guilhem.
2004-04-28 12:08:54 +02:00
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
post-review fixes. Now ROLLBACK is done in Format_description_log_event
2005-02-17 13:52:16 +01:00
ROLLBACK;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
SET INSERT_ID=1;
Added clarification comment regarding added ROLLBACK to mysqlbinlog output
2005-09-21 14:27:41 +02:00
# End of log file
Tell the user that this ROLLBACK is added by mysqlbinlog (so that he does not wonder if it's present in binlog). This was brought up by Salle - thanks Salle.
2005-09-30 10:58:24 +02:00
ROLLBACK /* added by mysqlbinlog */;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
--- --position --
Post-merge fixes, some quite complex. client/mysqlbinlog.cc and sql/log_event.cc merged manually by guilhem.
2004-04-28 12:08:54 +02:00
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
use test;
SET TIMESTAMP=1000000000;
Now merge is done. For previous commit I had run only rpl* tests, here the other ones had a few surprises. Latest status: - all tests pass - all replication tests pass with Valgrind This is the final-final commit & push. Doc remains.
2003-12-20 00:38:30 +01:00
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=1, @@session.unique_checks=1;
SET @@session.sql_mode=0;
BUG#16217 forced to introduce a separate mysql client command to adopt its internal charset to one associated with currently being handled query. To note such a query can come from interactive client either. There was a discussion within replication team and Monty who's suggestion won. It avoids straightforward parsing of all `set' queries that could affect client side character set. According to the idea, mysql client does not parse `set' queries but rather cares of `charset new_cs_name' command. This command is generated by mysqlbinlog in form of exclaiming comment (Lars' suggestion) so that enlightened clients like `mysql' knows what to do with it. Interactive human can switch between many multi-byte charsets during the session providing the command explicitly. To note that setting new internal mysql's charset does not trigger sending any `SET' sql statement to the server.
2006-02-09 15:23:09 +01:00
/*!\C latin1 */;
WL#1062 "log charset info into all Query_log_event": we store 7 bytes (1 + 2*3) in every Query_log_event. In the future if users want binlog optimized for small size and less safe, we could add --binlog-no-charset (and binlog-no-sql-mode etc): charset info is something by design optional (even if for now we don't offer possibility to disable it): it's not a binlog format change. We try to reduce the number of get_charset() calls in the slave SQL thread to a minimum by caching the charset read from the previous event (which will often be equal to the one of the current event). We don't use SET ONE_SHOT for charset-aware repl (we still do for timezones, will be fixed later). No more errors if one changes the global value of charset vars on master or slave (as we log charset info in all Query_log_event). Not fixing Load_log_event as it will be rewritten soon by Dmitri. Testing how mysqlbinlog behaves in rpl_charset.test. mysqlbinlog needs to know where charset file is (to be able to convert a charset number found in binlog (e.g. in User_var_log_event) to a charset name); mysql-test-run needs to pass the correct value for this option to mysqlbinlog. Many result udpates (adding charset info into every event shifts log_pos in SHOW BINLOG EVENTS). Roughly the same job is to be done for timezones :)
2005-02-03 16:22:16 +01:00
SET @@session.character_set_client=8,@@session.collation_connection=8,@@session.collation_server=8;
Test for mysqlbinlog Particularly for BUG#1340 mysqlbinlog coredumps when reading Exec event without seeing Create_file event before
2003-09-24 21:25:58 +02:00
insert into t1 values ("Alas");
Added clarification comment regarding added ROLLBACK to mysqlbinlog output
2005-09-21 14:27:41 +02:00
# End of log file
Tell the user that this ROLLBACK is added by mysqlbinlog (so that he does not wonder if it's present in binlog). This was brought up by Salle - thanks Salle.
2005-09-30 10:58:24 +02:00
ROLLBACK /* added by mysqlbinlog */;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
Bug#7853 (mysqlbinlog does not accept input from stdin) The utility 'mysqlbinlog' now accepts input from stdin. It can now be used to read the output from, e.g., 'zcat' or other utility.
2005-02-04 14:29:54 +01:00
--- reading stdin --
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
post-review fixes. Now ROLLBACK is done in Format_description_log_event
2005-02-17 13:52:16 +01:00
ROLLBACK;
Bug#7853 (mysqlbinlog does not accept input from stdin) The utility 'mysqlbinlog' now accepts input from stdin. It can now be used to read the output from, e.g., 'zcat' or other utility.
2005-02-04 14:29:54 +01:00
use test;
portability fixes
2005-02-20 20:08:33 +01:00
SET TIMESTAMP=1108844556;
Bug#7853 (mysqlbinlog does not accept input from stdin) The utility 'mysqlbinlog' now accepts input from stdin. It can now be used to read the output from, e.g., 'zcat' or other utility.
2005-02-04 14:29:54 +01:00
BEGIN;
portability fixes
2005-02-20 20:08:33 +01:00
SET TIMESTAMP=1108844555;
insert t1 values (1);
Added clarification comment regarding added ROLLBACK to mysqlbinlog output
2005-09-21 14:27:41 +02:00
# End of log file
Tell the user that this ROLLBACK is added by mysqlbinlog (so that he does not wonder if it's present in binlog). This was brought up by Salle - thanks Salle.
2005-09-30 10:58:24 +02:00
ROLLBACK /* added by mysqlbinlog */;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
Bug#7853 (mysqlbinlog does not accept input from stdin) The utility 'mysqlbinlog' now accepts input from stdin. It can now be used to read the output from, e.g., 'zcat' or other utility.
2005-02-04 14:29:54 +01:00
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
Bug#7853 (mysqlbinlog does not accept input from stdin) The utility 'mysqlbinlog' now accepts input from stdin. It can now be used to read the output from, e.g., 'zcat' or other utility.
2005-02-04 14:29:54 +01:00
use test;
portability fixes
2005-02-20 20:08:33 +01:00
SET TIMESTAMP=1108844556;
Bug#7853 (mysqlbinlog does not accept input from stdin) The utility 'mysqlbinlog' now accepts input from stdin. It can now be used to read the output from, e.g., 'zcat' or other utility.
2005-02-04 14:29:54 +01:00
BEGIN;
portability fixes
2005-02-20 20:08:33 +01:00
SET TIMESTAMP=1108844555;
insert t1 values (1);
Added clarification comment regarding added ROLLBACK to mysqlbinlog output
2005-09-21 14:27:41 +02:00
# End of log file
Tell the user that this ROLLBACK is added by mysqlbinlog (so that he does not wonder if it's present in binlog). This was brought up by Salle - thanks Salle.
2005-09-30 10:58:24 +02:00
ROLLBACK /* added by mysqlbinlog */;
result fixes after my change to mysqlbinlog (which was accidentally pushed some minutes ago)
2005-02-23 19:59:25 +01:00
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
BUG#16217 forced to introduce a separate mysql client command to adopt its internal charset to one associated with currently being handled query. To note such a query can come from interactive client either. There was a discussion within replication team and Monty who's suggestion won. It avoids straightforward parsing of all `set' queries that could affect client side character set. According to the idea, mysql client does not parse `set' queries but rather cares of `charset new_cs_name' command. This command is generated by mysqlbinlog in form of exclaiming comment (Lars' suggestion) so that enlightened clients like `mysql' knows what to do with it. Interactive human can switch between many multi-byte charsets during the session providing the command explicitly. To note that setting new internal mysql's charset does not trigger sending any `SET' sql statement to the server.
2006-02-09 15:23:09 +01:00
flush logs;
create table t3 (f text character set utf8);
create table t4 (f text character set cp932);
flush logs;
rename table t3 to t03, t4 to t04;
select HEX(f) from t03;
HEX(f)
E382BD
select HEX(f) from t3;
HEX(f)
E382BD
select HEX(f) from t04;
HEX(f)
835C
select HEX(f) from t4;
HEX(f)
835C
drop table t1, t2, t03, t04, t3, t4;
Reference in a new issue Copy permalink