Search Results
                    
                    
            https://dev.mysql.com/doc/internals/en/cmd-line-utils-directory.html
                                All the files here are "non-MySQL" files, in the sense that MySQL AB didn't produce them, it just uses them. It should be unnecessary to study the programs in these files unless you are writing or debugging a tty-like client for MySQL, such as ...
                                            
                https://dev.mysql.com/doc/internals/en/com-change-user.html
                                 COM_CHANGE_USER changes the user of the current connection and reset the connection state. and others It is followed by the same states as the initial handshake. 
                                            
                https://dev.mysql.com/doc/internals/en/com-stmt-prepare.html
                                 COM_STMT_PREPARE creates a prepared statement from the passed query string. The server returns a COM_STMT_PREPARE Response which contains a statement-id which is used to identify the prepared statement. 
                                            
                https://dev.mysql.com/doc/internals/en/creating-tables.html
                                 Once a handler is instanced, the first operation that will likely be required is the creation of a table. Your storage engine must implement the [custom-engine.html#custom-engine-api-reference-create create()] virtual method: virtual int ...
                                            
                https://dev.mysql.com/doc/internals/en/dbug-directory.html
                                Rather, it's a set of public-domain routines which are useful for debugging MySQL programs. The MySQL Server and all .c and .cc programs support the use of this package. How it works: One inserts a function call that begins with DBUG_* in one of the ...
                                            
                https://dev.mysql.com/doc/internals/en/determining-logging-format.html
                                 For each statement, we must determine the logging format: row or statement. At parse time, it is detected if the statement is unsafe to log in statement format (that is, requires row format). This must be done prior to the call to ...
                                            
                https://dev.mysql.com/doc/internals/en/differences-master-slave.html
                                Any intermediate state of the slave is identical to some intermediate state of the master. Note: it is not required that each intermediate state of the master is identical to some intermediate state of the slave. We now state the architectural ...
                                            
                https://dev.mysql.com/doc/internals/en/ensuring-compatibility-of-future-binary-log-versions.html
                                However, as indicated earlier, v1-format files can be recognized from the initial event in the file, by a type code of START_EVENT_V3 and an event length less than 75. The v4 format description event is designed so that it can handle future format ...
                                            
                https://dev.mysql.com/doc/internals/en/error-message-marking-obsolete.html
                                 Beginning with MySQL 8.0, it is possible to mark an error message obsolete. This should be done only for messages that no longer used in the server code. The following procedure shows how to do this, using the ER_HASHCHK error as an example. Find ...
                                            
                https://dev.mysql.com/doc/internals/en/error-messages-old-versions.html
                                In practice, no new error messages should be added to error message files for versions of MySQL prior to 5.0.3. Doing so and merging the messages upward would cause error numbers to change in more recent versions. Before MySQL 5.0.3, error messages ...