MySQL is today releasing a new ODBC driver, under the version number ODBC 5.1. It is a partial rewrite of the the original MyODBC 3.51 code base, originally developed by Monty and Venu Anuganti, including individual parts of the current 65K ODBC 5 code base. It is designed to work with all MySQL versions starting with MySQL 4.1.

The original ODBC 3.51 driver was incomplete and admittedly somewhat of a quick hack, containing some debatable code. For that reason, Connector/ODBC 5 started as a complete rewrite. After 2 years it had 65 KLOC, but no tests and was in part overdesigned. That project was started but never finished, and had some deep Qt dependencies.

In the meantime, the original ODBC 3.51 has had 6 new releases and over 200 bugs fixed. As for ODBC 5.1, debatable parts of the code have been …

MySQL Proxy 0.6.0 has been tagged and should hit the mirrors near you pretty soon.

In the last 3 month of development we added a lot more features to the proxy-core which should bring the proxy closer to your needs. As always the proxy is transparent to your application, no requirement for a special language, no special needs for a platform and all customizable for your needs.

The most powerful feature is Read/Write Splitting which allows you to scale a application which is unaware of replication automaticly cross several slaves without changes to your application. Instance Scale Out we say.

The Proxy also became a 1st class citizen in the MySQL world …

Version 1.5.0 of the innotop MySQL and InnoDB monitor is out. This release is the first in the unstable 1.5.0 branch, which will eventually become the stable 1.6 branch. I'm beginning to merge the various branches I've made to support some of our needs at my employer. This first release adds some major new features and prepares for some other large improvements and new features.

As a quick follow up to the last post on malloc() speed comparisons, I decided to extend the size out a bit to cover malloc()ing up to 500M.

Time for        128k:   0.035259
Time for        256k:   0.009718
Time for        1M:     0.478129
Time for        5M:     0.968945
Time for        10M:    0.965172
Time for        50M:    0.674316
Time for        500M:   1.018901

As you can see, once you make the jump up to mmap() (>256k), the cost is fairly well constant (give or take fluctuations). So it’s not that huge memory buffers are terrible, just that there is a cost difference between the smaller and larger buffer sizes that may or may not matter in your case.

…

The recent read_buffer issue got me curious, so I hacked up a quick (ugly) test program to see if I could show the different speeds of malloc()ing different buffer sizes. Here’s the test code:

[C]
#include
#include
#include

#define LOOP 10000

int main(void) {

int x[4] = { 128,256,1024,5*1024 } ;

int f = 0;
for(f=0;f<4;f++) {
int val = x[f];

timeval before;
timeval after;

gettimeofday(&before,0);

int loop=0;
for(loop=0;loop after.tv_usec) {
udiff = (float)(after.tv_usec + 10000000 - before.tv_usec)/10000000.0;
diff = after.tv_sec - 1 - before.tv_sec;
} else {
udiff = (float)(after.tv_usec - before.tv_usec)/1000000.0;
diff = after.tv_sec - before.tv_sec;
}
printf(”Time for %dk:\t%f\n”,val,((float)diff+udiff));

}

return 0; …

Our parent site InfoWorld has just announced it's 36 winners for this year's Best of Open Source Awards. Selected by InfoWorld Test Center editors and reviewers, these first annual Bossies celebrate the best open source software available for the enterprise. From CRM and ERP to OSes and middleware to networking, storage, and security software, our 36 winners prove that if your business is willing and your IT staff is ready, there's an open source solution that's able. Check out the winners: Apps Networking Platforms Security Software Storage Disclosure: MySQL and MuleSource both won, but Zack and I had nothing to... READ MORE

MySQL Bug Tracker

I realize that MySQL is in a transitional phase making it’s development more transparent to the community so this entry isn’t really a rant but something that will hopefully ease the transition. The public MySQL bug tracker doesn’t seem to have any way to view the history of status changes to a bug. Things like changing a bug from open to inactive. I assume there will always be things that should be hidden from bugs like links to sites internal to MySQL AB but things like simple status changes should be visible to the public.

For example on this Bug #20358 Heikki posted a comment that he was moving the bug from open to unable to repeat. Did he actually make the change? I have no idea because I can’t access the status log. Was it ever changed from unable to repeat back to open or verified? Again I have no idea…

Another …

another month, another release of connector/odbc 3.51. there?s not a lot of bug fixes in this one, but we did manage to get the bug count under 80 bugs.

the reason there were fewer bug fixes in the release of 3.51.20 (other than there being fewer bugs to fix) was that we have been hard at work on connector/odbc 5.1.0, which builds on the 3.51 foundation to bring new functionality like unicode and descriptor support. there are more features planned, and you can see the release announcement for details. i hope that we?ll be able to keep on releasing new versions of 3.51 and 5.1 on …

As one of my last posts about issues with hosting provider got great response and We got a lot of good advice and offers I decided to ask for advice another problem we have as we're growing our company - organizing good phone communications.

Our goals are rather simple though the fact we're globally distributed may put us a bit aside from typical small business needs.

Normal Phone Line We're looking to get normal business phone line which would be routed to me and Vadim withing our normal business hours and voicemail outside of them. The same line could offer extensions to reach other team members plus. Plus we'd like to get direct numbers for me and Vadim at least so people do not have to pass through choice …

I have been on vacation the last week, which meant I spent the previous three weeks at work preparing to go on that vacation. :) All in all, it was much needed. It represented the first family vacation we've taken since I was still in the Air Force (and I separated in 1999). We've taken a couple of days here or there or I've taken a week off to take care of personal things, but we finally did the week long, get away from everything vacation.

Our vacation was fairly inexpensive. We spent a week at Myrtle Beach, SC, at my mother-in-law's house. I admit this is a great convenience because Myrtle Beach is certainly a vacation location and not having to splurge on hotel and being able to minimize other expenses like food was great. But I think the most important thing was the time away and the time to destress. Given that, just about anywhere with some reasonable accomodations and some things to do (and even small towns nearby always have …