mirror of
https://github.com/MariaDB/server.git
synced 2025-05-05 16:59:35 +03:00
5f75c8f5b4
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
client/mysqlbinlog.cc:
Added support of two new binary log events Begin_load_query_log_event and
Execute_load_query_log_Event which are used to replicate LOAD DATA INFILE.
mysql-test/r/ctype_ucs.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results and made it more robust for future similar
changes.
mysql-test/r/insert_select.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results and made it more robust for future similar
changes.
mysql-test/r/loaddata.result:
Added tests for new LOAD DATA features.
mysql-test/r/mix_innodb_myisam_binlog.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results (don't dare to get rid from binlog positions
completely since it seems that this test uses them).
mysql-test/r/mysqlbinlog.result:
New approach for binlogging of LOAD DATA statement. Now we store it as
usual query and rewrite part in which file is specified when needed.
So now mysqlbinlog output for LOAD DATA much more closer to its initial
form. Updated test'd results accordingly.
mysql-test/r/mysqldump.result:
Made test more robust to other tests failures.
mysql-test/r/rpl000015.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_change_master.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results.
mysql-test/r/rpl_charset.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly
mysql-test/r/rpl_deadlock.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly
mysql-test/r/rpl_error_ignored_table.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results and made it more robust for future similar
changes.
mysql-test/r/rpl_flush_log_loop.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_flush_tables.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results and made it more robust for future similar
changes.
mysql-test/r/rpl_loaddata.result:
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...
Updated test's results wwith new binlog positions.
mysql-test/r/rpl_loaddata_rule_m.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results and made it more robust for future similar
changes.
Since now LOAD DATA is replicated much in the same way as usual query
--binlog_do/ignore_db work for it inthe same way as for usual queries.
mysql-test/r/rpl_loaddata_rule_s.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_loaddatalocal.result:
Added nice test for case when it is important that LOAD DATA LOCAL
ignores duplicates.
mysql-test/r/rpl_log.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly (don't dare to get rid from binlog
positions completely since it seems that this test uses them).
mysql-test/r/rpl_log_pos.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_max_relay_size.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_multi_query.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_relayrotate.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_replicate_do.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_reset_slave.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_rotate_logs.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_server_id1.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_server_id2.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly.
mysql-test/r/rpl_temporary.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results and made it more robust for future similar
changes.
mysql-test/r/rpl_timezone.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results and made it more robust for future similar
changes.
mysql-test/r/rpl_until.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results accordingly and tweaked test a bit to bring it
back to good shape.
mysql-test/r/rpl_user_variables.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results and made it more robust for future similar
changes.
mysql-test/r/user_var.result:
Addition of two new types of binary log events shifted binlog positions.
Updated test's results and made it more robust for future similar
changes.
mysql-test/t/ctype_ucs.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly and made it more robust for future similar
changes.
mysql-test/t/insert_select.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly and made it more robust for future similar
changes.
mysql-test/t/loaddata.test:
Added test cases for new LOAD DATA functionality.
mysql-test/t/mix_innodb_myisam_binlog.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly.
mysql-test/t/mysqlbinlog.test:
New way of replicating LOAD DATA local. 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...
Thus we need new binlog positions for LOAD DATA events.
mysql-test/t/mysqlbinlog2.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly.
mysql-test/t/mysqldump.test:
Made test more robust for failures of other tests.
mysql-test/t/rpl_charset.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly.
mysql-test/t/rpl_deadlock.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly.
mysql-test/t/rpl_error_ignored_table.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly and made it more robust for future similar
changes.
mysql-test/t/rpl_flush_tables.test:
Addition of two new types of binary log events shifted binlog positions.
Made test more robust for future similar changes.
mysql-test/t/rpl_loaddata.test:
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...
Apropritely updated comments in test.
mysql-test/t/rpl_loaddata_rule_m.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly and made it more robust for future similar
changes.
Since now LOAD DATA is replicated much in the same way as usual query
--binlog_do/ignore_db work for it inthe same way as for usual queries.
mysql-test/t/rpl_loaddata_rule_s.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly.
mysql-test/t/rpl_loaddatalocal.test:
Added nice test for case when it is important that LOAD DATA LOCAL
ignores duplicates.
mysql-test/t/rpl_log.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly (don't dare to get rid from binlog positions
completely since it seems that this test uses them).
mysql-test/t/rpl_log_pos.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly.
mysql-test/t/rpl_multi_query.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly.
mysql-test/t/rpl_temporary.test:
Addition of two new types of binary log events shifted binlog positions.
Made test more robust for future similar changes.
mysql-test/t/rpl_timezone.test:
Addition of two new types of binary log events shifted binlog positions.
Made test more robust for future similar changes.
mysql-test/t/rpl_until.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly and tweaked it a bit to bring it back to good
shape.
mysql-test/t/rpl_user_variables.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly and made it more robust for future similar
changes.
mysql-test/t/user_var.test:
Addition of two new types of binary log events shifted binlog positions.
Updated test accordingly and made it more robust for future similar
changes.
sql/item_func.cc:
Added Item_user_var_as_out_param class that represents user variable
which used as out parameter in LOAD DATA.
Moved code from Item_func_set_user_var::update_hash() function to
separate static function to be able to reuse it in this new class.
sql/item_func.h:
Added Item_user_var_as_out_param class that represents user variable
which used as out parameter in LOAD DATA.
sql/log_event.cc:
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.
sql/log_event.h:
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.
sql/mysql_priv.h:
Now mysql_load() has two more arguments. They are needed to pass list of
columns and corresponding expressions from new LOAD DATA's SET clause.
sql/share/errmsg.txt:
Added new error message which is used to forbid loading of data from
fixed length rows to variables.
sql/sql_lex.h:
Added LEX::fname_start/fname_end members.
They are pointers to part of LOAD DATA statement which should be
rewritten during replication (file name + little extra).
sql/sql_load.cc:
Added support for 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.
Updated mysql_load()/read_fixed_length()/read_sep_field() to support
this functionality (now they can read data from file to both columns and
variables and assign do calculations and assignments specified in SET
clause).
We also use new approach for LOAD DATA binlogging/replication.
sql/sql_parse.cc:
mysql_execute_command():
Since now we have SET clause in LOAD DATA we should also check
permissions for tables used in its expressions. Also mysql_load()
has two more arguments to pass information about this clause.
sql/sql_repl.cc:
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.
sql/sql_repl.h:
struct st_load_file_info:
Removed memebers which are no longer needed for LOAD DATA binnlogging.
sql/sql_yacc.yy:
Added support for extended LOAD DATA syntax. 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;
Also now we save pointers to the beginning and to the end of part of
LOAD DATA statement which should be rewritten during replication.
196 lines
5.3 KiB
Plaintext
196 lines
5.3 KiB
Plaintext
--disable_warnings
|
||
DROP TABLE IF EXISTS t1, `"t"1`, t1aa, t2, t2aa;
|
||
drop database if exists mysqldump_test_db;
|
||
drop view if exists v1;
|
||
--enable_warnings
|
||
|
||
# XML output
|
||
|
||
CREATE TABLE t1(a int);
|
||
INSERT INTO t1 VALUES (1), (2);
|
||
--exec $MYSQL_DUMP --skip-create --skip-comments -X test t1
|
||
DROP TABLE t1;
|
||
|
||
#
|
||
# Bug #2005
|
||
#
|
||
|
||
CREATE TABLE t1 (a decimal(64, 20));
|
||
INSERT INTO t1 VALUES ("1234567890123456789012345678901234567890"),
|
||
("0987654321098765432109876543210987654321");
|
||
--exec $MYSQL_DUMP --compact test t1
|
||
DROP TABLE t1;
|
||
|
||
#
|
||
# Bug #2055
|
||
#
|
||
|
||
CREATE TABLE t1 (a double);
|
||
INSERT INTO t1 VALUES ('-9e999999');
|
||
# The following replaces is here because some systems replaces the above
|
||
# double with '-inf' and others with MAX_DOUBLE
|
||
--replace_result (-1.79769313486232e+308) (RES) (NULL) (RES)
|
||
--exec $MYSQL_DUMP --compact test t1
|
||
DROP TABLE t1;
|
||
|
||
#
|
||
# Bug #3361 mysqldump quotes DECIMAL values inconsistently
|
||
#
|
||
|
||
CREATE TABLE t1 (a DECIMAL(10,5), b FLOAT);
|
||
|
||
# check at first how mysql work with quoted decimal
|
||
|
||
INSERT INTO t1 VALUES (1.2345, 2.3456);
|
||
INSERT INTO t1 VALUES ('1.2345', 2.3456);
|
||
INSERT INTO t1 VALUES ("1.2345", 2.3456);
|
||
|
||
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='ANSI_QUOTES';
|
||
INSERT INTO t1 VALUES (1.2345, 2.3456);
|
||
INSERT INTO t1 VALUES ('1.2345', 2.3456);
|
||
--error 1054
|
||
INSERT INTO t1 VALUES ("1.2345", 2.3456);
|
||
SET SQL_MODE=@OLD_SQL_MODE;
|
||
|
||
# check how mysqldump make quoting
|
||
--exec $MYSQL_DUMP --compact test t1
|
||
--exec $MYSQL_DUMP --compact --skip-create test t1
|
||
--exec $MYSQL_DUMP --skip-create --skip-comments test t1
|
||
--exec $MYSQL_DUMP --skip-opt --extended-insert --skip-comments test t1
|
||
DROP TABLE t1;
|
||
|
||
CREATE TABLE t1(a int, b text, c varchar(3));
|
||
INSERT INTO t1 VALUES (1, "test", "tes"), (2, "TEST", "TES");
|
||
--exec $MYSQL_DUMP --skip-create --compact -X test t1
|
||
DROP TABLE t1;
|
||
|
||
#
|
||
# Bug #1707
|
||
#
|
||
|
||
CREATE TABLE t1 (`a"b"` char(2));
|
||
INSERT INTO t1 VALUES ("1\""), ("\"2");
|
||
--exec $MYSQL_DUMP --compact --skip-create -X test t1
|
||
DROP TABLE t1;
|
||
|
||
#
|
||
# Bug #1994
|
||
# Bug #4261
|
||
#
|
||
|
||
CREATE TABLE t1 (a VARCHAR(255)) DEFAULT CHARSET koi8r;
|
||
INSERT INTO t1 VALUES (_koi8r x'C1C2C3C4C5'), (NULL);
|
||
--exec $MYSQL_DUMP --skip-comments --skip-extended-insert test t1
|
||
DROP TABLE t1;
|
||
|
||
#
|
||
# Bug #2634
|
||
#
|
||
|
||
CREATE TABLE t1 (a int) ENGINE=MYISAM;
|
||
INSERT INTO t1 VALUES (1), (2);
|
||
--exec $MYSQL_DUMP --skip-comments --compatible=mysql40 test t1
|
||
--exec $MYSQL_DUMP --skip-comments --compatible=mysql323 test t1
|
||
DROP TABLE t1;
|
||
|
||
#
|
||
# Bug #2592 'mysqldump doesn't quote "tricky" names correctly'
|
||
#
|
||
|
||
create table ```a` (i int);
|
||
--exec $MYSQL_DUMP --compact test
|
||
drop table ```a`;
|
||
|
||
#
|
||
# Bug #2591 "mysqldump quotes names inconsistently"
|
||
#
|
||
|
||
create table t1(a int);
|
||
--exec $MYSQL_DUMP --comments=0 test
|
||
--exec $MYSQL_DUMP --comments=0 --compatible=ansi test
|
||
set global sql_mode='ANSI_QUOTES';
|
||
--exec $MYSQL_DUMP --comments=0 test
|
||
--exec $MYSQL_DUMP --comments=0 --compatible=ansi test
|
||
set global sql_mode='';
|
||
drop table t1;
|
||
|
||
#
|
||
# Bug #2705 'mysqldump --tab extra output'
|
||
#
|
||
|
||
create table t1(a int);
|
||
insert into t1 values (1),(2),(3);
|
||
--exec $MYSQL_DUMP --skip-comments --tab=$MYSQL_TEST_DIR/var/tmp/ test
|
||
--exec cat $MYSQL_TEST_DIR/var/tmp/t1.sql
|
||
--exec cat $MYSQL_TEST_DIR/var/tmp/t1.txt
|
||
--exec rm $MYSQL_TEST_DIR/var/tmp/t1.sql
|
||
--exec rm $MYSQL_TEST_DIR/var/tmp/t1.txt
|
||
--exec $MYSQL_DUMP --tab=$MYSQL_TEST_DIR/var/tmp/ test
|
||
--exec rm $MYSQL_TEST_DIR/var/tmp/t1.sql
|
||
--exec rm $MYSQL_TEST_DIR/var/tmp/t1.txt
|
||
drop table t1;
|
||
|
||
#
|
||
# dump of view
|
||
#
|
||
create table t1(a int);
|
||
create view v1 as select * from t1;
|
||
--exec $MYSQL_DUMP --skip-comments test
|
||
drop view v1;
|
||
drop table t1;
|
||
|
||
#
|
||
# Bug #6101: create database problem
|
||
#
|
||
|
||
--exec $MYSQL_DUMP --skip-comments --databases test
|
||
|
||
create database mysqldump_test_db character set latin2 collate latin2_bin;
|
||
--exec $MYSQL_DUMP --skip-comments --databases mysqldump_test_db;
|
||
drop database mysqldump_test_db;
|
||
|
||
#
|
||
# Bug #7020
|
||
# Check that we don't dump in UTF8 in compatible mode by default,
|
||
# but use the default compiled values, or the values given in
|
||
# --default-character-set=xxx. However, we should dump in UTF8
|
||
# if it is explicitely set.
|
||
|
||
CREATE TABLE t1 (a CHAR(10));
|
||
INSERT INTO t1 VALUES (_latin1 '<27><><EFBFBD><EFBFBD>');
|
||
--exec $MYSQL_DUMP --character-sets-dir=$CHARSETSDIR --skip-comments test t1
|
||
#
|
||
# Bug#8063: make test mysqldump [ fail ]
|
||
# We cannot tes this command because its output depends
|
||
# on --default-character-set incompiled into "mysqldump" program.
|
||
# If the future we can move this command into a separate test with
|
||
# checking that "mysqldump" is compiled with "latin1"
|
||
#
|
||
#--exec $MYSQL_DUMP --character-sets-dir=$CHARSETSDIR --skip-comments --compatible=mysql323 test t1
|
||
--exec $MYSQL_DUMP --character-sets-dir=$CHARSETSDIR --skip-comments --compatible=mysql323 --default-character-set=cp850 test t1
|
||
--exec $MYSQL_DUMP --character-sets-dir=$CHARSETSDIR --skip-comments --default-character-set=cp850 --compatible=mysql323 test t1
|
||
--exec $MYSQL_DUMP --character-sets-dir=$CHARSETSDIR --skip-comments --default-character-set=utf8 --compatible=mysql323 test t1
|
||
DROP TABLE t1;
|
||
|
||
#
|
||
# WL #2319: Exclude Tables from dump
|
||
#
|
||
|
||
CREATE TABLE t1 (a int);
|
||
CREATE TABLE t2 (a int);
|
||
INSERT INTO t1 VALUES (1),(2),(3);
|
||
INSERT INTO t2 VALUES (4),(5),(6);
|
||
--exec $MYSQL_DUMP --skip-comments --ignore-table=test.t1 test
|
||
DROP TABLE t1;
|
||
DROP TABLE t2;
|
||
|
||
#
|
||
# Bug #8830
|
||
#
|
||
|
||
CREATE TABLE t1 (`b` blob);
|
||
INSERT INTO `t1` VALUES (0x602010000280100005E71A);
|
||
--exec $MYSQL_DUMP --skip-extended-insert --hex-blob test --skip-comments t1
|
||
DROP TABLE t1;
|
||
|