PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/precision-math-examples.html
Rounding behavior for exact-value numbers is well-defined: Rounding behavior (for example, with the ROUND() function) is independent of the implementation of the underlying C library, which means that results are consistent from platform to platform. If the argument to an aggregate function is an exact numeric type, the result is also an exact numeric type, with a scale at least that of the ...
https://dev.mysql.com/doc/refman/5.7/en/precision-math-rounding.html
This section discusses precision math rounding for the ROUND() function and for inserts into columns with exact-value types (DECIMAL and integer). The ROUND() function rounds differently depending on whether its argument is exact or approximate: ...
https://dev.mysql.com/doc/refman/5.7/en/replication-administration-skip.html
The CHANGE MASTER TO statement does not have this function, so you must be careful to identify the correct location to restart replication at the beginning of an event group. If replication stops due to an issue with an event in a replicated ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-fractional-seconds.html
On the source, functions that return a result that includes the current time (such as CURTIME(), SYSDATE(), or UTC_TIMESTAMP()) interpret an argument as an fsp value and the return value includes a fractional seconds part of that many digits. On the ... MySQL 5.7 permits fractional seconds for TIME, DATETIME, and TIMESTAMP values, with up to microseconds (6 digits) ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-timezone.html
Otherwise, statements depending on the local time on the source are not replicated properly, such as statements that use the NOW() or FROM_UNIXTIME() functions. By default, source and replica servers assume that they are in the same time zone. If ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-concepts.html
The auto-skip function for GTIDs means that a transaction committed on the source can be applied no more than once on the replica, which helps to guarantee consistency. The built-in functions GTID_SUBSET() and GTID_SUBTRACT() require GTID sets as ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html
In any of the cases just mentioned, the one-to-one correspondence between transactions and GTIDs is broken, with the result that GTID-based replication cannot function correctly. CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE statements are not ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source-provision-replica.html
If the sources in the multi-source replication topology have existing data, it can save time to provision the replica with the relevant data before starting replication. In a multi-source replication topology, copying the data directory cannot be ...
https://dev.mysql.com/doc/refman/5.7/en/replication-rules-examples.html
Operations to watch out for include transactions involving multi-table UPDATE statements, triggers, cascading foreign keys, stored functions that update multiple tables, and DML statements that invoke stored functions that update one or more tables.
https://dev.mysql.com/doc/refman/5.7/en/replication-rules-table-options.html
If so, and the statement occurs within a stored function, the replica executes the statement and exits. If row-based replication is enabled, the replica does not know whether a statement occurred within a stored function on the source, so this ...