Rechercher dans le manuel MySQL
29.2.4 Writing Plugins
[+/-]
- 29.2.4.1 Overview of Plugin Writing
- 29.2.4.2 Plugin Data Structures
- 29.2.4.3 Compiling and Installing Plugin Libraries
- 29.2.4.4 Writing Full-Text Parser Plugins
- 29.2.4.5 Writing Daemon Plugins
- 29.2.4.6 Writing INFORMATION_SCHEMA Plugins
- 29.2.4.7 Writing Semisynchronous Replication Plugins
- 29.2.4.8 Writing Audit Plugins
- 29.2.4.9 Writing Authentication Plugins
- 29.2.4.10 Writing Password-Validation Plugins
- 29.2.4.11 Writing Protocol Trace Plugins
- 29.2.4.12 Writing Keyring Plugins
To create a plugin library, you must provide the required descriptor information that indicates what plugins the library file contains, and write the interface functions for each plugin.
Every server plugin must have a general descriptor that provides
information to the plugin API, and a type-specific descriptor
that provides information about the plugin interface for a given
type of plugin. The structure of the general descriptor is the
same for all plugin types. The structure of the type-specific
descriptor varies among plugin types and is determined by the
requirements of what the plugin needs to do. The server plugin
interface also enables plugins to expose status and system
variables. These variables become visible through the
SHOW STATUS
and
SHOW VARIABLES
statements and the
corresponding INFORMATION_SCHEMA
tables.
For client-side plugins, the architecture is a bit different. Each plugin must have a descriptor, but there is no division into separate general and type-specific descriptors. Instead, the descriptor begins with a fixed set of members common to all client plugin types, and the common members are followed by any additional members required to implement the specific plugin type.
A server plugin contains code that becomes part of the running
server, so when you write the plugin, you are bound by any and
all constraints that otherwise apply to writing server code. For
example, you may have problems if you attempt to use functions
from the libstdc++
library. These constraints
may change in future versions of the server, so it is possible
that server upgrades will require revisions to plugins
originally written for older servers. For information about
these constraints, see
Section 2.9.7, “MySQL Source-Configuration Options”, and
Section 2.9.8, “Dealing with Problems Compiling MySQL”.
Client plugin writers should avoid dependencies on what symbols the calling application has because you cannot be sure what applications will use the plugin.
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-writing-plugins.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.