There's a thought provoking article by open source guru Bernard Golden over at the CIO blog web site called "Why CIOs Don't Care About Open Source."  The title alone is enough to give me pause; and sometimes that's the key to a good article.  Get people to stop and think about an issue and start a dialog.  Golden identifies some of the reasons why large companies might not see open source is strategic: it's low dollar amount, it's not "analyst approved" or the IT department is busy maintaining and optimizing the last generation of software rather than looking forward to the next. 

While these are no doubt valid observations of many overworked CIOs, I think likely is not the case among more innovative companies.  We've sold a lot of MySQL to companies where the CIOs have established an open …

I've already sent out the invitation and announcements to various channels, but let me repeat it once more: the 5th Hamburg MySQL User Group Meetup is coming up on Monday, 5th of Februrary. So far, 15 people have already RSVPed, so it's going to be a fun evening again. If you have not done so yet, please register via meetup.com or Xing soon! I will give a 15 minute lightning talk about "What's new at MySQL AB", but we're still looking for another MySQL-related talk. If you want to share your experiences with MySQL or talk about a certain application or tool that has a relation to MySQL, please let me know! As usual, we'll meet a 19:00 at the Chinese Restaurant "Ni Hao", …

It looks like it looks like there are going a lot of discussions about future of MySQL Community Binaries, see for example this post and Kaj's clarifications.

Obviously now it grew to a lot of speculations and many comments are far from real story. It is also really interesting to watch MySQL try to balance situation of maximizing revenues and minimizing missing off community at the same time. It is moving target and balance may shift in the future one direction or another depending on how things go.

Some of confusion I guess comes from my post where I speak about recent version and so recent binaries which were not available at that point. In many cases "recent" …

Some days ago I had the pleasure to interview Andrey Hristov, who is a developer at MySQL AB. He joined the team after working on a new feature for the MySQL Server as part of his master's thesis. You can read the full interview on the MySQL Developer Zone. Enjoy!

From: http://tinyurl.com/299h29

Oracle Updates Free SQL Developer Tools
Oracle Corp. has released the first major upgrade to SQL Developer, its free visual database development tool. The new version can browse non-Oracle databases, including Microsoft SQL Server and Access and MySQL AB?s open-source MySQL. The SQL Developer 1.1 tool simplifies the creation and debugging of code in standard SQL and in Oracle?s proprietary PL/SQL programming languages.

Roland Bouman has an excellent blog post on it:
http://rpbouman.blogspot.com/2007/01/oracle-sql-developer-11-supports-mysql.html

Some people have been saying that MySQL will not provide any more binary releases for its Community users, and that from now on you’ll have to build from source or pay up. Say it ain’t so!

It ain’t so.

Yes, it’s true that MySQL 5.0.33-community is a source-only release. However, this does not mean that all future MySQL Community Server releases will be source-only! In fact, we are planning another (probably 5.0.35) Community release in the near future, that will include binaries that you can download from dev.mysql.com/downloads, same as always.

But don’t take my word for it, when you can read for yourself what Kaj Arnö has to say about it.

In …

Sitting in Logan waiting for my flight back to Seattle I got to looking over my notes on Asterisk and realized an update to my blog was in order.

O'Reilly has put up a wiki for their forthcoming "Asterisk Cookbook". If you have ever wanted to be a part of an O'Reilly book, this is your chance.

I will be speaking on the 1st of March at O'Reilly's Emerging Telephony Conference on "Trixbox -VoIP Hacking at Home" (and yes I talk a bit about MySQL in it). I've been working on some hacks involving my WRT54GL units that I am going to bring up, along with a few new hacks I have been working on. I am really looking forward to this conference, the schedule looks to be excellent.

The traffic to …

The amount of data out there via API's is increadible these days. For instance you can take an address, and get the latitude and longitude using Google's GeoCoding API.

I am using this API along with some others to build a pretty some interesting stuff (more on that when its public).

Today I needed to calculate the distance between two points, I found a bunch of formulas here to convert two lats and longs into miles. They had some more complicated formulas, but I went with an easier one because approximate accuracy was sufficent. Here's how the formula translated into SQL (tested on MySQL):

SELECT id, place_name,
ROUND( SQRT( POW((69.1 * (#Val(arguments.latitude)# - latitude)), 2) + POW((53 * (#Val(arguments.longitude)# - …

Yesterday I spent a few hours going over the internals of MySQL with
the Falcon team.

At some point we hit the "and why does that work like that?".

It was because of copy and paste, or as I think of it in code as
"evolution by the lucky". When code is well documented, encapsulated,
or just plain understandable one developer will copy and paste it to
another section of the code.

Now where does the lucky part come it? My description sound more like
survival of the fittest?

Well now let us insert reality. Sometimes someone copies and pastes
code because they believe it is doing what they want, and they don't
always get it right. Other times there is a flaw in the code that
isn't found for some time. Survival of code occurs because of luck.

In a single code base you can solve this with libraries. Instead of
…

A small bug/feature, which I created a new bug for at http://bugs.mysql.com/25706. Basically, the CURRENT_DATE() function seems to assign a time to dates, and that time is 00:00:00. In fact, all DATE formats are actually DATETIMEs with the date field of 00:00:00 and hidden.

This interferes with queries that use the date as an actual date and expect the date to include everything up until 23:59:59 of that day. The easiest way to reproduce this:

SELECT IF(NOW() BETWEEN '2007-01-17' AND '2007-01-18','yes','no') AS test\G
test: no
1 row in set (0.00 sec)

In fact, the following query always returns “no”, unless it’s exactly midnight:

SELECT IF(NOW() BETWEEN CURRENT_DATE() - INTERVAL 1 DAY AND CURRENT_DATE(),'yes','no') AS test\G
test: no
1 row in set (0.00 sec)

This does not make logical …