I would like to make this post to reference one of posts published on mysql.com website. A lot of mysql users visit our site and I think our users will be willing to help. Here are the full details:

Donations are requested to help Andrii Nikitin, a MySQL support engineer in Ukraine, provide for his son Ivan who requires a bone marrow transplant operation. The cost of this operation is expected to be between €150,000 - €250,000 ($235,000 - $400,000). Please help us provide Ivan a chance to live.

More information can be found here: http://www.mysql.com/about/help-ivan.html

Slave delay can be a nightmare. I battle it every day and know plenty of people who curse the serialization problem of replication. For those who are not familiar with it, replication on MySQL slaves runs commands in series – one by one, while the master may run them in parallel. This fact usually causes bottlenecks. Consider these 2 examples:

• Between 1 and 100 UPDATE queries are constantly running on the master in parallel. If the slave IO is only fast enough to handle 50 of them without lagging, as soon as 51 start running, the slaves starts to lag.
• A more common problem is when one query takes an hour to run (let's say, it's an UPDATE with a big WHERE clause that doesn't use an index). In this case, the query runs on the master for an hour, which isn't a big problem because it doesn't block other queries. However, when the query moves over to the slaves, all of them start to lag because it plugs up the single …

Some weeks ago there was a request about adding a feature that keeps (or gets) datatypes of colums, which are connected via foreign keys, in sync. While we have added this to our ToDo list, I thought of doing some simple LUA exercises to give the user at least a funtion to check if the FKs in the model all have columns with matching datatypes.
As it turned out such tasks can be done quite easily using our GRT-shell. And by writing some functions you can add features to Workbenchs interface.

To get in touch with the shell/GRT environment inside Workbench click the tiny black prompt-window-icon in the top right area of workbench (or choose ‘View->Advanced->GRT Shell’ from the main menu).  Some items in the UI are swapped/added: the sidebar on the right side gets a new tab named ‘GRT Shell’ featuring some more tool-panes (GRT Tree, Modules, Inspector) and on the bottom part of the main window - where the editors …

As you may have noticed we’re going for a major milestone on our Workbench 5.1 roadmap. So our resources are pretty much concentrated on this  task at the moment. But it’s just as important to keep improving our 5.0 GA version, so we will reserve the first days next week to make progress here as well. We will publish the next release of 5.0 mid-next-week. So stay tuned for a better 5.0 next week and the upcoming 5.1 alpha later this month.

Valleywag reports that Monty Widenius has quit Sun. The Pythian Group reckons its true. Kaj Arno’s non-denial denial would appear to confirm it despite his protestations otherwise.

“Technically there is no resignation letter. However, I spoke to Monty yesterday, and yes, resignation is an option he considers,” writes Kaj before expanding on some of the reasons that Monty might consider leaving Sun and how the MySQL project would continue without him (or without him as an employee at any rate).

He concludes: “In summary, I can neither confirm nor deny the rumour. But I hope my posting has shed some light on the …

We have a rumour of MySQL co-founder Michael “Monty” Widenius resigning, as posted by Valleywag and expanded by Sheeri Kritzer Cabral.

Usually, I wouldn’t comment on rumours. But as I’ve been asked copious amounts of questions, let me make an exception today.

First, it’s a rumour. Technically there is no resignation letter. However, I spoke to Monty yesterday, and yes, resignation is an option he considers.

Second, Monty’s resignation has been a possible outcome already since years before the Sun acquisition. Perhaps his resignation at some point is inevitable, given that the type of skills and qualities needed to make MySQL great are different from those needed for …

Electing a slave as new master and aligning the other slaves to the new master

In a simple MySQL Replication set-up you have high-availability (HA) on the read side (r). But for the master which covers all the writes (w) and the time critical read (rt) there is no HA implemented. For some situations this can be OK. For example if you have rarely writes or if you can wait until a new Master is set up.

But in other cases you need a fast fail-over to a new master.

In the following article it is shown how to implement the election of a new master and how to align the slaves to the new master.

We can have two possible scenarios:

1. This scenario assumes, that every slave can become the new master.
2. This scenario assumes, that only one dedicated slave will become master.

The advantages and disadvantages of both scenarios:

Scenario 1

+ You can choose the …

Electing a slave as new master and aligning the other slaves to the new master

In a simple MySQL Replication set-up you have high-availability (HA) on the read side (r). But for the master which covers all the writes (w) and the time critical read (rt) there is no HA implemented. For some situations this can be OK. For example if you have rarely writes or if you can wait until a new Master is set up.

But in other cases you need a fast fail-over to a new master.

In the following article it is shown how to implement the election of a new master and how to align the slaves to the new master.

We can have two possible scenarios:

1. This scenario assumes, that every slave can become the new master.
2. This scenario assumes, that only one dedicated slave will become master.

The advantages and disadvantages of both scenarios:

Scenario 1
+ You …

As open-source vendors grow in strength, the value of source code diminishes as a guard against vendor lock-in. READ MORE

On monday I gave a presentation at MySQL user group meeting in Hamburg on the team I’m working for: the MySQL Connectors team. The presentation was given in german. Unfortunately about 99.99999% of all PlanetMySQL had no chance to join the meetup, but you can find the slides (german language) here for download (PDF). The slides give an overview on the team, its products and its activties. You will also find introduction material on those Connectors (drivers) I am working on: Connector/OpenOffice.org, Connector/C++ and all the PHP stuff.

(...)
Read the rest of Slides (german) from MySQL Connectors talk at the Hamburg MySQL Meetup (48 words)