Meet Drizzle

Drizzle is an open source software database management system (DBMS), which has budded off from MySQL, therefore possesses a client-server architecture and uses SQL as the command language, is licensed under the GNU General Public License v2. The prototype was made by Brian "Krow" Eiker (MySQL director of architecture). Development is entrusted entirely to the community, among contributors are employees of Canonica, Google, Six Apart, Sun Microsystems. ©

Introduction

If you are not very far from the world of open source software, then most likely you have already heard something about Drizzle and, in principle, you can go on to the next section, for those who learn about this DBMS for the first time, some background information is below.

The Drizzle project is focused on building a lightweight version of MySQL that provides a decent level of stability and ease of use, but some features will be excluded to improve performance and scalability. The project is still very young, but is already widely known among narrow circles of open source software developers who are interested in experimenting with this product, its development and implementation in their projects. From the article you will learn how to build and install Drizzle DBMS and connect to it using PHP.

According to the official website, Drizzle is “a database optimized for cloud computing and network applications ... for massive parallelization on systems with multiprocessor architectural architecture”, distributed under GNU GPL v2, and Brian Acker from MySQL handles the whole thing.
')
Although Drizzle rebounded from MySQL, it is not intended to replace MySQL, but rather, it is designed for users who want an easy-to-use tool with MySQL reliability, has ACID properties and do not use some of the new MySQL features such like stored procedures, triggers and views.

There are also some others different from MySQL:

• The default engine is InnoDB instead of MyISAM;
• Fewer data types supported than MySQL;
• Uses a different client / server protocol from MySQL;
• It supports an extensible architecture with plug-in support, which allows developers to build a system with only those modules that are needed (essentially like Apache with PHP).

More information about the differences you can get from from this post or Drizzle FAQ .

It is important to note that Drizzle is still in the development stage and the developers themselves declare that the code is not yet suitable for use in real projects, so you are looking for what to recommend to your boss or client, you should look towards MySQL, PostgreSQL or SQLite at this moment.

Getting the distribution

Drizzle is currently available for Mac OS X, Linux and Solaris Express platforms and requires GCC v4.1 or higher; Windows is not yet supported. To get started, download the source code archive:

• Database server (drizzle)
• Protocol Library (libdrizzle)

Unpack them, compile and install them on your system, as shown below:

> tar -xzvf libdrizzle-0.3.tar.gz
> cd libdrizzle-0.3
> ./configure
> make
> make install

> tar -xzvf drizzle-2009.06.1063.tar.gz
> cd drizzle-2009.06.1063
> ./configure --with-libprotobuf-prefix=/usr/local
> make
> make install


The article will be considered Drizzle v2009.06.1063 with libdrizzle v0.3. Note that Drizzle uses the Google Protocol Buffers library, so you will probably need to download and compile it for your system. Detailed instructions can be found at the Protocol Buffers website. This article uses version 2.0.3, not a later v2.1.0, to avoid the error associated with pthreads .

By default, the Drizzle server will be installed in / usr / local / sbin / drizzled, and the client in / usr / local / bin / drizzle, after installation, create a non-privileged group and user for the server as shown below:

shell> groupadd drizzle
shell> useradd -g drizzle drizzle


You also need to create a directory for the database files and issue the appropriate rights:

> mkdir /usr/local/drizzle
> mkdir /usr/local/drizzle/data
> cd /usr/local/drizzle
> chown -R drizzle .
> chgrp -R drizzle .


After these actions, start the Drizzle server as follows:

> /usr/local/sbin/drizzled --user=drizzle --basedir=/usr/local/drizzle/ --datadir=/usr/local/drizzle/data/ &
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins.
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
090630 10:29:42 InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
090630 10:29:42 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
090630 10:29:42 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
090630 10:29:43 InnoDB Plugin 1.0.3 started; log sequence number 0
/usr/local/sbin/drizzled: ready for connections.
Version: '2009.06.1063' socket: '' port: 4427 Source distribution


The Drizzle client is very similar to the MySQL client:

> /usr/local/bin/drizzle
Welcome to the Drizzle client.. Commands end with ; or \g.
Your Drizzle connection id is 24
Server version: 2009.06.1063 Source distribution
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

drizzle>


Now you can execute SQL commands on the server, just like with MySQL.

 drizzle> SELECT VERSION ();
 + -------------- +
 |  VERSION () |
 + -------------- +
 |  2009.06.1063 |
 + -------------- +
 1 row in set (0 sec)

Create a database and add a table to it:

drizzle> CREATE DATABASE test;
Query OK, 1 row affected (0 sec)

drizzle> USE test;
Database changed

drizzle> CREATE TABLE items (
-> ItemID INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
-> ItemDesc VARCHAR(255) NOT NULL,
-> ItemQty INT NOT NULL
-> );
Query OK, 0 rows affected (0.01 sec)


According to the Drizzle FAQ, the following data types TEXT, BLOB, VARCHAR, VARBINARY, TIMESTAMP, DATETIME, DATE, TIME, ENUM, INT, DOUBLE and DECIMAL are supported. Let's continue to create our database by adding the following entries to the table:

drizzle> INSERT INTO items (ItemDesc, ItemQty) VALUES ('Bacon', 4);
Query OK, 1 row affected (0 sec)

drizzle> INSERT INTO items (ItemDesc, ItemQty) VALUES ('Eggs', 3);
Query OK, 1 row affected (0 sec)

drizzle> INSERT INTO items (ItemDesc, ItemQty) VALUES ('Milk', 1);
Query OK, 1 row affected (0 sec)

drizzle> INSERT INTO items (ItemDesc, ItemQty) VALUES ('Apples', 6);
Query OK, 1 row affected (0.01 sec)


Let's check that everything was correctly added by doing a SELECT:

 drizzle> SELECT * FROM items;
 + -------- + ---------- + --------- +
 |  ItemID |  ItemDesc |  ItemQty |
 + -------- + ---------- + --------- +
 |  1 |  Bacon |  4 |
 |  2 |  Eggs |  3 |
 |  3 |  Milk |  1 |
 |  4 |  Apples |  6 |
 + -------- + ---------- + --------- +
 4 rows in set (0 sec)

PHP support

Drizzle support in PHP is provided through the appropriate PHP extension, which provides a full-fledged API for accessing the database. This extension is currently supported by Eric Day, James Luadke and some other developers, is freely available in the PECL under a PHP license. Although the extension is under development, it allows for most of the common tasks associated with accessing and using data from Drizzle within PHP applications. You can install the extension from PECL as follows:

 shell> pecl install drizzle-beta

But in principle, you can collect from the source:

 shell> tar -xzvf drizzle-0.4.0.tar.gz
 shell> cd drizzle-0.4.0
 shell> phpize
 shell> ./configure
 shell> make
 shell> make install

After these actions, you should have a loadable module with the name drizzle.so in the PHP module directory. Enable this extension in php.ini, restart the Web server and make sure that the extension is actively calling phpinfo ():



PS
This is not a complete translation - there are no examples of application in it, but those to whom they are interested can still see them in the original article.