Applications should be written taking into account that errors will eventually happen and, in particular, database application developers usually consider this while writing their applications.

Although the concepts required to write such applications are commonly taught in database courses and to some extent are widely spread, building a reliable and fault-tolerant database application is still not an easy task and hides some pitfalls that we intend to highlight in this post with a set of suggestions or tips.

In what follows, we consider that the execution flow in a database application is characterized by two distinct phases: connection and business logic. In the connection phase, the application connects to a database, sets up the environment and passes the control to the business logic phases. In this phase, it gets inputs from a source, which may be an operator, another application or a component within the same …

In this post, we are going to show how to develop fault-tolerant applications using MySQL Fabric, or simply Fabric, which is an approach to building high availability sharding solutions for MySQL and that has recently become available for download as a labs release (http://labs.mysql.com/). We are going to focus on Fabric's high availability aspects but to find out more on sharding readers may check out the following blog post:

•  http://vnwrites.blogspot.com/2013/09/mysqlfabric-sharding-introduction.html

Servers managed by Fabric are registered in a MySQL Server instance, called backing store, and are …

Connector/Python v1.1.1 is available for testing. It’s the second of a series of alpha releases which will bring some new features. Check out the Change History if you want to keep up with what is being added and changed.

Notable changes for v1.1.1:

• Connection Pooling is now available
• A backend for Django is now (again) provided with Connector/Python.

Connector/Python v1.1.1 is alpha and although in good shape, it’s advised not to use it in production just yet.

Some …

A few weeks ago we released MySQL Connector/Python v1.0.12. Bugs were fixed, and LOAD DATA LOCAL INFILE should now work correctly. The announcement can be read on the MySQL forums.

Some useful links:

• Documentation: http://dev.mysql.com/doc/connector-python/en/index.html
• Release Notes: http://dev.mysql.com/doc/relnotes/connector-python/en/index.html
• Downloads: …

ConFoo is currently looking for web professionals with deep understanding of PHP, Java, Ruby, Python, DotNet, HTML5, Databases, Cloud Computing, Security and Mobile development to share their skills and experience at the next ConFoo. Submit your proposals between August 26th and September 22nd.

ConFoo is a conference for developers that has built a reputation as a prime destination for exploring new technologies, diving deeper into familiar topics, and experiencing the best of community and culture.

• ConFoo 2014 will be hosted on February 26-28 in Montreal, at the Hilton Bonaventure Hotel.
• We take good care of our speakers by covering most expenses including travel, accommodation, lunch, full conference ticket, etc.
• Presentations are 35min + 10min for questions, …

The MySQL Utilities Team is pleased to announce the latest GA release of
MySQL Utilities. This release marks a milestone of concentrated effort to
expand the use of utilities in more diverse installations through improved
robustness, error handling, and quality.

Many Improvements
There are number such enhancements in this release. In this post we will
highlight a few of the more significant improvements.

• (new utility) MySQL .frm Reader (mysqlfrm) - read .frm files and generate CREATE statements with or without a server connection.
• (revised) improved documentation including a section on example administrative tasks - see http://dev.mysql.com/doc/workbench/en/mysql-utilities.html
• MySQL Utilities is packaged for .msi, .rpl, .deb platforms and source .tar/.zip
…

I’ve create and another module for this besides the mysql_replication, named mysql_variables.

The purpose of this module to get/set variables from running MySQL servers, and avoid to use shell module for this, because that is a bit frustrating, and there are long commands to run.

For example, when you wanna to set read_only mode via shell, you can do that like this:

ansible db-secondary.bfc.kinja-ops.com -m shell -a "mysql -e 'select @@read_only'"
db-secondary.bfc.kinja-ops.com | success | rc=0 >>

[root@admin banyek]# ansible db-secondary.bfc.kinja-ops.com -m shell -a "mysql -e 'set global read_only=1'"
db-secondary.bfc.kinja-ops.com | success | rc=0 >>

Not so neat, isn’t it, eh? And I have not speak about the —user and —password variables, to this could be real annoying.

That’s why I made this module, because it is a bit easier to use (and I like to use own toolset with the …

Issue – the OpenStack instances hostnames are not resolved at the moment by their floating IPs.

Fast solution – use PowerDNS
Short story:
1. Boot an instance , assign it a floating IP, open tcp ports 22 8001 and udp port 53.
2. Install PowerDNS, the particular yum package is named pdns.
3. install the mysql backend for PowerDNS, its available as yum package as well.
4. Install MariaDB , set the proper configuration, the initialize it at the default location.
5. Set the pdns user, create the pdns database and create the tables needed.
6. Configure the pdns service to use the gmysql backend.
7. Create and user at the OpenStack MySQL able to connect from the floating IP subnet.
8. Grant that user select permissions on all nova.* tables.
9. At the PowerDNS instance, set simple python / php / bash script to query the nova database and to inject the hostnames and the …

What programming languages and platforms do you use for large-scale projects in your organization?

If something is missing from the list please leave a comment and share your story. Thanks!

Note: There is a poll embedded within this post, please visit the site to participate in this post's poll.

The post Poll: What programming languages and platforms do you use? appeared first on MySQL Performance Blog.

Finally, Connector/Python v1.1.0 is out. It’s the first of a series of alpha releases which will bring some new features. Check out the Change History if you want to keep up with what is being added and changed.

Notable changes for v1.1.0:

• Connector/Python v1.0 was known to work with Python v2.4 and 2.5. We now break compatibility with these older Python versions.
• MySQL Prepared Statements are supported using cursor.MySQLCursorPrepared.
• You can find out whether there is an ongoing transaction by checking MySQLConnection object’s property in_transaction. …