Connectors now available to the MySQL® community as part of the MariaDB open source project

Helsinki – November 29, 2012 – Monty Program, the home of MariaDB, owned by MySQL®-database-creator Monty Widenius and its employees, and SkySQL, the trusted provider of open source database solutions, today announced the immediate availability of their connectors, ‘MariaDB Client Library for C and MariaDB Client Library for Java Applications’, to the wider MySQL® database community in the permissive LGPL licence.

With this announcement, the connectors become part of the wider MariaDB open source project, to which users will be able to contribute via relevant online resources.

Good news for open source developers

This announcement is relevant for users involved with applications built in C or Java language that also make use of a MariaDB and/or MySQL database, as these require a connector to ensure that the applications & the databases can talk to each other.

News Highlights

As part of their ongoing efforts to contribute innovation and technology to the wider MySQL database and open source user communities, Monty Program & SkySQL  today announced the availability of the MariaDB Client Library for C and MariaDB Client Library for Java Applications.

Up until recently, the two companies had been working on the connectors as a joint internal project used for specific customer requirements and they are now making their connectors generally available to the community as part of the MariaDB open source project.

Connectors enable users to connect from a given application to a database, in this case the MySQL & MariaDB databases. Commercial maintenance & support for the servers and connectors will be available via SkySQL’s Enterprise Data Suite.

Download links & additional resources

Supporting quotes:

“These connectors have been an internal SkySQL/Monty Program project long enough and it was time to make them available to the wider MySQL user community,” said Monty Widenius, CEO of Monty Program. “The connectors will add value to the MariaDB project by making our database technology and the MariaDB project itself easier for everyone to use. If anything, we’re opening the MariaDB project even further to the community and demonstrating that innovation happens with MariaDB.”

 “We’ve been seeing a strong demand for connectors from the MySQL database ecosystem. We are looking for means to ensure that the ecosystem prospers and that both users and developers have a rich set of options. We believe that these connectors will help to stimulate innovation in the ecosystem,” added Patrik Sallner, CEO of SkySQL. “Helping organisations out there adopt the MySQL and MariaDB databases more easily for their software projects also reinforces our position as the one-stop shop for all things to do with the MySQL and MariaDB databases.”

About SkySQL

SkySQL is the trusted provider of open source database solutions for MySQL and MariaDB users – in the enterprise and cloud, providing over 300 enterprise customers including Canal+, ClubMed, Constant Contact, Deutsche Telekom, La Poste, Virgin Mobile, Western Digital and XING with database deployment and management solutions.

With 250+ years of original MySQL experience, SkySQL has the leading MySQL talent pool with sponsorship by the original MySQL and MariaDB creators. It has also developed cloud-based database management solutions that bring ease of use, while providing an effective way to increase database productivity both in the enterprise and the cloud.

For more information, please visit www.skysql.com, and follow the company’s conversations on Twitter and Facebook.

About Monty Program

Monty Program Ab was founded by Michael “Monty” Widenius, the founder and creator of MySQL®. Monty Program is a center of engineering excellence for MariaDB, the Aria storage engine, MySQL®, and other associated technologies.

More than half of our staff are full-time developers, including most of the original MySQL engineers, some new personnel, and Monty. We have a better knowledge of the core MySQL® code than any other company! We are well funded and all of our plans and strategies take a long-term view.

For more information, visit: http://montyprogram.com

 

 

MySQL is a registered trademark of Oracle and/or its affiliates.

MariaDB is a registered trademark of Monty Program Ab.

SkySQL and the SkySQL logo are trademarks of SkySQL Inc. or SkySQL Ab. Neither SkySQL nor Monty Program is affiliated with MySQL or Oracle. All other company and product names may be trademarks or service marks of their respective owners.

In June, I told about the consolidation of the MariaDB project tools. The final piece of this consolidation, to report bugs in the MariaDB project tracking tool called JIRA has now been finalized.

Bug reporting stays open! JIRA is open to anyone. The bug reports are publicly available, even without logging in and as a bonus it will be easier to follow what is going on in the project since you don’t have to jump between several tools to get the complete picture.

All bugs that existed in Launchpad have been migrated to JIRA. To find a bug that was originally reported on Launchpad use the following approaches:

  • If you happen to have the original bug id you can search for the bug by typing lp:bugid into the search field in the upper right corner of JIRA. Also, if you have the link to the bug report on Launchpad, you’ll be able to open that bug report and get hold of the id (which by the way also can be seen in the URL).
  • You can also search on keywords, e.g. “ALTER TABLE” or “microsecond”
  • In addition JIRA includes a nice search functionality with which more advanced searches can be done like searching for issues reported by a specific user. This search is found in the top navigation under “Issues” and is called “Search for issues”.

Getting the bugs into the project tracking tool of MariaDB can be seen as an enabler of the personal task I set for myself in my MariaDB Directions blog post last week, on creating a longer-term roadmap for MariaDB. Now with the development tasks, bug reports and planning inside the same tool, anyone can see what is going into which version of MariaDB.

Please make yourself familiar with MariaDB development by checking out JIRA and do participate in the development by:

  • Creating new issues in JIRA for features you would like to see in upcoming versions of MariaDB
  • Reporting possible bugs in MariaDB, “Create Issue” in JIRA
  • Commenting and adding more information to existing issues in JIRA

