5
5
I've been wondering for a long time now about all of the changes post 4.1.
6
6
I believe there is a large market of users who never wanted them, and never
7
7
cared for them. I also wanted to question the foundations of what we built.
8
Do uses want wrong data? How often is the query cache really valuable? If
8
Do users want wrong data? How often is the query cache really valuable? If
9
9
everyone just has a root user with all privs, why carry the baggage of the
12
12
* What is the goal?
14
14
A micro-kernel that we then extend to add what we need (all additions come
15
through interfaces that can be compiled/loaded in as needed).
19
No modes, views, triggers, stored procedures, query cache, data conversion inserts,
20
ACL. Less engines, less code. Assume the primary engine is transactional.
15
through interfaces that can be compiled/loaded in as needed). The target
16
for the project is web infrastructure backend and cloud components.
18
* Is this a product of Sun/MySQL?
20
No, though several of the authors do work for Sun/MySQL. The development model is
21
one based around open collaboration. Drizzle's license is the GPL v2.
23
* So what are the differences between is and MySQL?
25
No modes, views, triggers, prepared statements, stored procedures, query cache,
26
data conversion inserts, ACL. Fewer data types. Less engines, less code.
27
Assume the primary engine is transactional.
62
69
* Can I get involved?
64
Most certainly. There is plenty to do from refactoring code, design of intereface,
65
to documentation, etc... The best way to get involved it to join the mailing
71
Most certainly. There is plenty to do from refactoring code, design of interfaces,
72
documentation and blueprints, etc... The best way to get involved it to join the
67
75
https://launchpad.net/~drizzle-discuss/
69
77
If you wish to suggest a refactoring project or an interface please email
70
78
the mailing list and keep an open mind. Do not expect anyone will work on
71
79
your idea though, you may influence someone to do that, but more then likely
72
you will need to rollup your sleaves and write some code. For very simple
80
you will need to rollup your sleeves and write some code. For very simple
73
81
bits you are welcome to ask others on #drizzle on Freenode, but please be
74
82
aware that you may be asked to email the mailing list.
82
90
requirements to review your code. This system is based entirely on trust,
83
91
and individuals who have shown that they can provide three good patches gain
84
92
credibility. Starting small is fine, patches that are just comments or are
85
event two or three line cleanups are welcome and encouraged. I would really
86
recommend anyone who wants to work on something start with something of this
87
size. Patches like these are valuable and they teach you how to work with
93
even two or three line cleanups are welcome and encouraged. I would really
94
recommend that anyone who wants to work on something first start with something
95
of this size. Patches like these are valuable and teach you how to work with
90
98
The general rule is no new code in the core of the server, and any changes
98
106
* What is the coding style?
100
108
Please look here:
101
110
https://blueprints.launchpad.net/drizzle/+spec/style-cleanup
103
112
If you have a question on this, please email the mailing list so that we can
104
clarifying the document. And when you get the answer? Please update the code
113
clarify the document. And when you get the answer? Please update the code
105
114
style document :)
107
116
* Should I email the mailing list with patches?
116
125
Deliver a microkernel that we can use to build a database that meets the
117
126
needs of a web/cloud infrastructure. To this end we are exploring http
118
127
interfaces, sharding enhancements, etc... do not expect an Oracle, MySQL,
119
Postgres, or DB2. There is no GA date at the moment.
130
There is no GA date at the moment.
121
132
We are focusing on multi-core architecture. This is not designed to run on a
122
133
wrist watch (hint, go use SQLite). We support both 32bit and 64bit but the
126
137
* Can I run a website with this?
128
No. We are stil making incompatible changes, and I certainly do not believe
139
No. We are still making incompatible changes, and I certainly do not believe
129
140
the code is production quality. Right now we are defaulting many configure
130
141
operations to generate debugging code for us so our binaries are not
131
optimum, so do not got out and benchmark this and expect it to be one way or
142
optimal. Therefore, do not go out and benchmark this and expect it to be one way or
132
143
the other. We are currently only doing benchmarks where it makes sense for
133
144
us to determine where bottlenecks are.
135
* And what is the license?
137
Drizzle inherits its license from MySQL's GPL. Any libraries not connected
138
to this are licensed under their own distribution license. All source files
139
are clearly idenified.
143
148
I am from Seattle. Drizzle is our normal form of "rain" but it is not "rain",
added
removed
DRIZZLE.FAQ
