This article shows how to create a MySQL-plugin that can be used to create a function which can in turn be used in stored procedures. The function will produce an integer value representing the time (to the nearest usec).

I’m working on an article for conflict detection/resolution when using MySQL Cluster asynchronous replication which requires an integer column to store a timestamp for comparison purposes. In fact, it doesn’t actually need the timestamp to represent an absolute or even a relative point in time – all it cares about is that the if the function is called twice on 2 different hosts that the 2nd call will always result in a larger number than the 1st. Obviously, in a production environment the times on the 2 hosts would need to be kept in sync.

The c code (inttime.c)

#include <mysql.h>
#include <sys/time.h>

my_bool inttime_init(UDF_INIT *initid,UDF_ARGS *args, char *message) {
  return 0;
} …

Optimized tool facilitates database developers and web masters to efficiently work with remote databases at a lower cost with a greater speed.

Devart today announced the release of dbForge Studio for MySQL v 3.60, a cutting-edge tool for administration and development of MySQL databases.

The new upgrade is the contemporary answer for common bottlenecks originated from employing remote
MySQL Servers while developing, updating, and using modern large databases. dbForge Studio for MySQL v 3.60 offers new freedom for those who work with large schemas and data amounts especially in cases of using remote MySQL servers, for example serving web sites.

Unlimited database connectivity

It is good news for web developers working with remote databases, as employment of remote connections becomes as simple as …

Yesterday InnoDB Plugin 1.0.4 was released by Innobase. This version contains one of the most important performance fixes - "Fix for broken group commit". After MySQL5.0, InnoDB breaks group commit when using with binary log (or with other transactional storage engines), even though setting innodb_support_xa=0. This was really serious because fsync() (called at transaction commit when setting innodb_flush_log_at_trx_commit=1) is very expensive. The initial bug report about this was submitted by Peter four years ago. Last year David Lutz submitted a bug report with his prototype patch. It is great news that this bug fix has been finally implemented in the official InnoDB release.
I did a simple benchmarking by …

It’s been a busy and exciting week since we announced RethinkDB. Of all the feedback we received, the most common request was for performance numbers. Before the launch our top priority was correctness. We spent most of our time testing RethinkDB with Wordpress and adding the missing features. As a result, performance suffered. In the past week we tuned the engine back up to high performance. We’re still far from finished with the improvements we want to make, but we feel that we’ve reached a level of performance we can be proud to display.

We wrote our original benchmarking tool in Python, but during our latest benchmarks, we noticed that it was taking about as much time as the engine itself, hiding our real performance numbers. We now have a very small Objective-C program (<900 lines) that uses prepared statements in a tight loop, and times only across the mysql_stmt_execute() call.  For inserts, the …

If you're interested in ways to back up stuff, and haven't tried Dar yet, here's an article on using Dar that I've just published on my personal blog. In short, Dar works very much like Tar, but it's got a built-in feature for slicing up archive files which comes handy when you want to distribute backup files across several media, for example DVDs or hard disks.

It's been a busy and exciting week since we announced RethinkDB. Of all the feedback we received, the most common request was for performance numbers. Before the launch our top priority was correctness. We spent most of our time testing RethinkDB with Wordpress and adding the missing features. As a result, performance suffered. In the past week we tuned the engine back up to high performance. We're still far from finished with the improvements we want to make, but we feel that we've reached a level of performance we can be proud to display.

We wrote our original benchmarking tool in Python, but during our latest benchmarks, we noticed that it was taking about as much time as the engine itself, hiding our real performance numbers. We now have a very small Objective-C program (<900 lines) that uses prepared statements in a tight loop, and times only across the mysql_stmt_execute() call. For inserts, the benchmark creates a …

If you're interested in ways to back up stuff, and haven't tried Dar yet, here's an article on using Dar that I've just published on my personal blog. In short, Dar works very much like Tar, but it's got a built-in feature for slicing up archive files which comes handy when you want to distribute backup files across several media, for example DVDs or hard disks.

As you might have seen Innodb Plugin 1.0.4 was released today. I am very excited to see this release which is released exactly 5 months after release of Innodb Plugin 1.0.3 (I honestly expected to see Innodb Plugin 1.0.4 to be released by MySQL Conference and Expo in April). This also is still "early adopter" version of a plugin which is a bit of disappointment as we can't wait for Innodb plugin to become stable/GA but considering number of improvements this is probably good thing.

We're also pleased to see some of Percona contributions made in this release (in modified form) while others were evaluated and given ideas for different implementations.

Among other changes I'm especially pleased with fixed …

If you're interested in ways to back up stuff, and haven't tried Dar yet, here's an article on using Dar that I've just published on my personal blog. In short, Dar works very much like Tar, but it's got a built-in feature for slicing up archive files which comes handy when you want to distribute backup files across several media, for example DVDs or hard disks.