For those of you attending my JDBC 4.0 and MySQL session, you can find the sample code I'll be using in the Connector/J subversion repository

http://svn.mysql.com/svnpublic/connector-j/trunk/jdbc-4-0-examples/

I'll have it up on the projector, but it's often easier to follow along locally.

For those of you attending my JDBC 4.0 and MySQL session, you can find the sample code I'll be using in the Connector/J subversion repository

http://svn.mysql.com/svnpublic/connector-j/trunk/jdbc-4-0-examples/

I'll have it up on the projector, but it's often easier to follow along locally.

We spent today working on the last minute details for the mySQL conference. The important things: T shirts, pens, mugs, etc….

Seriously, I’m pretty excited about the conference. I think conferences have transmogrified since the days of Interop and Internet World ‘97-’00 and many have reemerged as events actually worth going to.

Back before the Internet, most people would go to conferences to actually learn about new products, trends, etc. Companies typically sent their best developers and product managers to meet with attendees. But sometime around ‘98, many attendees learned that they could find all the info they needed on the net and didn’t have to send anyone. Attendance dropped, and exhibitors stopped sending their best and brightest. The attendees at subsequent conferences were greeted by nit wits that didn’t know anything and attendance dropped further. The …

In my first day at the MySQL Conference and Expo 2007, I attended the Scaling and High Availability Architectures tutorial in the morning, and Real-world MySQL Performance Tuning in the afternoon. This is a brief article on each session's Big Ideas, and a short blurb about the conference overall so far.

I'll also be involved in at least three sessions at the conference, and I describe them.

If you're interested in short overviews of the sessions I attend, keep watching for my articles. I will give you each session's major ideas instead of writing stream-of-thought notes. You can look at the presenter's slides for more.

Day 0 (tutorials), post 2. (I’m still working on the versioning thing — bear with me.) I snuck into the 5.1 new features session halfway through but definitely well worth it. Lots of new features coming out in 5.1 though Brian Aker admits some of them are not quite production-ready yet, so don’t go [...]

MySQL AB today announced the launch of a new business partner program designed to make it easier for resellers, software vendors, hardware companies, and IT service providers to offer their database-related solutions to the millions of MySQL users worldwide.

A wide range of companies have announced plans to join the MECA program, including: Alfresco, AxisOS, BakBone, BitRock, CodeGear, Continuent, Dolphin Interconnect Solutions, Embarcadero, FileMaker, GoldenGate Software, Hewlett-Packard, Infobright, Ingram Micro Inc., JasperSoft, Logicworks, NetApp, NitroSecurity, Oracle/Innobase, Pentaho, PremiumSoft, Red Hat, RippleTech, SugarCRM, Solid, Sun Microsystems, Talend, Tandem-Forum, Unisys, Webyog and Zmanda.

MySQL AB?s CEO Marten Mickos kicked off the opening day of the 2007 MySQL Conference & Expo this morning with a keynote exploring the phenomenal momentum of open source software as both a disruptive force on the traditional enterprise software industry and a positive communal movement among individual software developers.

Infobright today announced the general availability of BrightHouse Version 2.3 with enhanced support for complex and ah-hoc queries across very large amounts of data.

This article shows the easiest way to audit commands to a MySQL database, assuming all content happens from an application. Now, this will use a lot of storage, and doubles the query load for each query, but it’s useful for when you know you want to capture the information of someone using the application.

The basic premise is simple. Logon to your nearest MySQL server and type the following:

SELECT CURRENT_USER(), USER();

Chances are the values are different. More on this later.

First, create a table:

CREATE TABLE `action` (
`user` varchar(77) NOT NULL default '',
`asuser` varchar(77) NOT NULL default '',
`db` varchar(64) NOT NULL default '',
`query` mediumtext NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

Why varchar(77)? Because the mysql.user table puts a maximum of 16 characters for the username, and 60 characters for the …

I’ve been thinking about the query cache since last years user conference. One of the features of the query cache is that it’s completely transparent to client. It achieves this by clearing cache entries for tables as soon as the tables are updated. This makes the cache inefficient for tables that are constantly updating.

While thinking about this also thought about slaves and non critical reads. In a replication setup reads that are sent to slaves expect to get data back that might not be the most current. In this situation it doesn’t make sense to expire the cache for every single update because queries running against the slave already know that they are going to get back slightly old data. I thought, “Why not add a time to live to cache entries instead of clearing them for every update?” So, I did.

I added an option to select called sql_cache_ttl. This option instructs the query cache hold the entry in the cache for …