Oracle 5.0 Reference Manual page 1524

4. When the value is 0, issue a
Temporary tables and replication options.
happens whether or not there are any matching
[1458], or
do-table
replicate-ignore-table
honored for temporary tables.
A recommended practice when using replication is to designate a prefix for exclusive use in naming
temporary tables that you do not want replicated, then employ a matching
ignore-table
(such as norepmytable, norepyourtable, and so on), then use
norep
ignore-table=norep%
16.4.1.16. Replication of the
User privileges are replicated only if the
SET PASSWORD,
replication setup includes the
See also Section 16.4.1.17, "Replication and User
16.4.1.17. Replication and User Privileges
User privileges are replicated only if the
SET PASSWORD,
replication setup includes the
If you are replicating all databases, but do not want statements that affect user privileges to be
replicated, set up the slave not to replicate the
ignore-table=mysql.%
have no effect, and thus it does not execute those statements.
See Section 16.4.1.16, "Replication of the
16.4.1.18. Replication and the Query Optimizer
It is possible for the data on the master and slave to become different if a statement is written in such
a way that the data modification is nondeterministic; that is, left up the query optimizer. (In general, this
is not a good practice, even outside of replication.) Examples of nondeterministic statements include
or
DELETE UPDATE
"Replication and
Also see Section C.5.8, "Known Issues in
16.4.1.19. Replication and Reserved Words
You can encounter problems when you attempt to replicate from an older master to a newer slave and
you make use of identifiers on the master that are reserved words in the newer MySQL version running
on the slave. An example of this is using a table column named
that is replicating to a 4.1 or higher slave because
MySQL 4.1. Replication can fail in such cases with Error 1064
syntax..., even if a database or table named using the reserved word or a table having a column
named using the reserved word is excluded from replication. This is due to the fact that each SQL
event must be parsed by the slave prior to execution, so that the slave knows which database object or
objects would be affected; only after the event is parsed can the slave apply any filtering rules defined
by
--replicate-do-db
[1457], and
db
To work around the problem of database, table, or column names on the master which would be
regarded as reserved words by the slave, do one of the following:
Replication Features and Issues
mysqladmin shutdown
--replicate-wild-do-table
[1458] and
[1460] option. For example, you might give all such tables names beginning with
[1460] to prevent the replication of these tables.
System Database
mysql
USER, and
CREATE
database.
mysql
USER, and
CREATE
database.
mysql
[1460] option. The slave recognizes that privilege-related SQL statements
statements that use
LIMIT", for a detailed discussion of these.
[1457],
--replicate-do-table
--replicate-ignore-table
command to stop the slave.
By default, all temporary tables are replicated; this
--replicate-do-db
[1459]
--replicate-wild-ignore-table
database is replicated. That is, the GRANT, REVOKE,
mysql
statements take effect on the slave only if the
DROP USER
Privileges".
database is replicated. That is, the GRANT, REVOKE,
mysql
statements take effect on the slave only if the
DROP USER
database, using the
mysql
System Database", for more information.
mysql
with no
LIMIT ORDER BY
MySQL".
CURRENT_USER
[1458].
1504
[1457],
--replicate-
options in effect. However, the
[1460]
--replicate-wild-
--replicate-wild-
--replicate-wild-
clause; see Section 16.4.1.9,
on a 4.0 master
current_user
is a reserved word beginning in
You have an error in your SQL
[1458],
--replicate-ignore-
--
options are