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

Compiling and linking


Our engine from the previous chapter and all other plugins had to be built manually—anybody wanting to use them needed to invoke the compiler with the correct options. This is error prone and if we were to distribute a storage engine like this our users certainly would not appreciate this manual building process. For this engine, we will try to automate the building as described in the first chapter. We will need to create three files—plug.in, Makefile.am, and CMakeLists.txt.

We can copy the plug.in file from the first chapter almost verbatim. Our new engine will only work with HTML files of a predefined fixed structure. It will not use a general purpose HTML parser, and thus we will not need to check for any libraries in MYSQL_PLUGIN_ACTIONS. Our plug.in file can be just:

MYSQL_PLUGIN(html,[HTML Storage Engine],
[Storage Engine that writes an HTML file], [max])
MYSQL_PLUGIN_STATIC(html, [libha_html.a])
MYSQL_PLUGIN_DYNAMIC(html, [ha_html.la])

Similarly we create a Makefile...