MySQL Storage Engine

This patch adds an alternative storage engine that uses mysql as backend, instead of a big file or a spool directory. This makes some interesting setups possible and also allows to ease the disk I/O on the server (by using an external MySQL engine).

To use it, you first need to create a MySQL database, and a table to hold the store messages. We’ll use “kannel” as DB Name and “store” as the table name, but you can choose whatever you want and modify the config file to reflect your setup (more on this later).

To create the “store” table, run the following SQL query:

CREATE TABLE store ( uuid VARCHAR(36) NOT NULL PRIMARY KEY, message TEXT );

Again, you can rename the fields and modify the config to reflect your environment.

Then, on kannel.conf, you need to add a store-db group, and a mysql-connection pool:

group = mysql-connection
id = mypool
host = localhost
username = <user>
password = <password>
database = kannel
max-connections = 1

group = store-db
id = mypool
table = store
field-uuid = uuid
field-message = message

Last but not least, set the store-type to use the mysql storage engine on the core group:

store-type = mysql

As you may have noticed, you can modify the fields table, field-uuid and field-message to suit your particular database schema.

Here’s the patch against latest CVS:

kannel-mysql-storage-engine

This needs further testing (do not use it for production -yet-), please try it and let me know if you find any problems.