Do you hate it when you execute a query in the mysql cli only to have the output wrap three times making it almost impossible to read? Do you end up re-executing the query with \G waiting once again for the query to run? Well wait no more! My very first submitted patch to mysql is a client patch that adds –auto-vertical-output. This option compares the width of your terminal to the width of the result set and enables vertical output if it’s going to wrap. The patch link and details are Bug #26780

At last month’s Vancouver PHP Conference, local journalist Bruce Byfield gave me a quick interview about how I got involved in Free Software and Open Source. We chatted for a while about my time at MySQL, my bits of work in the PHP community and what I am currently up to. The interview turned into a profile for Linux.com that was published a few days ago.

I was a bit surprised to find that there have been a few anonymous trolls for the profile - I didn’t think that there would be any comments on the profile.

The Linux.com profile: …

XenSource launches global virtualization initiative…O’Reilly joins MySQL AB board of directors…OSBC announces keynote speakers…and more…

XenSource to Kick-off Global Virtualization Initiative, XenSource (Press Release)

Tim O’Reilly to Join MySQL AB’s Board of Directors, MySQL AB (Press Release)

InfoWorld’s Open Source Business Conference Announces Keynote Speakers for May Event, InfoWorld (Press Release)

Mr. Softy Won’t Save Novell, The Motley Fool, Tom Taulli (Article)

…

In Windows and Internet web business applications development the connection to the MySQL database server is critical and requires high-level of security. In ADO.NET database technology the connection is defined in the Connection String property of the connection object. Defining and storing the MySQL Connection String properly is an important application setting task for developers today. In this article I'll show you how to setup and secure MySQL Connection String for Windows application development using VB.NET 2005. Also the difference of programming code between VB.NET 2003 and 2005 will be provided for data loading using MySQL Connector/NET 5.0.3 database driver.

MySQL AB today announced the appointment of industry visionary Tim O?Reilly to its corporate board of directors. The company also announced that Dr. Jeffrey Pugh has joined its senior management team as vice president of engineering.

Are you seeing a MySQL error that says InnoDB support isn’t enabled, even though it is? This article explains why it happens and how to fix it. The symptom Suppose you call SHOW INNODB STATUS or another InnoDB-specific command and MySQL reports the following error: “ERROR 1235 (42000): Cannot call SHOW INNODB STATUS because skip-innodb is defined” Yet you search the MySQL configuration files and find that’s not true. And you know you have InnoDB tables, too.

I’m continuing to add new tools to the MySQL Toolkit. MySQL Deadlock Logger is for extracting and storing information about the latest recorded InnoDB deadlock. It’s not only easy to view the information from the command line, it’s dead simple to store it back into a MySQL table for analysis. I think most users will find it handy to create a cron job to record the deadlocks automatically for later analysis.

The topic of database stored procedures does not cease to divide the community of database application developers and DBAs. There are many articles around, expressing various opinions about this subject. But what do you think?

Please let me know and take this survey. The survey contains 5 multiple choice questions, and will take about 1 to 5 minutes to complete.

The results will be posted soon here on my blog at http://rpbouman.blogspot.com/. Thank you in advance!

(Disclaimer: I'm an employee of MySQL AB, but this survey does not in any way relate to my position with my employer. Also, I have made an utmost effort to write an unbiased survey. If you feel that something is wrong in this regard, please post a comment on this post.)

Today I was cloning the master using LVM Snapshot and found it was taking quite a while to catch up, which highlighted replication could be the limiting factor for this system quite soon, so I decided to check what is limiting MySQL Replication speed.

My first idea was to check it based on slow query log, happily the server was running MySQL with slow query log with microsecond resolution so I could check exactly which update queries take most time to execute. Unfortunately it did not work because Slave thread seems to have problems picking up long_query_time when it is set online, meaning changing it via
set global long_query_time=0 and restarting slave does not pick up the change.

I of course could just restart MySQL but this would make replication to be delayed few more hours …

A few days ago I had some good news on the new MySQL Bulk loader for which we added support in Kettle.

Today French i18n/translation hero Samatar checked in the code for the exact oposite, built on the “SELECT … INTO OUTFILE …” statements that MySQL supports.

As you can see, this job entry allows you to export the content of a MySQL database table to a flat file. Again, this is done completely by MySQL and therefor works at optimal speed (really fast!)
We added all kinds of helpers in the GUI so that you can easily select the table and the columns to export. All you need to do is give it a filename a separator and off you go! Not only that, you can use variables to specify almost all parameters of the job entry.

In short: another great option for those of us that work with MySQL …