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 server, while
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
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
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
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 server, while
Hello there,
I use MySQL (4.0.1) with InnoDB tables with binary logging on.
I see that the
BEGIN and COMMIT statements that wrap my queries are
not written to the binary log. I perfectly understand this if
I have one server. But assume I have a master server, and a
slave server that
