MariaDB 5.3 and up and MySQL 5.6 RC introduced real support for milliseconds:
https://kb.askmonty.org/en/microseconds-in-mariadb/
http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html

HeidiSQL now lets you define a LENGTH/SET value for data types which allow a microsecond precision (0-6, where 0 is the default). Also, when editing such TIME, TIMESTAMP or DATETIME values in a grid, HeidiSQL lets you press arrow up/down to increase/decrease the microseconds part of the underlying value. Thanks to rjgebis for the report and documentation links.

Brian Aker and I have been working hard in the last few weeks to give you a great Christmas present, Libdrizzle 5.1.0.  The MySQL compatible, BSD licensed C connector (so static compiling with commercial software gets the thumbs up!).

The latest changes include:

• A server-side prepared statement API
• Improved binary log API
• An example binary log remote retrieval utility using the binlog API called "drizzle_binlogs"
• A new build system, DDM4 which is used by Gearman and Memcached
• Many bugs fixes

The source and manuals can be found on the Launchpad downloads page.  Please enjoy, feel free to file bugs, questions and hack on code on our Launchpad …

Every time a view is accessed in MySQL, the view definition has to be read from the .FRM file on disk. This was resulting in a huge performance bottleneck. That is why we decided to introduce “View Definition Cache” in MySQL 5.6. Caching the view definitions turns out to work even better than hoped.

With the introduction of “View Definition Caching”, the view definition is read from the .FRM file on the first access of the view and cached. Subsequent view accesses gets the view definition from cache instead of reading it again from the .FRM file, until the view is removed from the cache. The view elements from the cache are removed on LRU basis when the cache is full or when DDL operations(as ALTER, DROP) are performed on the view. The size of the cache can be configured by the system variable “table_definition_cache”(Default Value= 128).

The following experiment shows the improvement in performance with the view …

I was just bitten by failing to catch a MySQL warning. It’s the old familiar tune: I inserted 100 characters into a VARCHAR(50) and it didn’t throw an error*. Of course, then subsequent SELECT statements didn’t find the value I inserted.

What’s different this time is that I was using Go as the client. There is no single official MySQL driver for Go, although there are several good-quality community-maintained ones. I was using one of those through the official Go database interface, which is a simple and lightweight way to interact with relational databases. This interface will generate errors, but I didn’t think about warnings. This is funny, because usually I’m paranoid about capturing warnings from MySQL and treating them as errors.

After I discovered my mistake, I realized that Go’s database interface doesn’t provide a way to observe the warnings …

I was just bitten by failing to catch a MySQL warning. It’s the old familiar tune: I inserted 100 characters into a VARCHAR(50) and it didn’t throw an error*. Of course, then subsequent SELECT statements didn’t find the value I inserted. What’s different this time is that I was using Go as the client. There is no single official MySQL driver for Go, although there are several good-quality community-maintained ones. I was using one of those through the official Go database interface, which is a simple and lightweight way to interact with relational databases.

(from Monty himself….apparently my captcha is broken, I am working on fixing that now).

Thanks for writing a post about this topic! There seems to be some misconceptions about the ODBA and the MariaDB foundation and it’s good to get them clarified!

Sorry for not answering this at once, I didn’t get to know about your post until today.

First a small mistakes in your original post:
Neither Monty Program or SkySQL are currently members of the foundation.

Then to your questions:

There is a big difference between the ODBA and MariaDB Foundation.

First some background of the two efforts.

ODBA
—-

ODAB was intended to be for all open source databases, helping them to better compete with closed source databases.

The problem with the ODBA was that no one of the founding members had time to drive it. The plan was from the beginning to find a person to …

A few months ago, in MySQL 5.6.4, I took a brief look at MySQL 5.6's new InnoDB Fulltext support; see Initial impressions of InnoDB Fulltext. There have been quite a few new point releases since then, and we're into RC releases of MySQL 5.6 now, so I thought I'd take another look.

read more

Even if you are using a GUI tool to connect to your MySQL servers, one day or another, you will have to deal with the command line. So it is nice to know a few tips that can really make your work easier.

Note: The commands below are only available for Unix/Linux.

Using pager

Most of the graphical tools paginate results, which is very handy. But this is not the way the command line client works: it just outputs all results. It can be annoying but it is easily solved by using the pager command:

mysql> pager more
PAGER set to 'more'
mysql> select title from sakila.film;
+-----------------------------+
| title                       |
+-----------------------------+
| ACADEMY DINOSAUR            |
| ACE GOLDFINGER              |
| ADAPTATION HOLES            |
| AFFAIR PREJUDICE            |
| AFRICAN EGG                 |
| AGENT TRUMAN                |
| AIRPLANE SIERRA             |
| AIRPORT POLLOCK …

Galera from codership has been getting a lot of attention recently. Galera provides a nice High Availability solution for MySQL where Galera provides synchronous replication with conflict detection using the classic InnoDB Storage Engine. No more playing about with special storage engines of DRBD failover, just continue to use InnoDB and add Galera as the secret sauce for High Availability.

Some of the neat features of Galera are, but are not limited to, multi-master replication, a lightweight implementation of replication and zero failover times due to the multi.master ability. This is not a complete HA solution though, just a component of it, we still need to add some monitoring and failover mechanisms, but as Galera is multi-master this is greatly simplified and can in many cases be handled by the driver or the application with little overhead.

Now, the replication in Galera is synchronous, so that should slow …

It's the end of the year and, before the world ends ;-) , I feel the pressure to follow up on last year's article "2011, a great year for MySQL in Review". I'll adopt a similar format and mention things in context, covering products, marketing, momentum, etc. at a high level. I may have missed something and I hope my colleagues will contribute to the list.

I really do think it's been the best year for MySQL so far... well, at least since when I signed my contract with MySQL AB at the end of 2007. We're just at the beginning of our journey and I wish to the MySQL family, to our community and ecosystem an even better 2013!

Summary
…