Search Results
https://dev.mysql.com/doc/internals/en/support-for-delete.html
For non-indexed storage engines the parameter can be ignored, but transactional storage engines may need to store the deleted data for rollback purposes. The following example is from the CSV storage engine: int ha_tina::delete_row(const byte * buf) ...
https://dev.mysql.com/doc/internals/en/support-for-non-sequential-reads.html
In addition to table scanning, storage engines can implement methods for non-sequential reading. (Note: this is not "can" but rather a "must" because certain operations rely on proper implementation of position() and rnd_pos() calls. Two examples ...
https://dev.mysql.com/doc/internals/en/support-for-savepoints.html
This should be a fixed size, preferably not large as the MySQL server will allocate space to store the savepoint for all storage engines with each named savepoint. First, the implementor should know how many bytes are required to store savepoint ...
https://dev.mysql.com/doc/internals/en/support-for-update.html
Performing an update will depend on row format and storage implementation. Some storage engines will replace data in-place, while other implementations delete the existing row and append the new row at the end of the data file. Non-indexed storage ...
https://dev.mysql.com/doc/internals/en/test-faults.html
In particular, one needs to know if servers will either correctly recover or print out appropriate error messages thus avoiding unexpected problems in a production environment. Status of this section: up to date 2010-09-08 The assessment of the ...
https://dev.mysql.com/doc/internals/en/text-protocol.html
The old commands are supported for all MySQL Server versions from 3.20 upwards (and perhaps older). Additional commands implemented since then are described in sections following this one.
https://dev.mysql.com/doc/internals/en/tools-directory.html
The only file is: mysqlmanager.c --- A "server management daemon" by Sasha Pachev. This is a tool under development and is not yet useful.
https://dev.mysql.com/doc/internals/en/transactions-current-situation.html
So from the server point of view, transactions are always distributed. Nowadays a statement transaction is started for each statement that accesses transactional tables or uses the binary log. Commits of statement transactions are not durable -- ...
https://dev.mysql.com/doc/internals/en/transactions-data-layout.html
These members correspond to the statement and normal transactions respectively: thd->transaction.stmt contains a list of engines that are participating in the given statement thd->transaction.all contains a list of engines that have participated in ...
https://dev.mysql.com/doc/internals/en/transactions-notes-on-ddl-and-normal-transaction.html
Behavior of the server in this case is currently badly defined. DDL statements and operations with nontransactional engines do not "register" in thd->transaction lists, and thus do not modify the transaction state. Besides, each DDL statement in ...