Search Results
https://dev.mysql.com/doc/internals/en/implementing-store-lock-method.html
The [custom-engine.html#custom-engine-api-reference-store_lock store_lock()] method is called before any reading or writing is performed. Before adding the lock into the table lock handler mysqld calls store lock with the requested locks. Store ...
https://dev.mysql.com/doc/internals/en/implementing-the-info-method.html
The optimizer requests an update of table information by calling the [custom-engine.html#custom-engine-api-reference-info handler::info()] method. The info() method does not have a return value, instead it is expected that the storage engine will ...
https://dev.mysql.com/doc/internals/en/mysql-services-for-plugins.html
As of MySQL 5.5, plugins have access to server “services.” The services interface exposes server functionality that plugins can call. It complements the plugin API and has these characteristics: Services enable plugins to access code inside the ...
https://dev.mysql.com/doc/internals/en/opening-a-table.html
Before any read or write operations are performed on a table, the MySQL server will call the [custom-engine.html#custom-engine-api-reference-open handler::open()] method to open the table data and index files (if they exist). int open(const char ...
https://dev.mysql.com/doc/internals/en/preparing-for-index-use.html
The [custom-engine.html#custom-engine-api-reference-index_init index_init()] method is called before an index is used to allow the storage engine to perform any necessary preparation or optimization: int ha_foo::index_init(uint keynr, bool sorted) ...
https://dev.mysql.com/doc/internals/en/stored-programs.html
The content formerly located in this chapter is now maintained in the Stored Programs section of the MySQL Server Doxygen documentation, available at https://dev.mysql.com/doc/index-other.html.
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-insert.html
Once you have read support in your storage engine, the next feature to implement is support for INSERT statements. With INSERT support in place, your storage engine can handle WORM (write once, read many) applications such as logging and archiving ...
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/write-row.html
Synopsis virtual int write_row ( buf); byte * buf ; Description This is the write_row method. No [custom-engine.html#custom-engine-api-reference-extra extra()] hint is given currently if a bulk load is happening. buf is a byte array of data with a ...