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

Updating the table


There are three primary methods that modify the table data. They are write_row(), delete_row(), and update_row(), which are used by the INSERT, DELETE, and UPDATE statements accordingly. In our engine, write_row() is the most complex one.

int ha_html::write_row(uchar *buf)
{
if (table->timestamp_field_type &
TIMESTAMP_AUTO_SET_ON_INSERT)
table->timestamp_field->set_time();
if (table->next_number_field && buf == table->record[0]) {
int error;
if ((error= update_auto_increment()))
return error;
}

Almost every engine's write_row() method starts with these lines. They update the values of the TIMESTAMP and AUTO_INCREMENT fields, if necessary. Strictly speaking, the second—AUTO_INCREMENT—block is not needed here. Our engine does not support indexes, that is, it can never have an AUTO_INCREMENT field.

fseek(fhtml, -FOOTER_LEN, SEEK_END);
fprintf(fhtml, "<tr>");

We write a new row at the end of the file. That is, we position the stream...