Can we output content of a mariaDB table into JSON using the CONNECT Storage Engine ? MariaDB and MySQL are not currently JSON friendly databases. The usage of JSON in MySQL is almost inexistent with the excetion of the explain JSON output and of MariaDB dynamic column dump. There also exist a few udf (in [...]
In the MySQL team, we have always had a requirement to support upgrades from one major version. For example:
- Upgrading from MySQL 5.5 to 5.6 is supported.
- Upgrading from MySQL 5.1 to 5.6 is not supported.
Downgrades are also supported for one major version. For example, if a user upgrades to 5.6 but discovers that it is not working as expected, they have the safety knowing that there is a way to step back to MySQL 5.5. This may come with some limits; for example when new features (such as new row formats or page checksums) are enabled, this may no longer be possible.
Today I wanted to discuss a current non-requirement. We do not support skipping major versions, such as upgrading from MySQL 5.1 to 5.6. Justin however makes the …[Read more]
In the MySQL team, we are planning to remove sql-bench from the MySQL 5.7 sources.
As the README file denotes, SQL Bench is a benchmark utility that supports MySQL 3.20 and 3.21, PostgreSQL 6.#, mSQL 2.# and Solid Server 2.2. It has not been well maintained for recent versions, and we are no longer using it internally as part of our testing process.
Our aim in making this change is to:
- Improve the manageability of our git repository by reducing its size.
- By keeping unmaintained code bundled with MySQL, it can lead users into negative impressions of our product. We have worked very hard at improving stability, and want to remove lurking pitfalls for our users.
The source code to sql-bench will remain in the …[Read more]
In the MySQL team, we are currently discussing deprecating several of the SQL mode options which are used by mysqldump to change the output format. From the mysqldump command:
$ mysqldump --help .. --compatible=name Change the dump to be compatible with a given mode. By default tables are dumped in a format optimized for MySQL. Legal modes are: ansi, mysql323, mysql40, postgresql, oracle, mssql, db2, maxdb, no_key_options, no_table_options, no_field_options. One can use several modes separated by commas. Note: Requires MySQL server version 4.1.0 or higher. This option is ignored with earlier server versions.
To explain the rationale for this proposal:
- The options mysql323, mysql40 are designed to allow mysqldump to create an output format that can be restored on a MySQL Server of version 3.23 or 4.0. While we aim to support the upgrade case from these versions, supporting a downgrade is not something we …
The 2015 MySQL Community Awards event will take place, as usual, in Santa Clara, during the Percona Live MySQL Conference & Expo, April 2015.
The MySQL Community Awards is a community based initiative. The idea is to publicly recognize contributors to the MySQL ecosystem. The entire process of discussing, voting and awarding is controlled by an independent group of community members, typically based of past winners or their representatives, as well as known contributors.
It is a self-appointed, self-declared, self-making-up-the-rules-as-it-goes committee. It is also very aware of the importance of the community; a no-nonsense, non-political, adhering to tradition, self criticizing committee.
The Call for Nominations is open. We are seeking the community’s assistance in nominating candidates in the following categories:
MySQL Community Awards: Community Contributor of the …[Read more]
Good bye bzr, welcome git!
After latest releases we moved development of MariaDB Connectors for C, ODBC and Java from launchpad to github.
The connector repositories can be found under https://github.com/MariaDB
Feel free to watch, fork and contribute!
Following on from my earlier proposal to change Replication + InnoDB settings, in the MySQL team, we are proposing to make the following additional changes to defaults in MySQL 5.7:
|Setting||Old Default||New Default|
In the MySQL Team, we are currently evaluating potential changes to the default server configuration for MySQL 5.7. For more context, please see my earlier post here.
One of the specific changes we would like to make is with the following three related replication and InnoDB settings:
|Setting||Old Default||New Default|
In MySQL 5.6, one of the most well received changes was improving the default configuration to be safer, and easier to use.
We are seeking community feedback for improvements that can be made to the default configuration in MySQL 5.7. Please leave a comment, or get in touch with me via email.
For elimination of confusion, please state both the setting you would like changed, and the new desired value.