We announced the results of our third fiscal quarter (Q3) on Thursday last week, and the results weren't what I, or any of us, wanted.

As you can read in the press release, we delivered $3.267 billion in revenue for Q3, roughly flat with a year ago. On that revenue, we delivered a GAAP loss of 4 cents (equal to the charge associated with the acquisition of MySQL, which closed within the quarter) - on that revenue, we generated around $320m in cash.

The low light of the quarter was revenue in the US - which declined year over year by nearly 10%, a big step down for a geography that typically contributes 40% of our total revenue. The highlight of the quarter was our India performance, up 30% year over year - and our chip multi-threading Niagara systems, which grew (billings) 110%.

We had growth in 12 of 16 geographies …

At the 2008 MySQL Conference and Expo, the closing keynote was Jacek Becla speaking on "The Science and Fiction of Petascale Analysis". See the slides on the Forge at http://forge.mysql.com/wiki/MySQLConf2008ThursdayNotes#The_Science_and_Fiction_of_Petascale_Analytics

Two month have passed since the close of the Sun-MySQL-Deal, two months of uncertainty whether it's a good idea to join Sun or not but after consulting my ElePHPant, who read the 18 pages of the contract and related documents (including MySQL termination agreement, data privacy agreement, ...), I'm quite optimistic and look ahead to a sunny future. Therefore I'll be a true Sun employee as of tomorrow, May 1st.

At the 2008 MySQL Users Conference and Expo, Mårten Mickos handed out the 2008 awards for Application, Partner and Community Members of the year See all the blog posts others have written about the tutorial from the Forge Wiki at http://forge.mysql.com/wiki/MySQLConf2008TuesdayNotes#State_of_MySQL.

In a little app where users can create tabs and portlets in those tabs I ran into some issues with my ordered list implementation. It turns out I just misplaced a filtering expression in the WHERE clause instead of the JOIN condition. The basic idea was that I wanted to add new portlets in the left hand column at the top. The positions from the portlets actually start at 0, but what I am doing is to insert them at 1 below the current minimum or -1 if the table is empty. Then in a second query I push everything up by one. Seemed like the most efficient way to deal with concurrency. I guess in theory I could even skip pushing things up by one, but oh well.

Here is the original query (note that I am using PDO which supports Oracle style named placeholders for all drivers including MySQL):

INSERT INTO user_tab_portlets (tab_id, portlet_id, pos, col, is_open, config)
            (SELECT :tab_id, :portlet_id, COALESCE(MIN(utp.pos)-1, …

Inspired by the Rail Spikes:

bash-3.2$ history 1000 | awk '{a[$2]++}END{for(i in a){print a[i] " " i}}' | sort -rn | head

228 cd

167 git

10 ssh

10 DEPLOY=production

6 sudo

6 pwd

6 ./script/import_views.rb

5 rm

4 rake

4 mv

bash-3.2$

Really interesting stats, I’d never guess that git is used more than ssh on my desktop (I’m a remote worker and mysql consultant so I ssh really often).

Hello my dear readers.

Today I have a question for all of you. What platforms (32bit or 64 bit) do you use for your servers with more than 4Gb RAM? I’m asking because recently we‘ve hit few really weird bugs in Linux kernels 2.6.18 to 2.6.22 and all those bugs were PAE-related. Now I’d really love to move all machines to 64-bit, but I’m in doubt because we don’t know too much about Rails stack (ruby, mongrel, haproxy) on 64-bit platforms (all our DB boxes are 64-bit of course).

So, please drop me a line if you have any experience (negative or positive) with Rails platform on 64-bit machines. I’d really appreciate your help.

So now that you have posted some clarifications on what is going on exactly, it seems like there is less of a problem as original thought. However I must say that the the replies you posted on Jeremy's blog (and later mine as well), you let me to believe that things are quite bad indeed. Only now that I see your two posts on /, I can relax a bit again. Matthew has written a very good …

Once again Jeremy weights in on the oddity called "MySQL Enterprise Edition". This time around it seems that Sun/MySQL is moving towards making their Enterprise Edition more proprietary by including features that will never be available in the Community Edition. Not sure, but I guess they are also not providing the source to the general public (I do not remember all the details of the continued mumbo-jumbo saga surrounding this product, but maybe they already pulled the source from the public version a while ago - please correct me here). I do assume that paying customers will still get the source, though obviously not under an open source license.

As before MySQL AB illustrates that they …