It was partly out of pure curiosity and partly the fact that it seemed to me there were less posts than previous years that I decided to trend out the number of posts over the past years and here we go.

The blue line shows the blog posts per month over the past six years and the black line is a polynomial trend line. There are a few points of interest which are visible and I’ll be listing here (to all their understanding):
1. The first thing which struck me negatively is that there is a decrease in posts unfortunately.
2. When sun bought mysql and oracle bought sun there is a major increase in blog posts (some political, some not) lasting months.
3. Every April there is a spike in blog posts (guess what … spot on, it’s the User Conference fever :) which will soon start again for 2011 ;)).

Now for a deeper analysis, I then separated the groups on their own, community, employees, teams and employee teams:

*** Please note that when a MySQL, Sun, Oracle employee changes status, any blog posts by that person will shift to a new group.

The same trend continues obviously, community and employees have somewhat reduced their blogging and teams and employee teams have slightly increased or kept on blogging (keep it up guys).

The community does need to move it and start blogging again, so I hope this serves a bit of a wakeup call.

More of these analysis will follow. I want to extract the list of most active bloggers in the past 6 years as well as those most active in 2010 and give thanks where is due!

Because Sharing is Caring

Whist coding mysql reverse reconciliation for Securich (the Security plugin for MySQL) I kept getting the above error! We all learn from experience and I’m definitely not going to forget about this one :).

Having stored routines calling other stored routines in a cascading fashion for four or five levels can get complicated and what I was lazy about came to bite me right back. I copy code from one proc to the other (code re-use) thus end up having same variable names in different procs and prepared statements in cascading stored routines is not a smart idea, hence the above error.

Solution:
Give prepared statements different names in different stored procedures!

Because Sharing is Caring

check it out here

As a friend explained, mysql and innodb are free as in free speech and free beer (the dream). Hence Oracle model version is only talking about ENTERPRISE versions of mysql NOT the popular COMMUNITY version. All of you who used to go to downloads.mysql.com to get your mysql + innodb fix still can do so for FREE.

Oracle have changed their products page, but haven’t deemed important to explain the changes to the MySQL community. Oversight or intentional, the news that innodb won’t come with MySQL for free anymore with the community version is NOT TRUE.

Because Sharing is Caring

Just like the storm back in April 2008 when Sun bought MySQL, another (possibly the perfect storm) happened in April 2009 when Oracle bought Sun, today the latter storm took us be “surprise” to a certain extent when Oracle released their new Editions model showing innodb removed from the classic edition. People are shouting all kinds of things at Oracle and there is a lot of confusion but I think it’s better to wait and see! We are a strong community and we won’t let this storm take us down ….. we are stronger than the Andrea Gail!

If you check out twitter be careful what you believe and don’t panic yet :) no need to migrate to postgresql or whatever.

http://twitter.com/mysql explains the version most are used to, in the download section is still and will remain there (at least that is what they are saying).

Keep you posted!

Because Sharing is Caring