2
2
Notable MySQL Differences
3
3
=========================
5
Drizzle was forked from the (now defunct) MySQL 6.0 tree in 2008. Since then there have been a lot of changes. Drizzle is in some ways similar to MySQL, and in other ways, unrecognizable.
7
This section of documentation aims to explore some of the notable differences between MySQL and Drizzle, and has been modified from its original state on the Drizzle Wiki.
5
Drizzle was forked from the (now defunct) MySQL 6.0 tree. Since then there
6
have been a lot of changes. Some areas are similar, others unrecognisable.
8
This section aims to explore some of the notable differences between MySQL
11
This section was originally adapted from the Drizzle Wiki.
13
17
* Drizzle is optimized for massively concurrent environments. If we have the
14
18
choice of improving performance for 1024 simultaneous connections to the
15
19
detriment of performance with only 64 connections, we will take that choice.
16
* It is designed for modern POSIX systems
20
* Designed for modern POSIX systems
17
21
* Microsoft Windows is not a supported platform (neither is HP-UX or IRIX).
18
* Drizzle doesn't use timezones. Everything is UTC.
22
* No timezones. Everything is UTC.
23
* No scripts/mysql_install_db or similar. Drizzle aims for a "just works" installation, without administrative overhead.
27
* No scripts/mysql_install_db or similar. A "just works" installation
28
mentality without administrative overhead.
24
29
* No system database that needs upgrading between versions.
25
30
* Drizzle can listen on the Drizzle port (4427) and/or MySQL port (3306)
26
31
and speak the respective protocols.
31
Drizzle is designed around the concept of being a microkernel. There should
36
Drizzle is designed around the concept of being a micro-kernel. There should
32
37
be a small core of the server with most functionality being provided through
33
38
small, efficient and hard to misuse plugin interfaces. The goal is a small,
34
light weight kernel that is easy to maintain, understand and extend.
39
light weight kernel which is easy to maintain, understand and extend.
36
Drizzle is written in C++ and makes use of the Standard Template Library (STL)
41
Drizzle is written in C++ making use of the Standard Template Library (STL)
37
42
and Boost. Only where performance or correctness proves to be inadequate will
38
we consider rolling our own; our preference is to fix the upstream library
43
we consider rolling our own, and our preference is to fix the upstream library
44
49
Pluggable network protocols allow Drizzle to speak one (or more) of several
45
50
protocols. Currently we support the MySQL protocol (compatible with existing
46
51
MySQL client libraries) and the Drizzle protocol which is still under
49
The Drizzle protocol embodies several important differences from MySQL:
52
development but aims for several important differences:
51
54
* Client sends first packet instead of server
53
* Multi statement support (without using a semicolon to separate them)
54
* Room for expansion to include NoSQL type commands inline with SQL.
56
* multi statement support (without using a semicolon to separate them)
57
* room for expansion to include NoSQL type commands inline with SQL.
56
There is also a console plugin -- instead of providing access over a network
57
socket, this plugin allows access from the current tty.
59
There is also a console plugin that instead of providing access over a network
60
socket, allows access from the current tty.
62
The existing plugin APIs that Drizzle inherited from MySQL have been reworked.
65
Existing plugin APIs inherited from MySQL have been reworked.
64
* User Defined Functions (UDFs) now follow the same API as a given
67
* User Defined Functions (UDFs) now follow the same API as within the
65
68
server instead of a different C API. This means that UDFs are on the
66
exact same level as built-in functions.
69
exact same level as builtin functions.
67
70
* Storage Engine API has had some parts extensively reworked, especially
68
71
around transactions and DDL.
69
72
* Logging is now pluggable
82
Drizzle does not currently have any plugins that implement stored procedures. We
85
Drizzle does not currently have any plugins implement stored procedures. We
83
86
viewed the implementation in MySQL to be non-optimal, bloating the parser
84
and only supporting one language (SQL2003 stored procedures), which was not
87
and only supporting one language (SQL2003 stored procedures) which was not
87
90
Fundamentally, stored procedures usually are not the correct architectural
88
91
decision for applications that need to scale. Pushing more computation down
89
92
into the database (which is the trickiest layer to scale) isn't a good idea.
91
We do recognize that the ability to reduce the time row locks are held
92
by using stored procedures is valuable, but think we can achieve the same
93
advantage by improved batching of commands over the wire instead of adding and
94
We do recognise that the ability to reduce the time row locks are held
95
by using stored procedures is valuable, but think the same advantage can
96
be gotten with improved batching of commands over the wire instead of adding
94
97
administering stored procedures to the list of things that can go wrong in
95
administering the database.
98
admisistering the database.
107
110
SQL Views are not currently supported in Drizzle. We believe they should be
108
implemented via a query rewrite plugin. See the `Query Rewrite Blueprint <https://blueprints.launchpad.net/Drizzle/+spec/query-rewrite>`_ on launchpad.
111
implemented via a query rewrite plugin. See the `Query Rewrite Blueprint <https://blueprints.launchpad.net/drizzle/+spec/query-rewrite>`_ on launchpad.
113
116
INFORMATION_SCHEMA
114
117
------------------
115
The INFORMATION_SCHEMA provides access to database metadata.
117
119
The INFORMATION_SCHEMA in Drizzle is strictly ANSI compliant. If you write
118
120
a query to any of the tables in the INFORMATION_SCHEMA in Drizzle, you can
126
128
Authentication, Authorization and Access
127
129
----------------------------------------
129
Authentication lies in Drizzle plugins. Currently there are PAM and HTTP AUTH plugins for authentication.
131
Plugins. Currently there are PAM and HTTP AUTH plugins for authentication.
130
132
Through the PAM plugin, you can use any PAM module (such as LDAP).
132
134
Command line clients
157
159
There are no FRM files in Drizzle. Engines now own their own metadata.
158
Some still choose to store these in files on disk. These are now in a
160
Some choose to still store these in files on disk. These are now in a
159
161
documented file format (using the google protobuf library).
added
removed
docs/mysql_differences.rst
