Want to learn to develop next generation web applications on MySQL using languages such as Java and PHP; take the MySQL for Developers course. In this course you will learn to:

• Use MySQL tools to connect to databases.
• Examine database structure and contents.
• Generate database structure diagrams.
• Execute complex queries.
• Manipulate numeric, text, spatial and temporal data.
• Execute complex subqueries and joins.

You can take this 5-day instructor-led course as a:

• Live-virtual event: Take this course from your desk - no travel required. Choose from a wide selection of events on the schedule to suit different time-zones.
• In-class event: Travel to an education …

It will soon be November and we'll be queuing up to register for the Percona Live conference once again. I spoke with some of this year's Percona Live London committee we all agreed that it would be great to arrange a community dinner if there was a community interest. In the past years of the PLUK conference there has not been a community event to attend in order to discuss sessions and make new friends. I for one love the `Pythian-arranged Community Dinner` at Pedro's that occurs annually in Santa Clara during the Percona Live Conference. I know that there are many attendees that do London and CA each year and wager that they'd agree that it's a great event. So lets have it... please r.s.v.p here and if the numbers are good enough we'll schedule something the evening of the tutorials. Please let me know of your interest in the comments below. Thanks :D

When I saw Shlomi’s recent post which asked (in part) for blacklist support in MySQL, I started thinking about ways in which this could be done using the tools we have today.  Here’s the example requirements Shlomi noted:

Speaking of whitelist, it would be great to have a host blacklist. If I wanted to grant access to ‘gromit’@’192.168.%’ except for ’192.168.10.%’ — well, I would have to whitelist all the possible subnets. I can’t exclude a set of hosts.

I think that’s entirely possible without the overhead of whitelisting all possible subnets – let’s give it a go!

This solution will rely on the fact that the first step in authentication in MySQL is finding the most applicable host for the incoming connection.  That’s caused all sorts of annoyances in the past with the anonymous user, where …

This week’s Log Buffer Edition casts light on selected blog posts from different database logs across the globe slicing and dicing different ideas. Enjoy!

Oracle:

Saurabh Verma is correlating SQL statements in DB Sessions with ODI Sessions in ODI 11.1.1.7.

David Allan is writing about file transformation debatching within ODI.

An interesting thread about OEM 12c support for the database 12c release is currently on the oracle-l mailing list. Martin has more.

Anyone who has been around Oracle performance over the years knows the grief that …

Is there any way to restore just one partition from MEB backup? See http://bugs.mysql.com/bug.php?id=70196 for potential use case.

I think MySQL 5.6 has many excellent features that are worth the cost of upgrading and then I read about MySQL 5.7.2 and the improvements keep on coming. Alas the notes are also full of references to bugs behind the support paywall so in many cases I wasn't able to learn more about the changes. Some of the changes are for feature requests from us or are rewrites of diffs from the FB patch. There are many interesting changes. I expect some of them to be backported to 5.6 by the community.

• better scaling for concurrent connection create. We started to fix this but the change was a bit too complex for the FB patch. It is nice to see an official fix. Domas has also …

I think MySQL 5.6 has many excellent features that are worth the cost of upgrading and then I read about MySQL 5.7.2 and the improvements keep on coming. Alas the notes are also full of references to bugs behind the support paywall so in many cases I wasn't able to learn more about the changes. Some of the changes are for feature requests from us or are rewrites of diffs from the FB patch. There are many interesting changes. I expect some of them to be backported to 5.6 by the community.

• better scaling for concurrent connection create. We started to fix this but the change was a bit too complex for the FB patch. It is nice to see an official fix. Domas has also …

Continuent and our client base are growing fast. We are looking for brilliant people to join us. We’re looking for passionate people that can make things happen. You'll be working with a team filled with top notch talent, and you’ll be competing in an evolving market of database clustering and replication. A career at Continuent means you'll be working with an amazing team with tons of benefits

To expand on Jervin’s Default RDS Account Privileges, RDS for MySQL provides a number of routines and triggers defined the the ‘mysql’ meta schema. These help in various tasks because the SUPER privilege is not provided.

SELECT routine_schema,routine_name
FROM information_schema.routines;
+----------------+-----------------------------------+
| routine_schema | routine_name                      |
+----------------+-----------------------------------+
| mysql          | rds_collect_global_status_history |
| mysql          | rds_disable_gsh_collector         |
| mysql          | rds_disable_gsh_rotation          |
| mysql          | rds_enable_gsh_collector          |
| mysql          | rds_enable_gsh_rotation           |
| mysql          | rds_kill                          |
| mysql          | rds_kill_query                    |
| mysql          | …

It was just a few days ago that we announced, with celebratory enthusiasm, Tungsten Replicator 2.1.1, and today we are at it again, with Tungsten Replicator 2.1.2.

What happened? In a surfeit of overconfidence, we released Tungsten 2.1.1, with faith on the test suite and its result. The faith was justified, as the test suite was able to catch any known problem and regression. The overconfidence was unjustified, because, due to a series of unfortunate events, some sections of the test suite were accidentally disabled, and the regression that was lurking in the dark was not caught.

Therefore, instead of having a quiet post-release week-end, the whole team has worked round the clock to plug the holes. There …