Re: BEGIN/COMMIT statements not written to the binary log : may it cause problems with replication ?

Guilhem, this is a known problem and mentioned in the Restrictions section of the InnoDB online manual. It is not the correct way to run SQL statements in the autocommit mode on the slave server, while the master has normal transaction processing on. I have asked Sasha to add COMMIT marks to th

Re: BEGIN/COMMIT statements not written to the binary log : may it cause problems with replication ?

Guilhem, this is a known problem and mentioned in the Restrictions section of the InnoDB online manual. It is not the correct way to run SQL statements in the autocommit mode on the slave server, while the master has normal transaction processing on. I have asked Sasha to add COMMIT marks to th

Re: BEGIN/COMMIT statements not written to the binary log : may it cause problems with replication ?

Hi! > "Heikki" == Heikki Tuuri <[EMAIL PROTECTED]> writes: Heikki> Guilhem, Heikki> this is a known problem and mentioned in the Restrictions section of the Heikki> InnoDB online manual. Heikki> It is not the correct way to run SQL statements in the autocommit mode on Heikki> the slave ser

Re: BEGIN/COMMIT statements not written to the binary log : may it cause problems with replication ?

Hi! > "Heikki" == Heikki Tuuri <[EMAIL PROTECTED]> writes: Heikki> Guilhem, Heikki> this is a known problem and mentioned in the Restrictions section of the Heikki> InnoDB online manual. Heikki> It is not the correct way to run SQL statements in the autocommit mode on Heikki> the slave ser

Re: BEGIN/COMMIT statements not written to the binary log : may it cause problems with replication ?

Guilhem, this is a known problem and mentioned in the Restrictions section of the InnoDB online manual. It is not the correct way to run SQL statements in the autocommit mode on the slave server, while the master has normal transaction processing on. I have asked Sasha to add COMMIT marks to th