If you track the database world outside of MySQL, you know that Oracle is having a conference this week. It’s called Oracle Open World. Drips with irony doesn’t it? But this post isn’t about Oracle being open or otherwise. This post is about the announcement being made Wednesday. It seems Oracle has a surprise. A pretty well kept surprise. It’s such a big deal that Larry Ellison himself is making the announcement.
Last week I speculated about the impact of Monty leaving Sun. In the end, if he does stay, it’s wonderful for Sun. If he leaves, he will no doubt go on to continue to be wonderful for the database community at large, much like Jim Starkey. But until Monty Says, nothing is official.
Scenario: Someone wants to know which of the over 50 MySQL users have certain privileges. There are many ways to solve this problem. Some of these scenarios are tedious and repetitious, others take no time at all. The issue, of course, lies in what the “certain” privileges are. If it is “who has the SUPER privilege?” then a simple SELECT user,host FROM mysql.user WHERE Super_priv=’Y'; is sufficient. If it is “who has write access to the foo database”, you might write: SELECT user,host FROM db WHERE Db=’foo’ AND Select_priv=’Y'; but that only shows who explicitly has read permissions on that database; it does not include those who have global read permissions. The full query would be….
Last week Giuseppe Maxia announced the Call for Papers for the 2009 MySQL Users Conference and Expo, and also announced that there would be an unconference, MySQL Camp, organized by me. It’s true! Currently MySQL Camp is set to happen, though I am still working out details with Colin Charles and Giuseppe Maxia. We had originally talked about having MySQL Camp on Tuesday and Wednesday, but I would like to add Monday so that folks attending the conference who are not attending a tutorial have a choice on Monday. I am also looking into lunch options, since the conference venue does not have many options within walking distance.
ValleyWag reports that MySQL’s Monty Widenius is no longer “MySQL’s”. Some folks have known that Monty has not been happy in his current position; this leads me to believe the rumor is true (though of course an official announcement is the only confirmation). So what does this mean for MySQL? Well, honestly, if a product falls apart because one out of 300 employees leaves, it was probably doomed anyway. There are plenty of capable employees left, and being owned by Sun means that there are many more resources they can tap as well.
What will the official company announcement be? My prediction is
Hey everyone — it’s time to send in your article proposals for the next issue of MySQL Magazine, which is scheduled for release on October 15th. The deadline is end-of-September, so don’t delay. You too can become famous by writing for MySQL Magazine! Just send me your idea for an article to bmurphy AT paragon-cs.com. Looking forward to hearing from you.
Though the event is still happening in Charlottesville, VA Nov. 14-16th (Fri night through Sunday), the new web page for OpenSQL Camp is http://www.opensqlcamp.org. The content has been ported over to MediaWiki, and a captcha has been put in place that is activated on any page change that adds an external URL. Whether you are into MySQL, PostgreSQL, Drizzle, or some other open source SQL database, go forth and register for OpenSQL Camp, without having to login! (Disclosure: if you do not create a login, your IP is tracked.)
The Malta MySQL User Group (MMUG) met for the second time this Thursday, and compared to last time, we had a much better venue: Ixaris Systems let us use their board room, so we had all the tools we needed to have a good meeting. Overall, I’m very pleased with this meeting, we had some valuable talks and questions raised during the presentations, and some very good company in good venue. I’d like to thank Pythian, Ixaris, and the MySQL Community team for their support in helping us.
Now, for my original purpose, I can do something like this to set my variable: SET GLOBAL
I have not said much about Drizzle here; that is because there is not much to say. It is premature, really, to say anything about it at this point. Some have said they will support Drizzle; as Pythian supports several database systems, it is very likely that we will support Drizzle as well. Particularly since there is in-house Drizzle expertise already. But I digress; my point is that it is premature to really say much about Drizzle.