| Bug #14050 | Blocking some replication statements. | ||
|---|---|---|---|
| Submitted: | 15 Oct 2005 17:52 | Modified: | 17 Dec 2010 13:18 |
| Reporter: | daniel lo | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: DML | Severity: | S4 (Feature request) |
| Version: | Any | OS: | Any (Any) |
| Assigned to: | CPU Architecture: | Any | |
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.021 sec. using MySQL 8.0.36-u2-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.
© 2024, Oracle Corporation and/or its affiliates
Description: It would be nice to have "LOCAL" in UPDATE/INSERT/DELETE/TRUNCATE SQL statements. LOCAL would turn off replication for this statement. Which would simulate the following UPDATE LOCAL table-name SET x=1,y=1 WHERE z=1 instead of SET SQL_LOG_BIN=0 UPDATE table-name SET x=1,y=1 WHERE z=1 SET SQL_LOG_BIN=1 This feature will save 2/3 of the queries that have to be written (and 2/3's of the round trips). This feature would be greatly appreciated, as I recently made this mistake $db->do("SET SQL_LOG_BIN=0"); return $db->do("UPDATE table-name SET x=1,y=1 WHERE z=1"); $db->do("SET SQL_LOG_BIN=1"); It was a stupid mistake, however, the feature still would be greatly appreciated. How to repeat: Turn off brain... resume programming.