MySQL EMEA Support Team gathering!

I’m back from the MySQL EMEA Support Team meeting.. and it was just fantastic!

Most know that MySQL is a virtual company and we don’t see to much colleagues. Most goes via our internal IRC server, email and phone. However, we in Support for example, try to meet up each year. This year we did it a bit differently by actually gathering and actively doing support together (in Bielefeld, Germany). You know, like in a real office!

The cool thing about the EMEA Support Team, and I can safely say this for the global Support Team, is that we simple play along very well. Each of us comes with baggage of experience when joining MySQL. Most importantly, we think mostly alike. When we disagree we settle or make it better. For people only meeting up once a year or less it is just spectacular!

It’s also lots of fun and drinking beers, socializing and sleeping together.. I mean sharing rooms! Fact that I had my birthday (turned 30) didn’t make it easy for me (always a bit down then..) but my colleagues got me in the hotel alright.

Anyway, we’re looking for more Support Engineers all over the world! It’s not an easy job, it’s challenging and you got work from home (not as easy/good as it sounds, btw). But damn, it’s the BEST job in the universe!

MySQL 5.1 knows /etc/mysql/my.cnf

OK, this is maybe no big news and maybe old, but I needed an excuse to blog something!

Since MySQL 5.1.15 the /etc/mysql/my.cnf has been added as default location after /etc/my.cnf. This is great and something I like keeping /etc a bit cleaner, but it might be tricky for some not knowing!

I found this the hard way and a bit with red cheeks (I’m a MySQL Support Engineer after all..). After installing postfix-mysql Ubuntu package, which also sets up common MySQL stuff, I couldn’t connect to my fresh installed 5.1.19. Confused, I saw it was using a socket setting I didn’t specify. So, /etc/mysql/my.cnf was read extra to /etc/my.cnf! I said ‘doh!’ and saw it was good.

Tip: leave /etc/my.cnf there for a while with a warning like “You’re living in the past dude! Check /etc/mysql/my.cnf”, or something.

Next would be to read /etc/mysql/config.ini for MySQL Cluster too, but work is on its way to make this file obsolete anyway.