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-create-db.html
COM_CREATE_DB: create a schema Payload 1 [05] COM_CREATE_DB string[EOF] schema name Returns OK_Packet or ERR_Packet Example 05 00 00 00 05 74 65 73 74 .....test .
https://dev.mysql.com/doc/internals/en/com-drop-db.html
COM_DROP_DB: drop a schema Payload 1 [06] COM_DROP_DB string[EOF] schema name Returns OK_Packet or ERR_Packet Example 05 00 00 00 06 74 65 73 74 .....test .
https://dev.mysql.com/doc/internals/en/create-file-event.html
Binlog::CREATE_FILE_EVENT: Payload 4 file_id string.EOF block-data ...
https://dev.mysql.com/doc/internals/en/determining-binary-log-version.html
Given any binary log file, the information in this section describes how to determine the format in which it is written. Some important points about descriptor event formats: The v1 header fields are common to all formats. (v3 and v4 headers begin ...
https://dev.mysql.com/doc/internals/en/extra-directory.html
These programs are all standalone utilities, that is, they have a main() function and their main role is to show information that the MySQL server needs or produces. They are as follows: comp_err.c --- makes error-message files from a multi-language ...
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 ...
https://dev.mysql.com/doc/internals/en/getting-source-tree.html
This section describes how to obtain the MySQL source tree, which is currently available on GitHub. For more information about MySQL's move to GitHub, refer to the announcement on the MySQL Release Engineering blog: MySQL on GitHub To obtain the ...
https://dev.mysql.com/doc/internals/en/incident-event.html
Binlog::INCIDENT_EVENT: Payload 2 type 1 message length n message Fields type (2) -- Hex Name 0x0000 INCIDENT_NONE 0x0001 INCIDENT_LOST_EVENTS message_length (1) -- length of message message (string.var_len) -- [len=$message_length] message .
https://dev.mysql.com/doc/internals/en/information-schema-optimizer-trace-table.html
TRACE: The trace, in JSON format (see json.org: basically it has scalars (number, string, bool) and structures (either arrays or associative arrays)).