I have never been to a DrupalCon before so my first was DrupalCon Portland 2013 (with some 3,500+ attendees). My first DrupalCon happened to also be one that I spoke at, and I hope to return to Austin in 2014 (added bonus: I’ve never been to Texas before).

SkySQL had decided to get a booth at DrupalCon since I was speaking and I have to say that the booth was very successful. You may ask why and the simple reasons are:

1. Everyone at DrupalCon was a user of MySQL. Once they hit scale, they may need professional services or even just switch to MariaDB. This is a captive audience.
2. Everyone running Drupal at scale with many modules and nodes generally faced issues with database slowdowns. Hello …

The MySQL for Developers course teaches you the knowledge, skills, tools and issues involved in writing applications with the MySQL database server. It forms the core of the MySQL Developer learning path.

During this 5-day course, you will perform lab work with Java and PHP, connecting to MySQL databases and executing queries and stored routines. Enrolling in this course will simultaneoursly help you prepare for the Oracle Certified Professional, MySQL Developer certification.

You can take this instructor-led course as a:

• Live-virtual event: Take this class live, from your own desk. No travel required. You can choose from a wide selection of events on the schedule to suit different timezones.
• In-class event: …

Hi Daniel,

Thanks for your comment. The function lock_get_mode() is declared as an inline function. Are you using optimized build? Also, in gdb, try the option "/4bt" instead of just "/4t" for the command "x". I think it is better to specify the size of the object explicitly.

Rgds,
anna

In the replication topology I manage there are many layers of replication filters that prune data at the database and in a few places table level. The way MySQL replicates Data Definition Language (create, alter, drop) statements differs from how Data Manipulation Language (insert, update, delete) statements are handled with row-based replication. I often need to fix broken replication due to a lack of understanding of these subtle differences.

With row-based replication DML statements focus directly on the table being modified. DDL on the other hand always uses statement-based replication and is tied to what is known in MySQL as the "default database". The default database is the schema/database currently in use when a DDL …

I really like the article.

I had to use lock_get_mode_str() instead of lock_get_mode(). And the bitmap was printed differently.

(gdb) p $rowlock
$3 = (ib_lock_t *) 0x7f9f94011d40
(gdb) p lock_get_mode($rowlock)
No symbol "lock_get_mode" in current context.
(gdb) p lock_get_mode_str($rowlock)
$4 = 0xc346b8 "X"

(gdb) x /4t $rowlock + 1
0x7f9f94011d88: 00000000000000000000000000011110 00000000000000000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000

This is with 5.6.10 on Linux (64-bit).

And maybe it's better to put the PDF link in at the beginning of the article.

Since Tarantool stored procedure API was extended with socket I/O, a whole universe of applications for data-enriched networking (routing, proxying, PUSH-notifications, and so on) has become possible.

But there is one case which doesn't lend itself so easily: anything MySQL. The first scenario I'd love to support is when Tarantool works as a smart write-back cache for MySQL, providing a higher update RPS, but automatically maintaining a slightly dated copy of all the data in a relational database.

One dramatic shortcoming of MySQL universe, which, IMHO, if addressed properly, could spark a whole new set of uses and third-party solutions, is the clumsiness of the client-server protocol.

The MySQL client-server protocol is unnecessarily hard to implement: it is built on top of a layered design, with built-in compression and transport-level tricks to be able to communicate over unreliable protocol such as …

Since Tarantool stored procedure API was extended with socket I/O, a whole universe of applications for data-enriched networking (routing, proxying, PUSH-notifications, and so on) has become possible.

But there is one case which doesn't lend itself so easily: anything MySQL. The first scenario I'd love to support is when Tarantool works as a smart write-back cache for MySQL, providing a higher update RPS, but automatically maintaining a slightly dated copy of all the data in a relational database.

One dramatic shortcoming of MySQL universe, which, IMHO, if addressed properly, could spark a whole new set of uses and third-party solutions, is the clumsiness of the client-server protocol.

The MySQL client-server protocol is unnecessarily hard to implement: it is built on top of a layered design, with built-in compression and transport-level tricks to be able to communicate over unreliable protocol such as …

The Texas Linuxfest might be the ‘little brother’ of the SCaLE show. While a smaller shower in length, it fells much more muscular. I had a full room for a session on The Proper Care and Feeding of a MySQL Database. The audience was sharp, asked amazingly great questions, and hungry for MySQL 5.6 features. And at the booth I was pleasantly inundated with MySQL questions and proud DBAs bragging about their instances.

If you missed the this show this year, please make the trip to Austin next year. You’ll not be disappointed.

This week we discuss MySQL Views. Ear Candy is GRANTs and replication and At the Movies is a presentation by Giuseppe Maxia talking about "Creating Multi-Master clusters with Tungsten Replicator".

Events
DB Hangops - every other Wednesay at noon Pacific time

Upcoming MySQL events

Training
SkySQL Trainings

Tungsten University trainings

read more

Lately more people ask me for comparisons between Percona Server & MariaDB. There isn’t a definitive blow-by-blow feature comparison yet, but it’ll come soon.

All that said, its great to see new features from MariaDB make it into Percona Server. The features that I’ve managed to track: group commit for the binary log, threadpool and atomic write support for Fusion-io devices.

It started with the group commit for the binary log feature in Percona Server 5.5.18-23.0 ( …