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/prepare.html
                                The prepared statement is executed with EXECUTE and released with DEALLOCATE PREPARE. Within the statement, ? characters can be used as parameter markers to indicate where data values are to be bound to the query later when you execute it. This ...
                                            
                https://dev.mysql.com/doc/refman/5.7/en/creating-spatial-indexes.html
                                 For InnoDB and MyISAM tables, MySQL can create spatial indexes using syntax similar to that for creating regular indexes, but using the SPATIAL keyword. For storage engines that support nonspatial indexing of spatial columns, the engine creates a ...
                                            
                https://dev.mysql.com/doc/refman/5.7/en/example-user-variables.html
                                 You can employ MySQL user variables to remember results without having to store them in temporary variables in the client. 
                                            
                https://dev.mysql.com/doc/refman/5.7/en/innodb-locking-transaction-model.html
                                 To implement a large-scale, busy, or highly reliable database application, to port substantial code from a different database system, or to tune MySQL performance, it is important to understand InnoDB locking and the InnoDB transaction model. This ...
                                            
                https://dev.mysql.com/doc/refman/5.7/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/5.7/en/set-sql-log-bin.html
                                If you are using GTIDs for replication, this means that even when binary logging is later enabled again, the GTIDs written into the log from this point do not account for any transactions that occurred in the meantime, so in effect those ... SET ...
                                            
                https://dev.mysql.com/doc/refman/5.7/en/sys-schema.html
                                mysql_upgrade returns an error if a sys schema exists but has no version view, on the assumption that absence of this view indicates a user-created sys schema.  MySQL 5.7 includes the sys schema, a set of objects that helps DBAs and developers ...
                                            
                https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-failover.html
                                Executing the entire transaction history can be time-consuming when the source server has processed a large number of transactions previously, and this can represent a major bottleneck when setting up a new replica. Copying over binary logs to the ...The easiest way to reproduce all identifiers and transactions on a new server is to make the new server into the replica of a source that has the entire execution history, and enable global transaction identifiers on both ...
                                            
                https://dev.mysql.com/doc/refman/5.7/en/creating-database.html
                                To make menagerie the current database, use this statement: mysql> USE menagerie Database changed Your database needs to be created only once, but you must select it for use each time you begin a mysql session. Note You can see at any time which ...
                                            
                https://dev.mysql.com/doc/refman/5.7/en/create-tablespace.html
                                EXTENT_SIZE: This option is specific to NDB, and is not supported by InnoDB, where it fails with an error. The minimum size is 32K, and theoretical maximum is 2G, although the practical maximum size depends on a number of factors. In theory, up to ...The precise syntax and semantics depend on the storage engine ...