Bug #88 | Some SET commands should be written to the binlog as they affect next updates | ||
---|---|---|---|
Submitted: | 21 Feb 2003 6:41 | Modified: | 27 Sep 2008 8:44 |
Reporter: | Guilhem Bichot | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.0 | OS: | Any (all) |
Assigned to: | CPU Architecture: | Any |
[21 Feb 2003 6:41]
Guilhem Bichot
[21 Feb 2003 6:50]
Guilhem Bichot
I don't know why, but this "bugs" reporting tool does not include any hint of who wrote this bug report in the email it send to dev-bugs. But the "from" field in this form is filled, it's just not printed in the email Guilhem@mysql.com
[11 Mar 2003 6:06]
Guilhem Bichot
Annoying bug but will be fixed in 5.0 only (agreed with Monty)
[22 Apr 2003 4:40]
Guilhem Bichot
Fixing it is scrum task #755
[26 Apr 2003 7:04]
Michael Widenius
This issue is documented in the MySQL manual in the replication section
[20 Dec 2003 6:50]
Guilhem Bichot
FOREIGN_KEY_CHECKS works since 4.0.14. UNIQUE_CHECKS, SQL_AUTO_IS_NULL, SQL_MODE work in 5.0.0
[2 Feb 2004 6:27]
Guilhem Bichot
Charsets setting will be replicated in 5.0.x, and others (probably TABLE_TYPE, and SQL_SELECT_LIMIT) too.
[27 Sep 2008 8:44]
Konstantin Osipov
Fixed in 5.0, in scope of WL#755