ta for archival. But I haven't done
this in a replication situation.
Dan.
-Original Message-
From: Goldblatt, Eric [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 09, 2006 2:45 PM
To: Atle Veka
Cc: mysql@lists.mysql.com
Subject: RE: replication after editing bin logs
Atle,
No, unfo
nd then didn't release it by the time
the 258th command was executed.
Eric
-----Original Message-
From: Scott Tanner [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 09, 2006 9:38 AM
To: Goldblatt, Eric
Cc: Mysql User List
Subject: Re: replication after editing bin logs
Can you post th
: mysql@lists.mysql.com
Subject: Re: replication after editing bin logs
Do you have control over the DELETE queries? If so I would look into the
option of using 'SQL_LOG_BIN':
http://dev.mysql.com/doc/refman/5.0/en/set-option.html
SQL_LOG_BIN = {0 | 1}
If set to 0, no loggi
Do you have control over the DELETE queries? If so I would look into the
option of using 'SQL_LOG_BIN':
http://dev.mysql.com/doc/refman/5.0/en/set-option.html
SQL_LOG_BIN = {0 | 1}
If set to 0, no logging is done to the binary log for the client.
The client must have the SUPER priv
thing is that
> there were inserts into this table earlier in the binlog, and they did
> not produce any error messages.
>
>
> Eric
> -Original Message-
> From: Scott Tanner [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 08, 2006 3:46 PM
> To: Goldblatt, E
