5 messages in com.mysql.lists.bugsRe: Replication to slave broken in 3....
FromSent OnAttachments
Leigh Phillips12 Feb 2001 08:56 
Sasha Pachev12 Feb 2001 10:30 
Leigh Phillips12 Feb 2001 10:44 
Sasha Pachev12 Feb 2001 10:58 
Michael Widenius12 Feb 2001 12:37 
Subject:Re: Replication to slave broken in 3.23.32 for mysqlimport/LOAD DATA INFILE.
From:Michael Widenius (mon@mysql.com)
Date:02/12/2001 12:37:26 PM
List:com.mysql.lists.bugs

Hi!

"Sasha" == Sasha Pachev <sas@mysql.com> writes:

Sasha> On Monday 12 February 2001 11:44, Leigh Phillips wrote:

As indicated I have not tested with LOAD DATA INFILE but as mysqlimport uses LOAD DATA INFILE I thought it was implied. Anyhow some additional information on my configuration. The machine which is running mysqlimport is a third Linux machine with the MySQL Client installed. The import file is never located on the Master in my scenario but on the third client machine, but from your desciption LOAD DATA INFILE should work, which mysqlimport should be using as the import file is not local to the target database server, but you refer to a local file on the master? confused now..

Sasha> If the file never makes it to the master, LOAD DATA INFILE is not
possible. Sasha> You can only do LOAD LOCAL DATA INFILE, in which case it will not be Sasha> replicated. If you copy the file to the master, do LOAD DATA INFILE, and
then Sasha> wait around for the slave to catch up before deleting the file, it will
work.

We have to fix that LOAD DATA LOCAL INFILE also works with replication, but we will leave this to 4.0

Regards, Monty