Most of you are all aware of the lack of microsecond support in MySQL.
This has been a long-standing issue:
*cringe* .. sorry, just my normal reaction after seeing that bug, err feature request, again and again over the past 6+ years ..
However, I think many people do not realize that microseconds are supported by MariaDB in version 5.3+, which for all intensive purposes is a drop-in replacement for MySQL.
So if you need microsecond support for MySQL, you should definitely check out MariaDB.
“In MariaDB 5.3, the TIME, DATETIME, and TIMESTAMP types, along with the temporal functions, CAST and dynamic columns, now support microseconds. The datetime precision of a column can be specified when creating the table with CREATE TABLE”
“Generally, the precision can be specified for any TIME, DATETIME, or TIMESTAMP column, in parentheses, after the type name. The datetime precision specifies number of digits after the decimal dot and can be any integer number from 0 to 6. If no precision is specified it is assumed to be 0, for backward compatibility reasons.”
I like the “backward compatibility” too.
I won’t fully copy/paste their manual page on this, but if interested, you can read more about it here:
And for those not too familiar with MariaDB, or unsure if you should use it in place of MySQL, please check out this page:
The above discusses how MariaDB is a drop-in replacement for MySQL, but also covers any/all known user level incompatibilities that one should be aware of (note it’s a short list).
Tags: askmonty, chris calender, mariadb, mariadb and mysql compatibility, mariadb compatibility, mariadb microsecond, mariadb microsecond support, Microseconds, MySQL, mysql microsecond, mysql microsecond support, skysql