Search Results
https://dev.mysql.com/doc/internals/en/com-query-response.html
Image description If it is not a valid Protocol::LengthEncodedInteger it is either a ERR_Packet or a Protocol::LOCAL_INFILE_Request. Image description 14.6.4.1.1 Text Resultset A Text Resultset is a possible COM_QUERY Response. It is made up of two ...
https://dev.mysql.com/doc/internals/en/com-refresh.html
Note As of MySQL 5.7.11, COM_REFRESH is deprecated and will be removed in a future version of MySQL.
https://dev.mysql.com/doc/internals/en/com-stmt-execute-response.html
Similar to the COM_QUERY_Response a COM_STMT_EXECUTE either returns: a OK_Packet a ERR_Packet or a resultset: Binary Protocol Resultset .
https://dev.mysql.com/doc/internals/en/creating-handlerton.html
The handlerton (short for handler singleton) defines the storage engine and contains method pointers to those methods that apply to the storage engine as a whole, as opposed to methods that work on a per-table basis. Some examples of such methods ...
https://dev.mysql.com/doc/internals/en/debug-sync-implementation.html
Pseudo code for a synchronization point: #define DEBUG_SYNC(thd, sync_point_name) if (unlikely(opt_debug_sync_timeout)) debug_sync(thd, STRING_WITH_LEN(sync_point_name)) The synchronization point performs a binary search in a sorted array of ...
https://dev.mysql.com/doc/internals/en/docs-directory.html
Binary and source distributions include some pre-formatted documentation files, such as the MySQL Reference manual in Info format (for Unix) or CHM format (for Windows).
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/event-class-archaeological-notes.html
Despite the "V3" in the type code name, START_EVENT_V3 currently is used as the type code not only for v3 start events, but also for v1 start events. The original symbol for type code 1 was START_EVENT in the format now known as v1. Later, when v3 ...
https://dev.mysql.com/doc/internals/en/event-data-fields.html
The structure of an event's data part depends on the event type: In v1 and v3, the event type entirely determines the data format In v4, interpretation of the data part depends on the event type in conjunction with information from the format ...
https://dev.mysql.com/doc/internals/en/files-in-innodb-sources.html
The InnoDB source files are the best place to look for information about internals of the file structure that MySQLers can optionally use for transaction support. But when you first look at all the subdirectories and file names you'll wonder: Where ...