The freshly released MySQL 8.0 includes a data dictionary, which makes MySQL much more
reliable. Thanks to this features, we don't have any '.frm'
files, and querying the information_schema is 30x to 100x faster
than previous versions.

While the reason is fully understandable (they don't want to
commit on an interface that may change in the future) many
curious users are disappointed, because openness is the basis of
good understanding and feedback.

The problem to access the dictionary tables can be split in three
parts:

gh-ost now powers our production schema migrations. We
hit some serious limitations using pt-online-schema-change on our large volume,
high traffic tables, to the effect of driving our database
to a near grinding halt or even to the extent of causing outages.
With gh-ost, we are now able to migrate our
busiest tables at any time, peak hours and heavy workloads
included, without causing impact to our service.

As work on WarpSQL (Shard-Query 3) progresses, it has outgrown
MySQL proxy. MySQL proxy is a very useful tool, but it
requires LUA scripting, and it is an external daemon that needs
to be maintained. The MySQL proxy module for Shard-Query
works well, but to make WarpSQL into a real distributed
transaction coordinator, moving the proxy logic inside of the
server makes more sense.

The main benefit of MySQL proxy is that it allows a script to
“inject” queries between the client and server, intercepting the
results and possibly sending back new results to the client.
I would like similar functionality, but inside of
the server.

For example, I would like to implement new SHOW commands, and
these commands do not need to be implemented as actual MySQL SHOW
commands under the covers.

For example, for this blog post I made a new example command
called “SHOW PASSWORD”

This is not a comprehensive review, nor an user guide. It's a
step-by-step account of my initial impressions while trying the
new MySQL XProtocol and the document store capabilities. In fact,
I am barely scratching the surface here: more articles will come
as time allows.

MySQL 5.7 has been GA for several months, as it was released in
October 2015. Among the many features and improvements, I was
surprised to see the MySQL team emphasizing the JSON data type. While it is an interesting feature
per se, I failed to see the reason why so many articles and
conference talks were focused around this single feature.
Everything became clear when, with the release of MySQL 5.7.12,
the MySQL team announced a new release model.

And for the fourth year in a row, MariaDB Foundation participates
in the Google Summer of Code! The MariaDB Organization in GSoC is
an umbrella organization for all projects that belongs to the
MariaDB ecosystem, be it MariaDB Server, MariaDB Connectors, or
MariaDB MaxScale. The complete list of our suggested project
ideas is in MariaDB […]

MariaDB 10.1 introduced Data at Rest Encryption. By default we
provide a file_key_management plugin. This is a basic plugin
storing keys in a file that can be itself encrypted. This file
can come from a usb stick removed once keys have been brought
into memory. But this remains a basic solution not suitable for
security [...]

The MySQL Workbench tool is great for development and
administration tasks. Also it's available on Windows, Linux and
Mac OS X which, according to information from third party
sources, is more than you can say for most of the other
equivalent tools. And Workbench is free. Having said that, most
of the provided functionalities are intuitive and of daily use
for developer and DBA staff alike.

If you are in Helsinki on Thursday next week March 17th, join us
for the MariaDB meetup at Solinor. MariaDB team members will
present the latest on MariaDB 10.1, MaxScale and MariaDB’s future
roadmap. On stage Rasmus Johansson VP Engineering, MariaDB
Corporation and Johan Wikman & Markus Mäkelä, developers of
MaxScale. See the meetup page […]

A couple of weeks ago we announced that we were moving from a
hosted instance of JIRA to our self hosted instance. The main
reason was that we hit 2000 active users in the hosted instance
of JIRA and that is the upper limit that it supports. We
obviously wanted to allow more people to […]

New SSL alternatives SSL connections in previous versions of
MariaDB Connector/C based on the OpenSSL library. The OpenSSL
heartbleed bug, licensing problems and the lack of supporting
different transport layers were the main reasons that we decided
to offer SSL alternatives. In addition to OpenSSL the following
SSL libraries are supported in Connector/C 3.0: GnuTLS […]

Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.