Przemyslaw Popielarski wrote:
Sasha Pachev [EMAIL PROTECTED] wrote:
Check if you have any replication restricting rules on the slave.
There might be a bug that incorrectly flags a query to be excluded.
If that is the case, then try to re-write the rules to see if you can
get around the bug.
Yes.
Sasha Pachev [EMAIL PROTECTED] wrote:
Check if you have any replication restricting rules on the slave.
There might be a bug that incorrectly flags a query to be excluded.
If that is the case, then try to re-write the rules to see if you can
get around the bug.
Yes. I have recently add the
I'm executing on master a long and complicated query such:
UPDATE (lots of tables, lots of LEFT JOIN) SET ... WHERE .
The query updates i.e. 3816 rows.
The query DOES replicate do master's and slave's binary log.
But it DOES NOT execute on slave. 3816 rows are not updated on slave
and slave
I'm executing on master a long and complicated query such:
UPDATE (lots of tables, lots of LEFT JOIN) SET ... WHERE .
Okey, I simplified the query to:
-
UPDATE
tKsidata,
tKsiabeksiazki
SET
tKsidata.STAN_REALNY=tKsiabeksiazki.STAN
WHERE
tKsidata.ksi='0815120877' and
Przemyslaw Popielarski wrote:
I'm executing on master a long and complicated query such:
UPDATE (lots of tables, lots of LEFT JOIN) SET ... WHERE .
Okey, I simplified the query to:
-
UPDATE
tKsidata,
tKsiabeksiazki
SET
tKsidata.STAN_REALNY=tKsiabeksiazki.STAN
WHERE
