In a previous post I wrote about how I have started implementing asynchronous I/O into the MySQL client library. I plan on contacting and working with other client API maintainers (PHP, Python, Ruby, …) to make sure this functionality gets pushed out to those places too. Any comments or suggestions on how the interfaces should behave are of course welcome, and I’ll get patches posted somewhere for testing once I have the basics working. This is also my first project going through the MySQL Community Contributions Program so it can be included as part of a later release. I sent out the first contact e-mail to MySQL a week ago, but have not received any response yet. Anyone at MySQL listening? :)

For those of you new to the idea of asynchronous clients, check out …

In the tradition of creative names for MySQL related projects ...

<weigon_> arj... no arjen :(
<dormando> haven't seen him in a few days, huh
<weigon_> http://code.google.com/soc/2008/mysql/appinfo.html?csaid=B0E0C3111A6494AB looked like a proxy job
<weigon_> tokenize the query, replace the constants and rewrite the resultset to something harmless
<dormando> sounds easy
<weigon_> in the tradition of http://jan.kneschke.de/2008/4/23/mysql-proxy-commit-obfuscator
<dormando> :)
<weigon_> I really would like to see applications falling apart when this script is put in between
<dormando> mine fall apart on their own. I need proxy to put them back together :(
<weigon_> Bandaid for MySQL ? :)
<dormando> Pretty much :(
<weigon_> is "bandaid" is trademarked ?
<dormando> It's a brand, so yes I think
<weigon_> otherwise it is ... damn
<dormando> the real term is adhesive-strip or …

OpenSolaris OS 2008.05 is now available for download.  Its quite a departure from traditional Solaris. Why? because the CD that one will be downloading is probably just a chapter in the full book. To understand the full picture one will have to really look at the bigger picture on how the whole deployment model is now changing. The full scope is not my topic of discussion but I probably want to focus on probably couple of pieces today in order to demonstrate on how to create a PostgreSQL OpenSolaris LiveCD.

In order to create a custom LiveCD, its probably best to start with OpenSolaris OS 2008.05 installation though it is not necessary as it can be done on Solaris Express installations also but needs pkg(5) to be installed. But the two things really required to create a custom LiveCD, you need one kit to download and a repository to access. The kit to download …

Check out the new OpenSolaris page and download the new OpenSolaris binary distribution.

You can easily download the integrated MySQL packages by using the Package Manager GUI or simply

pkg install SUNWmysql5

As part of the MySQL packages the MySQL Cluster (NDB) storage engine and management binaries are included. You can use the general documentation available at MySQL.comfor setting up a Cluster . Then you should be ready for high availability MySQL.

What I love of MySQL as a user is that you can google MySQL <anything> (where <anything> is nonterminal… or perchance not :-) and always found some useful results!

It happens to be also the case for MySQL development. I had struggled a bit with MySQL code but I’m on my way out of initial panic and I am quite positive right now. As I reported, I started with a look to the handler interface (plus the handlerton data structure and some subclasses of handler): to better understand those types, I had to take a look to other files and sometimes got lost, so I thought I would benefit from an introduction to MySQL development. So I went through the MySQL Internals guide. It was an …

Thanks to all the attendees to the session on creative programming with MySQL at CommunityOne.
As announced, the slides are online.
3.5M (PDF)
Enjoy!

Today is my first official day with Kickfire. I've spent most of the day reading up about how the appliance works and trying to wrap my head around some of the finer details.

My starting role here is essentially as an internal consultant, which means that I'll be the one that gets the MySQL server related questions from the development team. This is going to allow me a chance to really sink my teeth further into the source code and help implement some really cool tech, which has me quite excited.

Later I will be doing some external consulting (sales, implementation, etc) that will allow me to travel a bit.

Overall, I think this position is a great fit for me and I'm really psyched.

As you all know, MySQL is participating in the Google Summer of Code 2008. Its the community bonding period now, and real work only starts on May 26 2008.

Just a couple of highlights:

• Raj Kissu Rajandran, a student at APIIT, in Malaysia, is the first Malaysian to participate in the MySQL project. I was under the impression that he was the first Malaysian in general, but it turns out that that he has competition in another project as well… He’s mentored by Marc Delisle from phpMyAdmin, but also has a co-mentor that is Ronald Bradford from PBXT/PrimeBase. Interest stuff.
• Filippo Bollini, mentored by Brian Aker, has already started writing weekly reports, and has a most impressive …

It’s been a while since I had chance to work on Informeer as my itch was one of multi-user web based password management (AuthStor). Oh and moving house.

Now that things are settling down again (Servers back up and running) I decided to take a break from AuthStor and focus on something new – Informeer.

The concept is simple, Centralised Notification.

I am forever configuring notifications from several sources, be it backup alerts, host monitoring notification and even simple applications that send mail via SMTP. When living in a world of change, both software and business, having to visit every application to change an e-mail address or add a new user to a notification schedule can be quite time consuming. Add to that the effort of having to modify firewalls, SMTP servers and XMPP …

i was going to write some reactions to an observation that postgresql has no bug tracker and its discussion last week, but lost the spark and abandoned the post after a few days. but today i ran across a quote from linus torvalds that neatly sums up my thoughts:

We’ve always had some pending/unresolved issues, and I think that as our tracking gets better, there’s likely to be more of them. A number of bug-reports are either hard to reproduce (often including from the reporter) or end up without updates etc.

before there was a bug tracking system for mysql, there was a claim that all bugs were fixed in each release (or documented), and there has been a lot of pain in seeing how well that sort of claim stacks up against a actual …