MySQL Bugs: #222: Options of LOAD DATA lost in replication (FIELDS TERMINATED BY etc)

Bug #222	Options of LOAD DATA lost in replication (FIELDS TERMINATED BY etc)
Submitted:	2 Apr 2003 5:11	Modified:	3 Apr 2003 1:39
Reporter:	Guilhem Bichot	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	4.0	OS:	Any (all)
Assigned to:	Bugs System	CPU Architecture:	Any

Description:
Options are well written to the binlog but badly read by the slave.

How to repeat:
create table andrew(f1 varchar(10),f2 varchar(10));

Have a text file '/home/andrew/upload' that looks like this :
hell0,hello
hi,hi

Master :
mysql> LOAD DATA INFILE '/home/andrew/upload' into table andrew FIELDS
TERMINATED BY ',' lines terminated by '\n';
Query OK, 2 rows affected (0.01 sec)
cords: 2  Deleted: 0  Skipped: 0  Warnings: 0

The resulting table on the master is :

mysql> select * from andrew;
+-------+-------+

| f1    | f2    |

+-------+-------+

| hell0 | hello |
| hi    | hi    |

+-------+-------+
2 rows in set (0.00 sec)

But on the slave it is :

mysql> select * from andrew;
+------------+------+

| f1         | f2   |

+------------+------+

| hell0,hell | NULL |
| hi,hi      | NULL |

+------------+------+
2 rows in set (0.00 sec)

Suggested fix:
Victor has sent a patch to Monty, the fix should go into 4.0.13.

Thank you for your bug report. This issue has been fixed in the latest
development tree for that product. You can find more information about
accessing our development trees at 
    http://www.mysql.com/doc/en/Installing_source_tree.html