mirror of
https://github.com/MariaDB/server.git
synced 2025-07-29 05:21:33 +03:00
Bug#11829838: ALTER TABLE NOT BINLOGGED WITH
--BINLOG-IGNORE-DB AND FULLY QUALIFIED TABLE Problem: ======= An ALTER TABLE statement is not written to binlog if server started with "--binlog-ignore-db some database" and 'fully qualified' table names are used in the ALTER TABLE statement altering table different from current database context. Analysis: ======== The above mentioned problem not only affects "ALTER TABLE" statements but also to all kind of statements. Once the current default database becomes "NULL" none of the statements will be binlogged. The current behaviour is such that if the user has specified restrictions on which database needs to be replicated and the default db is not specified, then do not replicate. This means that "NULL" is considered to be equivalent to everything (default db = null implied ignore don't log the statement). Fix: === "NULL" should not be considered as equivalent to everything. Since the filtering criteria is not equal to "NULL" the statement should be logged into binlog.
This commit is contained in:
@ -154,11 +154,14 @@ Rpl_filter::db_ok(const char* db)
|
||||
DBUG_RETURN(1); // Ok to replicate if the user puts no constraints
|
||||
|
||||
/*
|
||||
If the user has specified restrictions on which databases to replicate
|
||||
and db was not selected, do not replicate.
|
||||
Previous behaviour "if the user has specified restrictions on which
|
||||
databases to replicate and db was not selected, do not replicate" has
|
||||
been replaced with "do replicate".
|
||||
Since the filtering criteria is not equal to "NULL" the statement should
|
||||
be logged into binlog.
|
||||
*/
|
||||
if (!db)
|
||||
DBUG_RETURN(0);
|
||||
DBUG_RETURN(1);
|
||||
|
||||
if (!do_db.is_empty()) // if the do's are not empty
|
||||
{
|
||||
|
Reference in New Issue
Block a user