Search Results
                    
                    
            https://dev.mysql.com/doc/refman/8.4/en/privileges-provided.html
                                 The privileges granted to a MySQL account determine which operations the account can perform. MySQL privileges differ in the contexts in which they apply and at different levels of operation: Administrative privileges enable users to manage ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/problems-with-float.html
                                 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 statement may not be the same as the value represented internally. Attempts to treat ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/program-variables.html
                                 Many MySQL programs have internal variables that can be set at runtime using the SET statement. See Section 15.7.6.1, “SET Syntax for Variable Assignment”, and Section 7.1.9, “Using System Variables”. Most of these program variables also ...
                                            
                https://dev.mysql.com/doc/refman/8.4/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.4/en/replication-features-transactions.html
                                In general, you should avoid transactions that update both transactional and nontransactional tables in a replication environment. You should also avoid using any statement that accesses both transactional (or temporary) and nontransactional tables ...
                                            
                https://dev.mysql.com/doc/refman/8.4/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.4/en/replication-gtids-auto-positioning.html
                                 GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and replica. When GTIDs are in use, all the information that the replica needs for synchronizing with ...
                                            MySQL 8.4 Reference Manual :: 19.2.1.3 Determination of Safe and Unsafe Statements in Binary Logging
                https://dev.mysql.com/doc/refman/8.4/en/replication-rbr-safe-unsafe.html
                                 The “safeness” of a statement in MySQL replication refers to whether the statement and its effects can be replicated correctly using statement-based format. If this is true of the statement, we refer to the statement as safe; otherwise, we ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/replication-rules-channel-based-filters.html
                                 This section explains how to work with replication filters when multiple replication channels exist, for example in a multi-source replication topology. Replication filters can be global or specific to a channel, enabling you to configure ...
                                            
                https://dev.mysql.com/doc/refman/8.4/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 ...