Search Results
https://dev.mysql.com/doc/internals/en/innodb-field-contents.html
I made a table with this definition: CREATE TABLE T (FIELD1 VARCHAR(3), FIELD2 VARCHAR(3), FIELD3 VARCHAR(3)) Type=InnoDB; To understand what follows, you must know that table T has six columns — not three — because InnoDB automatically added ...
https://dev.mysql.com/doc/internals/en/logging-transactions-definitions.html
Note: N-writes include updates to N-tables, but also CREATE and DROP statements. To reason about logging different table types, we make some preliminary definitions. (D-T-table) A table that has a transactional engine is called a T-table.
https://dev.mysql.com/doc/internals/en/mismatch-of-focus-of-test-and-code-sequence.html
CREATE TABLE t1 ( id INT NOT NULL AUTO_INCREMENT, my_column VARCHAR(30), name LONGTEXT, PRIMARY KEY (id)); INSERT INTO t1(my_column,name) VALUES('2','two'); INSERT INTO t1(my_column,name) VALUES('1','one'); INSERT INTO t1(my_column,name) ...
https://dev.mysql.com/doc/internals/en/optimizer-index-join-type.html
For this query: SELECT column1, column2 FROM Table1; the optimizer will use join type = index only if the index has this definition: CREATE INDEX ... Consider this query: SELECT column1 FROM Table1; If column1 is indexed, then the optimizer may ...
https://dev.mysql.com/doc/internals/en/optimizer-index-merge-join-type.html
MySQL creates a cond_key_i condition for each of the usable keys. 7.2.2.5.1 Overview Index Merge is used when table condition can be converted to form: cond_1 OR cond_2 ... OR cond_N The conditions for conversion are that each cond_i can be used ...
https://dev.mysql.com/doc/internals/en/prepared-stored-procedure-execution.html
This arena happens to be also the permanent query arena of every instruction of the procedure, as the parser creates all instructions in the same arena. Execution of a stored procedure statement is similar to execution of a prepared statement.
https://dev.mysql.com/doc/internals/en/prepared-stored.html
The role of the parser is to create a set of objects to represent the query. Creation of an execution plan, including evaluation of an order of joins and initialization of methods to access the used tables. Let us start with a general description ...
https://dev.mysql.com/doc/internals/en/replication-not-guaranteed.html
(P-exception-federated) If a table uses a federated table on the master, then TODO (P-exception-table-definition) If a CREATE TABLE uses a DATA DIRECTORY or INDEX DIRECTORY clause, then the table may not be correctly replicated. There are some ...
https://dev.mysql.com/doc/internals/en/running-mysql-test-run-out-of-source.html
When building out of source (see Section 4.4.1, “Create the Build Directory”), use mysql-test-run.pl in the mysql-test directory under the build directory. It is a wrapper script that calls mysql-test-run.pl in the source directory and tells it ...
https://dev.mysql.com/doc/internals/en/select-steps.html
Every select is performed in these base steps: JOIN::prepare Initialization and linking JOIN structure to st_select_lex. fix_fields() for all items (after fix_fields(), we know everything about item).