Book Image

MySQL 5.1 Plugin Development

Book Image

MySQL 5.1 Plugin Development

Overview of this book

MySQL has introduced a Plugin API with its latest version – a robust, powerful, and easy way of extending the server functionality with loadable modules on the fly. But until now anyone wishing to develop a plugin would almost certainly need to dig into the MySQL source code and search the Web for missing bits of the information.This is the first book on the MySQL Plugin API. Written together with one of the Plugin API primary architects, it contains all the details you need to build a plugin. It shows what a plugin should contain and how to compile, install, and package it. Every chapter illustrates the material with thoroughly explained source code examples.Starting from the basic features, common to all plugin types, and the structure of the plugin framework, this book will guide you through the different plugin types, from simple examples to advanced ones. Server monitoring, full-text search in JPEG comments, typo-tolerant searches, getting the list of all user variables, system usage statistics, or a complete storage engine with indexes – these and other plugins are developed in different chapters of this book, demonstrating the power and versatility of the MySQL Plugin API and explaining the intricate details of MySQL Plugin programming.
Table of Contents (16 chapters)
MySQL 5.1 Plugin Development
About the Authors
About the Reviewer

Storage engine API for indexes

There are quite a few methods in the handler class that deal with indexes. Luckily, we do not have to implement every single one of them. Still, it is good to know what methods exist and what possibilities we have. The table below lists most of the handler methods related to indexes:




This is a purely informational method, similar to the table_type() method, and it returns a string with the index type. Often, it is either "HASH" or "BTREE", but it can be just anything. For example, Federated engine returns "REMOTE" here. This method takes an index number as an argument, as different indexes may be of different types.


This is, too, similar to the table_flags() method. It returns a bitmap defining index capabilities that, depending on arguments, describe a whole index, a specific key part (one column in a multi-column index), or an index prefix up to and including a given key part. Index capability flags...