Retraction: Oracle + MySQL = Bad information

One of the problems with relying on sources unaffiliated with a company is that no matter how trustworthy, they can still be wrong. Such is the case with my post on MySQL and Oracle. The information contained in it turns out to be inaccurate as I've just found out. I apologize for my original post, especially to those at Oracle, MySQL, and Sun who may be affected by it. My source was not a member of the current or past MySQL team or board.

This is not the first nor the last example of my gross incompetence.

[seo2seo]

Thank you for being honest - and for not simply removing the post (lets face it, it wasn't there for long before the truth came out).

A tough lesson in ASKING those concerned before going public - but you've shown a professionalism that's very, very rare in journalism these days.

[botchagalupe]

This is a great example of how the Enterprise 2.0 information age is indeed working very well. I have been reading that a lot of collages are banning students from using Google and Wikipedia in lue of more traditional research tools. There argument usually stems from the idea that "E20" data can have more flaws than traditional data sources. What they fail to realize is the where traditional format flaws are rarely corrected the "E20" turn around can be astonishly fast. I linked to your original post and I also have you in my rss reader so I corrected my original link when I saw your correct post..

johnmwillis.com