Oracle contributes code to Linux community. Linux Foundation adds legal talent. Luxoft open sources test automation tool. (and more)

Oracle Contributes Enhancements To Linux Community, Oracle (Press Release)

Leading Open Source Legal Experts Join Linux Foundation, Linux Foundation (Press Release)

Outsourcing Leader Luxoft Contributes New Test Automation Tool to Open Source, Luxoft (Press Release)

Oracle Provides Six New Validated Configurations for Linux …

Direct play this episode at:
http://technocation.org/content/oursql-episode-21%3A-rise-mysql-dba-1

Paul Vallee is back for this non-technical podcast about the special creature that is the MySQL DBA.

News:
October 2006 Enterprise/Community Split announcement
http://www.planetmysql.org/entry.php?id=4393

Current clarification of Enterprise/Community split
http://www.planetmysql.org/kaj/?p=123

Dorsal Source, a community-focused website whose goal is to provide builds of MySQL and related products.
http://www.dorsalsource.org

Learning Resource:
MySQL Camp II, August …

Mike Kruckenberg, well-respected community member recently blogged about MySQL taking another step (away from open source, and I’d like to refute some of his worries. In fact, this is really more to drive away from what some within the community think is not kosher, i.e. change #5 in Kaj’s blog entry.

The sources are always available. Its just gone one step further, in that you need to use the Bitkeeper free client, and pull the correct revision, tags of which are always at http://mysql.bkbits.net/. From there, you are welcome to compile it yourself, and even make a binary distribution, all with fair ease thanks to the excellent …

Paul Vallee is back for this non-technical podcast about the special creature that is the MySQL DBA.

News:
October 2006 Enterprise/Community Split announcement
http://www.planetmysql.org/entry.php?id=4393

Current clarification of Enterprise/Community split
http://www.planetmysql.org/kaj/?p=123

Dorsal Source, a community-focused website whose goal is to provide builds of MySQL and related products.
http://www.dorsalsource.org

Learning Resource:
MySQL Camp II, August 23-24 2007, Brooklyn NY
http://www.mysqlcamp.org

http://www.poly.edu

Feature:
The …

If you haven't checked out the MySQL Proxy yet, it is definitely worth playing with. One of the most useful features is the embedded Lua interpreter that allows a user such as myself to write scripts that modify queries and responses. Upon each connection to the proxy server, the Lua script is loaded and affects only that connection. Unfortunately my project requires logging over multiple connections (hard when each connections has its own instance of the script), but Jan was nice enough to add the PROXY.global feature. Now a single instance of my logging module can be used by multiple connections. So for your viewing pleasure, I am going to show you an example of how to use the globals in case you ever venture into using the proxy's embedded Lua interpreter.

So, to keep it simple, lets say that you want to simply count the number of queries that come through the server. Here is a script that adds one to `query_count` every time a …

The idea is as old as Replication is:

How do you know which is the most current slave.

You can use the Master_Binlog_Pos to guess what is most up to date, but which transaction does this binlog position match ?

With the proxy you can add a global transaction ID to your setup, if you let the inject some information into the stream.

The idea is simple and is documented in various places.

Create a MEMORY table which is replicated with a single UNSIGNED BIGINT and increment it at the end of each transaction.

CREATE TABLE trx (
  trx_id BIGINT UNSIGNED NOT NULL
) ENGINE=memory;

INSERT INTO trx VALUES ( 0 );

When ever you commit a transaction UPDATE the trx_id field:

UPDATE trx SET trx_id = trx_id + 1

Usecases:

• identify which slave is most current and …

MySQL Camp Website Transitioning Right Now

In case anyone noticed, the mysqlcamp.org website is currently down, as the DNS resolution occurs. Hopefully, the resolution will be completed in a few hours, when you will see a brand new Drupal-fied MySQL Camp website. Again, the purpose for moving the website was to have full control over the software (it was previously a pbwiki website) and to address the spam problems we were having. Thanks for your patience.

By tomorrow morning, I plan to start posting session proposals as well as getting Sheeri's help to get hotel, ride and room share information, and stuff about the All-Night Hackathon, up on the site...

First 150 MySQL Camp II Registrants Receive a T-Shirt

Farhan and one other as-yet-unnamed sponsor have graciously decided to donate 150 …

This is a continuation of my earlier post with the same title. Recently while solving a problem where values of an auto_increment fields were getting repeated, a well documented and often neglected feature of InnoDB came forward. Lets first have a glimpse of the system and the problem.

We are maintaining a job queue in an InnoDB table for a distributed resource environment. This job queue is populated by distributed schedulers from the system, the job is assigned to a resource and once the job is done, it is removed from the job queue. The system runs on an assumption that the job id, which is an auto_increment field, always remain unique throughout the life of the system. I acknowledge that the usage is debatable, but lets keep it separate from this.

The problem: The operations team restarted the MySQL server in between. After that restart, some job id's got repeated. This broke the basic assumption of unique job …

In the ongoing effort to convert more users into paying customers, MySQL announced today that they are no longer making the source code tarball for their Enterprise server publicly available. You could see this coming from a million miles away.

Back in December 2006 I pondered on the changes with the MySQL database splitting into two offerings, the enterprise and community editions:

The source for the enterprise edition will still be available: we will continue to make all releases available over our BitKeeper tree and as source code tarballs So it appears that those willing to compile from source will still have access to the enterprise edition. This is very important (in my eyes) to …

Back in October 2006, we introduced MySQL Community Server. Since then, we’ve learnt a thing or two, spent many man hours discussing how to improve our processes, and are now refining the concept. We feel that we’ve come up with some good middle-ground that fulfils not only our company interests but fosters community use and growth as well.

The changes are in the areas of release policy and stability of MySQL Community Server and in the availability of MySQL Enterprise Server.

The changes start from the question: “How can we better target MySQL Community Server to the community and MySQL Enterprise Server to the paying customers?“. Many of them originate from our ongoing discussions with the Linux Distributions, some of whom have been distributing MySQL …