You’ll have to create an account for yourself to do that, which is very straight forward. Just click on the Sign Up –link in conjunction with the Login and follow the instructions.

If you did report MariaDB bugs on Launchpad before you’re also seen as the reporter of the bug in JIRA and an account has automatically been created for you in JIRA. However this account doesn’t hold your email address, since it was not (easily at least) possible to export that from Launchpad (probably because of privacy reasons). We are glad to activate your automatically created account in JIRA. Todo so please send us your name and email address through the Monty Program contact form.

 

Infor announced this week, that they will provide open source database alternatives to some of their products. MariaDB has been chosen, tested, and certified by Infor to be the open source database of choice (together with MySQL) for the Infor LN and ION products. Infor LN is Infor’s flagship ERP and is sometimes better known by its former name, Baan. It has 25 years of manufacturing know-how built into it and is used by more than 5,000 companies worldwide in a wide range of industries. These include automotive, industrial equipment and machinery, high tech and electronics, and aerospace and defense. This is a big stamp of approval that even the most critical systems can be run on MariaDB.

In other news, there are currently several really interesting paths coming together into some important milestones. The rest of this post will be about them and I hope you are as excited about them as we are and please do let us know what you think, as always.

MariaDB 10.0

First up, MariaDB 10.0. In my late spring blog post about the next version of MariaDB, we informed you that the next version will be called MariaDB 10.0. There was a little storm of feedback on this and most of the feedback was related to how different tools will react with this versioning change. We’re still looking into this, but it’s good to remember that MariaDB includes features and functionality that aren’t in MySQL and that it would be good for tools to handle the MariaDB version string separately to make use of the advantages of MariaDB, like extended statistics and more switches compared to MySQL. Currently we are just a few days away from releasing the Alpha version of MariaDB 10.0 and I would like to make particular mention of two features:

  • Multi-source replication, which is a longtime wish of many users. In scenarios where you partition your data over many masters you can then replicate the data from all masters onto one slave. This is very useful for analytical queries towards the whole data or for backing up all data.
  • Get the query plan of a running statement (SHOW EXPLAIN). In MySQL and MariaDB up until now a query plan printout (EXPLAIN) wasn’t always correct because the actual running query wasn’t studied, which is the case now with SHOW EXPLAIN.

To get more details on what MariaDB 10.0 includes, please read Monty’s blog post. The Alpha version of MariaDB 10.0 is about to be released. Stay tuned!

Cassandra, JSON and Dynamic Columns

For those of you keeping score, one and a half years ago Dynamic Columns was introduced into MariaDB. This feature allows you to store a different set of columns for every row in a table. In that manner Dynamic Columns can be called NoSQL-like.

Whether or not the first intention of introducing Dynamic Columns was to become the foundation for data interchange, it definitely has. Since we introduced Dynamic Columns we have received user input, and have researched how to make it better and the end result is that Dynamic Columns now has some new capabilities:

  • Database interoperability: It’s pretty rare that companies use only a single type of databases and even critical business systems are often built on several different types of databases. Usually the data residing in those different databases are combined in an upper application level. MariaDB introduces the possibility to do this at a low level inside the MariaDB database. The first implementation of this is integration with Cassandra. Yes, you can now combine data residing in Cassandra with data inside MariaDB and all this is done through normal looking queries on the MariaDB side.
  • Data interchange: JSON has become a very popular standard for data interchange. In Dynamic Columns one can now request a row in JSON format.

The feature preview release of the Dynamic Columns with the above features included will be made available today and all of this will naturally become part of MariaDB 10.0, currently scheduled for the version 10.0.1.

MariaDB Galera Cluster

Next, you may recall that at the beginning of the month we introduced MariaDB Galera Cluster. This Alpha version has been out now for about three weeks and we’ve been testing and fixing it to prepare for the next development release. To be honest, most end user problems have been related to packaging and running the product on a specific platform. The final steps of finalizing, and preparing for, the Beta version are currently being taken.

Be part of the MariaDB project

Another push we’re making at this time is to actively extend involvement in MariaDB. Every new installation of MariaDB of course counts to this, but what I’m actually referring to is that we want to involve more companies and individuals in the MariaDB project. This doesn’t necessarily mean digging into the MariaDB source code. That is always welcome, of course. But another very important way to help the project is to sponsor specific work in MariaDB or make general financial contributions.

Patrik Sallner, CEO of SkySQL, said yesterday in his blog post about the launch of their new SkySQL products and offerings for MariaDB and MySQL, that there are a lot of businesses out there having really critical workloads running on MySQL and MariaDB. If you happen to represent one of these businesses, please consider the possibility of being part of planning the future of the product your critical business is run on. Please contact me through Monty Program for further information.

A personal task and wish

Lastly, we try to be as open as possible inside the MariaDB team in regards to the MariaDB project and I think we have succeeded fairly well. We are definitely continuing on that path. However there are always things we can do to improve, and one of them that I personally think is important for both MySQL and MariaDB is evolution predictability. Users want to know in which direction the product is going and to have a roadmap that clearly tells what’s going to be in the next version and what is planned for future versions after that. I will work on the MariaDB side to create a longer-term roadmap with as many details as possible and I do hope we’ll see something similar from the Oracle MySQL team.