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
Credits
About the Authors
About the Reviewer
Preface

Introducing storage engines


Earlier in this book we covered Information Schema plugins. Although very differently defined, these plugins work a little like partially implemented read-only storage engines. We just have to provide the table layout and fill the rows when queried. With a basic storage engine plugin we have to do exactly the same, but there are many other methods which can be implemented to cover indexes, updates, inserts, and so on.

The storage engine plugins are implemented using two main structures:

  • A class, inherited from a MySQL class, called handler

  • A structure called handlerton

The handler class provides the methods that work on a single table such as open(), index_read(), write_row(), and so on. There can be many objects of the handler class. The handlerton object is created only once per storage engine (it is a singleton, thus the name) and provides methods that affect the whole storage engine, such as commit(), savepoint_rollback(), show_status(), and so...