In MyQuery 3.3, where I just released version 3.3.2 which includes some MySQL Cluster NB specific fixes, there is some support for accessing MySQL Cluster / NDB beyond what is available as ndbinfo table and such things. MyQuery is a Windows based MySQL GUI, if you didn't know that already, and just because you run this tool on Windows (it is only supported on Windows), doesn't mean you cannot monitor a Cluster that runs on, say, Linux. Or Windows, should you so wish.

There are 2 predefined tools that support MySQL Cluster there, one that uses the ability to predefine a SQL statement that runs in a non-modal dialog and is optionally updated and one that uses the feature that allows a DLL, using a sepcfic MyQuery API, to run as a tool, and in this case, this tool is linked up with the NDBAPI to allow monitoring and a certain amount of control overthe Cluster.

Monitoring NDB Cluster memory usage
In MySQL Cluster / …

Issue #2134 reported that there are users which do not have the privilege to fire a LOAD DATA command, which rendered HeidiSQL's "import textfile" feature useless for them. So, I recently implemented a client-side parser for CSV files. The new parser does its best to detect the right values while avoiding any slow loop code. On huge files it's slightly slower than a LOAD DATA command processed on the server but I think that's very ok, especially if there is no alternative to a client-side parser.



Another new useful thing is the option "Input file contains local formatted numbers", which basically converts the local decimal and thousand separators to those chars MySQL expects. This allows fixing wrong numbers being inserted into your database, e.g. in cases of german numbers of let's say 12.345,6789 which is parsed by the …

Issue #2134 reported that there are users which do not have the privilege to fire a LOAD DATA command, which rendered HeidiSQL's "import textfile" feature useless for them. So, I recently implemented a client-side parser for CSV files. The new parser does its best to detect the right values while avoiding any slow loop code. On huge files it's slightly slower than a LOAD DATA command processed on the server but I think that's very ok, especially if there is no alternative to a client-side parser.



Another new useful thing is the option "Input file contains local formatted numbers", which basically converts the local decimal and thousand separators to those chars MySQL expects. This allows fixing wrong numbers being inserted into your database, e.g. in cases of german numbers of let's say 12.345,6789 which is parsed by the …

Why should you convert myisam tables to innodb ?

For the perfectly simple reason that innodb tables do not get locked by concurrent selects & inserts. So if you find that your myisam table is suffering for too many locks - due to concurrent selects and inserts, it is time for you to covert the table to innodb.

The simple query which does the trick is

Alter table myisam_table_name engine =

I will be in Manila, Philippines from September 13 – 17 2010. If you want to learn more about MariaDB, talk about MySQL, or just talk about open source in general, there are several opportunities for this:

• Y4iT 2010 (event is September 14-17): Thursday, September 16 2010, 1.50pm, the talk I will give is titled: MariaDB: The new M in LAMP. It was a popular attention grabber during OSCON, where we had a MariaDB booth, and this is a completely new talk, so should be fun to give in front of a huge audience.
• MySQL/MariaDB Meetup on September 16 2010, 4-6pm, at Bahay ng Alumni. This is a meetup, and will be informal, so good for Q&A. Manila doesn’t have a regular MySQL Meetup group, and we’re hoping to kick something off here. Much thanks to Rom Feria, who helped putting everyone together to …

MariaDB just released MariaDB 5.1.50. Linux, Solaris and Windows (32-bit) are supported. Go give it a twirl.

Its also worth noting that today when you go install Drupal, and check out the documentation for requirements, you’ll see that MariaDB is now a recommended option.

Via the new news page at Monty Program’s newly designed website, I also found out that MariaDB is now recommended in the documentation for the next release of the Zend Framework. See the …

Dear MariaDB users,

MariaDB 5.1.50, a branch of the MySQL database which includes all major open source storage engines, myriad bug fixes, and many community patches, has been released. MariaDB: Community developed, feature enhanced, backward compatible.

For an overview of what’s new in MariaDB 5.1.50, please see the release notes.

Highlights include MariaDB 5.1.50 based on MySQL 5.1.50, includes XtraDB 5.1.49-12, and have some bug fixes in the Aria storage engine. For finer grained details, please view the changelog.

MariaDB is available in source and binary form for a variety of platforms and is available from the download pages.

Enjoy!

I have released MyQuery 3.3.1 now. This is a minor release in many ways, but still significant in others. MyQuery 3.3.0 had issues on platforms where the runtime library I used wasn't installed. Also, there was a minor (but crashing) bug that caused Ndb Monitor to fail. All this, and a few other minor things, are fixed now.

I will eventually blog a bit more on the new features in MyQuery 3.3, such as the plugins, the InnoDB Lock monitor and how to easily define your own monitor dialogs with a simple SELECT statement.

Til then, download MyQuery 3.3 from Sourceforge.

Cheers
/Karlsson
And by the way, I'm sorry that I failed some QA with version 3.3.0, but it's just me coding away here, and I have a limited amount of machines and above all, time.

I may no longer be in charge of MySQL Certification but it does not mean I am not looking out for those of us with those certs.  I am still moderating the MySQL Certified Professionals Group on LinkedIn and running the North Texas MySQL USers Group.  But I missed Oracle University re-branding the Sun certifications as Oracle certifications earlier this month.  This includes  the MySQL certifications that were re-branded as Sun. 

And for those wanting to take the certification exams, they retain the Prometric numbers set up by Sun.  But you will find them listed as:

310-810 - Oracle Certified MySQL 5.0 Database Administrator Part 1 
310-811 - Oracle Certified MySQL 5.0 Database Administrator Part 2 
310-812 - Oracle Certified MySQL 5.0 Developer Part 1

This is more of a question than me sharing knowledge, but I'm testing the effects of MySQL SSL on replication delay. Interestingly, my tests show faster replication when I enable SSL, versus disable. The slave_compressed_protocol has an effect too, and I get the best result when I use SSL and slave compression in a non-CPU bound test.

The question came up, however, of what SSL Cipher I'm using. I'm not specifying one in my CHANGE MASTER statement, so I'm guessing I'm getting the same default cipher as if I connect with the regular mysql command line client with SSL, which is:

read more