Hi!
On Mar 10, 2009, at 12:33 PM, Robert Hodges wrote:
What’s the strategy on compatibility between Drizzle and MySQL?
Are there any areas where Drizzle will remain fully compatible and
if so which ones?
I want to keep compatibility on the SQL layer, but the rest?
Setup, DML, etc... those are different. They have to be... otherwise?
We couldn't make fundamental changes.
One thing I can really see us needing is a "mysql2drizzledumper"
program.
Based on Brian Aker’s recent talk at the San Francisco MySQL Meetup,
the list of differences is pretty long. Even if much SQL syntax is
preserved, there are changes to basic datatypes, client libraries,
management, replication, and supported storage engines to name a
few. Moving applications to Drizzle looks like a one-way migration.
We will be able to replicate out to MySQL. That will be pretty simple
(and the same to Postgres for that matter). What won't be easy is
replication from MySQL to Drizzle.... there is no API in the MySQL
server to work from (wel... besides just using mysqlbinlog).
I expect Drizzle will be used more for new application design, or in
cases where people are currently bottlenecked for performance (like a
few of the current early adopters... they need performance and can
skip replication for the time being).
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
