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 – …

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: …

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: …

With all the changes between MySQL and Meetup Corporation, our Los Angeles MySQL Meetup has been in flux. But I’m happy to note that Navicat was kind enough to sponsor us for now & if that ever falls through, OpenQuery … Continue reading →

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 - what it …

Just the fact that a system can scale to a large number of nodes does not mean it is worth using.
Imagine a fictitious data system that scaled to 1 million nodes but could only process 100 bytes per second on each node.
This would be the worlds biggest energy wasting phenomenon, due to the electricity and cooling requirements for such a cluster. [arguably you could think of something else that wastes more energy than this :) ]
When supporters of a system start talking about how many nodes their system can scale to, don't forget to ask for an analysis of the efficiency of each of these nodes.
More later .... Ivan