Both MySQL Connector/Python 2.0.1 and 1.2.3 are now available through the Python Package Index or PyPI. Leaving the previous version available is probably a good idea as you can always go back if needed.

Note that we still have no files hosted at PyPI.

Both MySQL Connector/Python 2.0.1 and 1.2.3 are now available through the Python Package Index or PyPI. Leaving the previous version available is probably a good idea as you can always go back if needed.

Note that we still have no files hosted at PyPI.

Tue, 2014-09-30 08:55patriksallner

As we start the beginning of our FY15, I want to thank all our customers, partners, staff, and community members for their contributions this past year. I'm proud of what we collectively achieved even as we drove significant changes in our business and organization. It's energizing to feel the momentum and enthusiasm building around MariaDB.

So, as my first act for FY15, I am excited to announce that today SkySQL will change its name to MariaDB Corporation. This name change will more closely associate the MariaDB open-source database with the company behind it. You may have already noticed that we moved our corporate website from skysql.com to mariadb.com.

As the adoption of MariaDB grows within the MySQL community, so does its acceptance in the enterprise space. Having started as an exciting open source project, MariaDB has since been embraced by millions of enthusiastic developers and …

Friend and former colleague Roland Bouwman has written an excellent update on the GROUP BY implementation in MySQL.

MySQL’s implementation of GROUP BY has historically been quirky. Sometimes that quirkiness has been useful, but often it causes grief as SQL authors can make mistakes that are executed but don’t produce the results they want (or expect).

Simple example:

SELECT cat, COUNT(val) as cnt, othercol FROM tbl GROUP BY cat

The ‘cat‘ column is in the GROUP BY clause, the COUNT(val) is an aggregate, but the ‘othercol‘ column is … well… neither. What used to effectively happen is that the server would pick one othercol value from within each group. As I noted before, sometimes useful but often a pest as the server wouldn’t know if …

In a previous blog post we presented some of the issues with the current optimizer cost model and listed several ideas for improvements. The new 5.7.5 DMR contains the result of our initial work on improving the optimizer’s cost model:

• Cost Model for WHERE Conditions. In previous versions of MySQL, the estimated number of rows from a table that will be joined with the next table only takes into account the conditions used by the access method. This often led to record estimates that were far too high and thus to a very wrong cost estimate for the join. With wrong cost estimates, the join optimizer might not find and choose the best join order. To solve this issue, a cost model that includes the …

As documented in the Reference Manual MySQL supports a maximum of 16 columns per index. That's more than sufficient for most index use cases, but what about unique constraints? If I create a fact table with more than 16 dimension columns in my star schema, and then try to add an index to enforce a unique constraint across all of the dimension columns, then I'll get this error:

ERROR 1070 (42000): Too many key parts specified; max 16 parts allowed

For multi-column unique indexes, internally MySQL concatenates all of the column values together in a single hyphen-delimited string for comparison. Thus I can simulate a multi-column unique index by adding an extra column that stores the concatenated column values, and adding a unique index on that column.

Read on for details...

I could populate the new column …

Indeed, MySQL 5.7 rocks ;-)

This is the part1 of the following blog posts about various benchmark results on MySQL 5.7 - and this particular one is dedicated to the Sysbench OLTP_RO Point-Select 8-tables workload.

We've already published the over 500K QPS on SQL Point-Selects before @32cores-HT server, so may reconfirm it again with MySQL 5.7 DMR5 -vs- other engines :


and now on a similar server, but with 40cores-HT we're able to confirm 645 QPS on the same workload!

If you missed the long story about how we arrived on such a performance level and how to reproduce the test - you may find all here. This workload is the most killing from all Read-Only Sysbench OLTP tests.. And it's really for the first time we started to scale here with MySQL! …

In this third installment in this series, I'll explain why the smart solution I described in the previous post actually wasn't that good, and then I go on to explain how to fix it, and why that fix wasn't such a smart thing after all. So, this was the design we ended with last time:
We have Oracle replicating to a Materialized View, this to ensure that we can run triggers when the is a commit, and then triggers on this Materialized View updates MariaDB by sending a UDP message to a server that in turn is connected to MariaDB.

The issue with the above thingy was that a Materialized View by default is refreshed in it's entirety when there is a refresh, so if the table has 10.000 rows and 1 …

Business Wire  Oracle Open World 2014, Booth # 430- Continuent, Inc., a leading provider of open source database clustering and replication solutions, today announced Continuent Tungsten 3.0, a powerful solution that combines advanced clustering and replication technologies to meet the transaction processing and analytic needs of the entire business. Continuent Tungsten 3.0 enables constant,

MySQL Fabric 1.5.2 is out. In this release, you will find fixes for some bugs and, specially, new exciting features:

New interface using the MySQL Protocol

Now MySQL Fabric mimics to some extent a MySQL Server. This will foster the MySQL Fabric adoption by other connectors as they will not have to use a XML-RPC protocol.

import mysql.connector

cnx = mysql.connector.connect(host='localhost', port=32275, user='admin', password='adminpasswd')

cur = cnx.cursor()

cur.execute("CALL dump.servers(patterns=%)", multi=True)
print cur.column_names
for row in cur.fetchall():
print "Row", row

Provisioning command group

We have started to make MySQL Fabric Cloud Aware and exploit the easiness to spawn new machines in a cloud environment. There is a long road ahead and this is just the beginning.

$ mysqlfabric provider register my_provider user passwd \ …