Re: Rename Table in Replication failed / command missing in slave log

2002-08-13 Thread Heikki Tuuri
> Lutz, > > - Original Message - > From: "Lutz Maibach" <[EMAIL PROTECTED]> > To: "Heikki Tuuri" <[EMAIL PROTECTED]> > Sent: Tuesday, August 13, 2002 5:09 PM > Subject: Re: Rename Table in Replication failed / command missing in slave &

Re: Rename Table in Replication failed / command missing in slave log

2002-08-13 Thread Heikki Tuuri
Hi! The following might fix Pete's RENAME TABLE bug: ... August 12, 2002: If you ran in the AUTOCOMMIT mode, executed a SELECT, and immediately after that a RENAME TABLE, then RENAME would fail and MySQL would complain about error 1192 'Can't execute the given command because you have active lock

Re: Rename Table in Replication failed / command missing in slave log

2002-08-12 Thread Pete Harlan
If you're using InnoDB tables, replication stops the slaves from running. Heikki said he'd try to get this fixed for 3.23.52. --Pete On Mon, Aug 12, 2002 at 04:05:11PM +0200, Lutz Maibach wrote: > Hi, > > today I noticed a strange behaviour in MySQL 3.23.49a-Replication I can't explain. > A