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

Reading data


As we have learned in the previous chapter, an indexless table can be read using two access patterns—either sequential, with rnd_init() and rnd_next() methods, or a random one with position() and rnd_pos() methods. Let's start with the former:

int ha_html::rnd_next(unsigned char *buf)
{
fseek(fhtml, current_row_end, SEEK_SET);
for (;;) {

This is one of the most complex methods in our storage engine. Let's analyze it line by line. We started by positioning the stream at the end of the last read row, and will be looking for the first non-deleted row (remember that a row starts with a<tr> tag, while a deleted row starts with<!‑‑).

But first we save the offset of the row that we will read, as it may be needed for position(), and check it against the end of data offset:

current_row_start= ftell(fhtml);
if (current_row_start >= data_end)
return HA_ERR_END_OF_FILE;

This check allows us to skip any processing and return an error at once if we have read all of the rows...