PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.5Kb
Man Pages (Zip)
- 401.8Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/problems-with-float.html
Attempts to treat floating-point values as exact in comparisons may lead to problems. Floating-point numbers sometimes cause confusion because they are approximate and not stored as exact values. A floating-point value as written in an SQL ...
https://dev.mysql.com/doc/refman/8.0/en/program-variables.html
In an option file, variable settings are given without the leading dashes: [mysql] max_allowed_packet=16777216 Or: [mysql] max_allowed_packet=16M If you like, underscores in an option name can be specified as dashes. Many MySQL programs have ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-sql-mode.html
Using different server SQL mode settings on the source and the replica may cause the same INSERT statements to be handled differently on the source and the replica, leading the source and replica to diverge. For best results, you should always use ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-transactions.html
That is, such transactions can lead to source storage engine-specific behavior with the possible effect of replication going out of synchrony. In general, you should avoid transactions that update both transactional and nontransactional tables in a ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-triggers.html
If under row-based replication the replica applied the triggers as well as the row changes caused by them, the changes would in effect be applied twice on the replica, leading to different data on the source and the replica. With statement-based ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-variables.html
sql_mode is also replicated except for the NO_DIR_IN_CREATE mode; the replica always preserves its own value for NO_DIR_IN_CREATE, regardless of changes to it on the source. However, when mysqlbinlog parses a SET @@sql_mode = mode statement, the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-auto-positioning.html
The source and replica can diverge if any clients commit transactions on the source after it is restarted, which can lead to the situation where the source and replica are using the same GTID for different transactions. GTIDs replace the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rbr-safe-unsafe.html
If a large number of such statements were executed on the source, this could lead to excessively large error log files. The “safeness” of a statement in MySQL replication refers to whether the statement and its effects can be replicated ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rules-channel-based-filters.html
The following command options support channel specific replication filters using this format: --replicate-do-db=channel:database_id --replicate-ignore-db=channel:database_id --replicate-do-table=channel:table_id ... This section explains how to work ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rules-examples.html
If you use a combination of database-level and table-level replication filtering options, the replica first accepts or ignores events using the database options, then it evaluates all events permitted by those options according to the table options. It is also important to note that the results vary depending on whether the operation is logged using statement-based or row-based binary logging ...