Blog | Bugs | Build Farm | Events | Feature Requests | IRC | LCOV | Mailing List | Planet Drizzle | Source Code | Source Docs | Wiki
Contents |
Main Points
- Based on MySQL 6.0 source tree
- No shipped libraries
- POSIX compliance
- Micro kernel design
- Pluggable Architecture for views, stored procedures, UDFs, storage engines ...
- Sharding across multiple nodes
- Intelligent proxy
- Multi CPU/Multi Core
- Optimized field types
- Efficient memory use
- No internal ACL, use LDAP/PAM
- No database data formatting
- Cleaned up make system
- InnoDB default storage engine
- Windows compatibility removed
- Localized commandline tools and user notifications
Data types supported
- please refer datatypes [removed] from MySQL 6.0
- Following are the datatypes currently supported.
- INT or INTEGER
- BIGINT
(Since INT is optimised around 32/64 bit, need not / should not say INT(<SIZE>), instead just say INT) (Auto-increment is supported)
- DOUBLE or FLOAT
- DECIMAL or NUMERIC (for storing exact precision numbers)
- VARCHAR
- BLOB
- TEXT (Same as BLOB)
- DATE
- TIMESTAMP
- DATETIME
- ENUM
New and Upcoming Features
Following are extracted from Biran's Blog Post
Authorization with LDAP
Planned for Cherry milestone.
Drizzle will have direct support for LDAP where Drizzle will be able to fetch authorization informaiton from LDAP.
External http server and HTTP authentication can be used to authenticate to access Drizzle
Freeing Schema / Database from filesystem directories
Now Schema is a real objects and not linked to filesystem directories.
New communication Protocol
Current protocol defaults to MySQL on port 3306, but the new protocol (which under heavy development) will be using port 4427.
Embedded Innodb
Drizzle will be moving to InnoDB Embedded Server instead of InnoDB plugin. and developed by Stewart Smith
Embedded Innodb is having very small footprint (around 800K) but with full ACID compliant for Transactions.
With Embedded Innodb, Drizzle got lot many features to monitor the configuration and performance of innodb
Comparison to Innodb plugin which is used Currently in Drizzle and MySQL, Embedded Innodb plugin will be using
new storage engine APIs which is very clean and efficient
DATA_DICTIONARY.INNODB_CONFIGURATION :- Provides informaiton about the configuration parameters.
DATA_DICTIONARY.INNODB_STATUS :- Provides Innodb Status information
New Generation Storage Engine APIs
Complete Re-thinking is done for a much cleaner and simple interface to accommodate new storage engines.
Drizzle development team is designing the new interface / API from stratch using the lessons they learned so far with Drizzle and its ancestor - MySQL.
Drizzle Developers are considering all valuable feedback from storage engine developers and community aswell.
For further Reading please refer Jay Pipe's blog post
Query Rewrites
Allows Drizzle to use full potential of Storage Engines. and in future database views will be using this feature.
New Data Dictionary (data_dictionary) schema
New Data Dictionary is providing lots of information for DBAs without much overhead of the legacy systems.
For a quick example see this
Latest additions are
TABLE_DEFINITION_CACHE
TABLE_CACHE
Last Updated : Jobinau 10:42, 10 March 2010 (UTC)