If interested in contributing code to MySQL, you should attend the MySQL University session on contributing code to MySQL.

(Live broadcast with Q&A will be held on Thursday, June 25, 2009. You can still have access to rebroadcasts afterwards.)

If interested in contributing code to MySQL, you should attend the MySQL University session on contributing code to MySQL.

(Live broadcast with Q&A will be held on Thursday, June 25, 2009. You can still have access to rebroadcasts afterwards.)

When you write your create table statements, always make sure that you make them non-ambiguous. That way even though other servers might have different configurations, you make sure your table will be created in the same way.
Imagine for instance you are developing an application on a development server, nicely storing all the scripts you need to create the same database on your production server. If the same script creates a table differently on both servers, that might cause you a lot of headache later on. At Open Query, we strive to minimise (or preferrably eliminate) headaches.

One of the parts of the create table statement that has the largest impact is the storage engine specification. When you omit the storage engine from the create table statement, your table is automatically created with the default storage engine type configured for the server. Since the storage engine is a very important choice when designing your tables, …

A couple of weeks ago, Baron Schwartz wrote an interesting post describing a rule of thumb he sometimes uses to choose the order of columns in an index. In a nutshell, he recommends putting highly selective columns first. This is a very good rule of thumb.

I would like to add another rule of thumb: columns that are used for equality comparisons are better than columns that are used for range queries.

If one has a query “select count(*) from foo where a BETWEEN 10 and 20 and b=5”, an index of (b,a) will always be as good, and likely better, than an index of (a,b), regardless of the selectivity of “a” or “b”.

This is because of how MySQL performs range queries. For an index of (a,b), a range query will be done from (10,5) to (20,5). This will require many rows to be processed where …

After four years, this blog has a new home. We've just upgraded www.opensourcestrategies.com to use WordPress. We hope you'll continue to follow opentaps Open Source ERP + CRM and our life as an open source software company there.

This Thursday (June 25th, 13:00 UTC), Lenz Grimmer will explain how to contribute code to MySQL, in a MySQL University session titled MySQL Code Contributions. Lenz is a member of the MySQL Community Team. His session will give an overview about how code contributions to MySQL should be handled and performed. It will cover the ideal workflow, requirements and available infrastructure and toolchain that potential contributors should be aware of.

For MySQL University sessions, point your browser to this page. You need a browser with a working Flash plugin. You may register for a Dimdim account, but you don't have to. (Dimdim is the conferencing system we're using for MySQL …

Dear users,

Devart Development Team has released today a new build 3.50.305 of dbForge Studio for MySQL, which includes the following bug fixes:

• Problem with obtaining the SQL code for procedures was fixed (42100)
• The bug with application hang on while parsing some view texts was fixed (41333)
• The “Stop” button that stops query executing is working correctly now (41292)
• The bug with removing of a procedure during its renaming was fixed (41284)
• IndexOutOfRangeException on working with identifier’s aliases in SELECT statements was fixed (41712)
• IndexOutOfRangeException during tables editing was fixed (41716)
• The problem with incorrect detection of relations between tables in Database Diagram was fixed (41799)
• NullReferenceException on closing an …

I came across a situation recently where I was asked if it was possible to edit a binary log to remove a part of it to restore onto a slave server. Now the choice of doing something like a hexedit did not seem appealing, and the more experienced might suggest that it is simply a matter of using  mysqlbinlog with the --start-position and/or --stop-position options. However, the problem had arisen that required the binary log to played through the replication process onto the slave based on specific options in MySQL cluster, so using an SQL dump from the binary log was of no use.

Initially this may seem like a daunting task where you will have to find some specialist tool or delve into the deep recesses of the binary log format, but a much simpler solution was found. The replication process allows the slave to be started up to a specific point in the log files. The command is the START SLAVE UNTIL... statement as seen in the manual at: …

An incident has occurred with on Gandi SiteMaker platform which has rendered your websites offline. We will keep you informed of the situation as soon as the problem has been identified. Please accept our apologies for any problem this may have caused.

10:38 => incident fixed.
11:00 => Following the network outage and subsequent impact on the SiteMaker service, we need to perform some emergency maintenance to bring the file system back up. It should take about an hour, in the meantime, there will be a maintenance page showing.
13:00 => Maintenance done

We’re sponsoring an important webinar series along with Sun/MySQL starting this week on June 25th – The Kimball Group Data Warehousing Educational Webinar Series.  This webinar series will introduce the audience to data warehousing concepts and best practices, and will cover the history and evolution of data warehousing, provide an overview of dimensional modeling, and review the full life cycle of designing and implementing a data warehouse.  Part 1, on June 25th at 1:00P PDT, is on Data Warehousing Fundamentals.

There are two key reasons why we think this webinar series is important:

• First, we believe this webinar further advances data warehousing in the MySQL world. There is a whole new generation of database developers in the MySQL community that are at various stages of understanding data warehousing – …