Drizzle's Future Moving To Rackspace? 41
abartels writes "It seems like there's been nothing but bad news and resignations coming from Oracle since it finally managed to close the deal on Sun. Finally, there's good news in that Drizzle seems to have a bright future ahead. It just isn't with Oracle, but with the Rackspace Cloud."
Re:Better Headline (Score:3, Interesting)
off topic? it is specific to this article.
Apparently the mods are very white today.
Moving from a user to a major contributor of FOSS (Score:5, Interesting)
Since the mid 90's I've been a user of FOSS projects and products for business use - contributing where and when I can - and I've been a long time customer of Rackspace since 2001 and an employee since Jan 2007... I must say I'm thrilled by the moves my company has been making to not only be a major consumer of Open Source products but also now a major contributor to such projects. From open Cloud architecture APIs and API specifications (enabling anyone to build their own Cloud hosting systems) to big-data focused projects like Cassandra and, of course, Drizzle.
Sorry to gush here...it's just that so many companies tend to nominally use Open Source to gain market share and free development help initially and then begin to restrict documentation, support and even access to new features in a dual licensing scheme. The list of names of those that "SCO-ify" their Open Source strategy is too long and sad to mention. So, please cut me some slack as I revel in the direction we're heading at Rackspace -- I hope more companies will jump on this trend to raise the sea level for us all.
To the Drizzle team: welcome! Very happy to have you onboard and look forward to your continued contributions to the community.
Note: my comments and gushing are my own!
Re:It's still basically MySQL. (Score:3, Interesting)
I am pretty sure that PostgreSQL uses thread from version 8.0. Was that not one of the changes they made to improve the quality of their windows implementation?
But more interesting: Have Drizzle fixed the problem with views and the query optimizer. Each time I try to use views in mysql, i end up with such slow queries(Something like 100 times slower) that i have to replace the view with the query that created the view. The problem seems to be that if I select from a view and then also filter the result from an other value (Something like select * from MyView where MyFieldInTheVIewWithAnIndex=42) then mysql will always use the index used to create the view, instead of the index on the field MyFieldInTheViewWithAnIndex.