Search Results
https://dev.mysql.com/doc/internals/en/debug-sync-activation-deactivation.html
For test cases that require the Debug Sync facility, include the following line in the test case file: --source include/have_debug_sync.inc . The Debug Sync facility is an optional part of the MySQL server. The Debug Sync Facility, when compiled ...
https://dev.mysql.com/doc/internals/en/debug-sync-facility.html
The documentation here is derived from comments in the sql/debug_sync.cc source file. MySQL supports a Debug Sync Facility, which - in spite of the "debug" in its name - is completely independent from the DBUG facility (except that it uses DBUG to ...
https://dev.mysql.com/doc/internals/en/error-masking.html
Example: --error ER_BAD_DB_ERROR USE <not existing database>; You can find the error names in the include/mysqld_error.h file of a MySQL source distribution, or in the Server Error Message Reference section of the MySQL Reference Manual]. Use of the ...
https://dev.mysql.com/doc/internals/en/event-data-field-notational-caveat.html
The fixed part of the event data goes under different names, depending on which source file, work log, bug report, etc. you are reading: Sometimes it is called the "fixed data" part, as in this discussion. To make things notationally interesting, ...
https://dev.mysql.com/doc/internals/en/extra-directory.html
They are as follows: comp_err.c --- makes error-message files from a multi-language source my_print_defaults.c --- print parameters from my.ini files. These programs are all standalone utilities, that is, they have a main() function and their main ...
https://dev.mysql.com/doc/internals/en/floating-point-types.html
The MySQL Reference Manual has a discussion of floating-point numbers in Section 11.2 Numeric Types, including details about the storage. Let us now take up the story from where the MySQL Reference Manual leaves off. The following discussion ...
https://dev.mysql.com/doc/internals/en/frm-file-format.html
Regardless of the storage engine you choose, every MySQL table you create is represented on disk by a .frm file that describes the table's format (that is, the table definition). The file bears the same name as the table, with an .frm extension.
https://dev.mysql.com/doc/internals/en/guided-tour-chunk.html
Now, having finished with our bird's eye view of the source code from the air, let's take the perspective of the worms on the ground (which is another name for MySQL's developer staff -- turn on laugh track here). if (updated && (error <= 0 || ...
https://dev.mysql.com/doc/internals/en/guided-tour-sedir.html
So you can download Sleepycat's own documentation of the source code in the BDB directory. bdb /* external */ heap innobase /* external */ myisam myisammrg ndb Let's go through the idea of storage engines once more, this time with a list of all the ...
https://dev.mysql.com/doc/internals/en/handler-instantiation.html
Before the handlerton is defined in the storage engine source file, a method header for the instantiation method must be defined. The first method call your storage engine needs to support is the call for a new handler instance. Here is an example ...