-
"To close out, let's try to answer our questions about the dartboard of the opening paragraph. Based on the PITCHf/x results it appears that a fastball thrown at a dartboard placed over home plate will hit the bulls-eye with some part of the ball a little less than 1.5 percent of the time. Fully 46 percent of these pitches would miss the dartboard completely. Just think of that when they tell you about somebody's pinpoint control."
-
standards are indeed important. it's just difficult to get buyers to think beyond the present.
-
who's using what in the Ruby world
-
interesting
-
more FJM
-
questioning the interaction between the Drizzle and the MySQL projects
-
the obvious conclusion: there are a lot of pirates
-
still bummed about this
tecosystems
links for 2008-12-01
Share via Twitter Share via Facebook Share via Linkedin Share via Reddit
Brian Aker says:
December 1, 2008 at 7:49 pm
Hi!
Ian’s blog lacks a comment section so I will just answer here.
The bug he references doesn’t exist in Drizzle (one of the advantages of simplifying is that a number of bugs just drop out of the system).
In general though? There is no bug flow from Drizzle to MySQL. So all of the bug fixes we have made to turn Drizzle into an ACID compliant/OLTP type system? I don’t see those going back (and there are hundreds). On the same token their bug fixes? Other then the bug fixes for the optimizer we just do not see them.
Both projects get fed Innodb, so as far as that goes we are similar (though we have community pushing for Google/Percona patches).
Really though, this is not too surprising and it is not all that bad. Our internals are different enough that in many cases fixes would not work directly.
We are though almost finished with a new testing framework that will allow us to verify our bugs on both Drizzle and MySQL. Which is super useful since we can discover regression or just “this was always broke”.
Anyway, this is the state today. I don’t know what the future will hold.
Cheers,
-Brian
tecosystems » MySQL: Now and Then says:
December 21, 2008 at 9:56 am
[…] entry here, but Brian was kind enough to drop by and comment on that, describing the current state thusly: In general though? There is no bug flow from Drizzle to MySQL. So all of the bug fixes we have […]