Well, actually it is not reading future, but just mysql-5.1.30.rhel4.spec file from MySQL RedHat 4 SRPM.

I found there few MySQL Enterprise Editions, namely:

MySQL Enterprise Server - Advanced Edition
MySQL Enterprise Server - Pro Edition
MySQL Enterprise Server - Classic Edition

What is difference ? Let's see.

For MySQL Enterprise Server - Advanced Edition:
%define PARTITION_BUILD 1
%define INNODB_BUILD 1

For MySQL Enterprise Server - Pro Edition:
%define PARTITION_BUILD 0
%define INNODB_BUILD 1
So this one comes without Partitions.

And MySQL Enterprise Server - Classic Edition
%define PARTITION_BUILD 1
%define INNODB_BUILD 0
Which I am finding most interesting ... with Partitioning but without InnoDB ?

Entry posted by Vadim | …

I’ve reposted the slides from my Spockproxy talk (Spockproxy is a Sharding only version of the MySQL proxy).  Since I’ve have to move this web site it’s been some effort to move all of the files into their new homes.

These slides are in a variety of formats and have loads of great information if you’re considering a sharding solution – even if that is not Spockproxy.  Of course once you see how easy it is you’ll put it on your short list.

The slides are available at http://www.frankf.us/projects/spockproxy/  If you want to hear the talk you’ll have to invite me.

Alexander "Salle" Keremidarski works as the Manager of EMEA Support for MySQL and is one of MySQL's longest serving employees. This isn't Salle's first interview on the Devzone, but seeing as how it's been a couple of years, we thought we'd catch up with Salle and see how things are going.

A new database feature in NetBeans 6.5 is the ability to save and
reuse SQL statements that have been executed. A dialog listing SQL
statements along with the date executed can be opened from the SQL
Editor by right-clicking within the editor and choosing SQL History or
clicking an image button for SQL History in the SQL Editor toolbar.

To reuse previously executed SQL statements, in the SQL History
dialog, select an SQL statement then click the Insert button, or
double-click on the SQL History. SQL is inserted at the location of the
editor cursor.

In order to fit the SQL within the width allocated in the dialog,
SQL has been truncated. To see the entire SQL, mouse over the SQL and a
tooltip opens displaying the entire SQL statement.

Initially, the order of SQL displayed is descending by …

I recently built a new file server on which I planned to install Solaris 10 10/08. I’m not a fan of CD/DVD installs, so wanted to jumpstart via PXE, though I only had OSX handy.

Here’s how I installed my new machine (gromit.adsl.perkin.org.uk/192.168.1.10) from my iMac (192.168.1.30) over the local network.

Note that since writing this piece I’ve updated to Solaris 10 10/09, and have changed the examples to use that instead.

Step 1, Prepare File System

First off, create a dedicated file system which we can export our jumpstart configuration from. You can probably skip this and just use any existing file system but this way everything is self-contained and we avoid NFS exporting more than we need.

We use HFSX to ensure that the file system is case sensitive, HFS+ can cause problems with pkgadd(1M).

$ hdiutil create -size 1g -type SPARSE -fs HFSX -volname "install" …

In response to a number of comments, I thought I would clarify the scope of my discussion regarding Options using MySQL pairs before I begin. As mentioned their is no one way or type of configuration for MySQL in a HA solution, however the simplest progression from a single Master/Slave environment is the concept of a pair of servers, configured to support a fail over and fail back via MySQL Replication.

The concept of a MySQL Pair in this context is to have a “hot” MySQL standby ready for controlled and hopefully! automated fail over. I say hopefully because with MySQL Replication as an asynchronous solution there is no guarantee for no loss of data.

I consider DRBD/Heatbeat for example a “cold” standby, as MySQL on the slave server is not actually running. DRBD does provide …

In response to a number of comments, I thought I would clarify the scope of my discussion regarding Options using MySQL pairs before I begin. As mentioned their is no one way or type of configuration for MySQL in a HA solution, however the simplest progression from a single Master/Slave environment is the concept of a pair of servers, configured to support a fail over and fail back via MySQL Replication.

MySQL 5.1 and MySQL 5.1 Connector/J 5.1 have been officially released. Connector/J 5.1 adds support for JDBC 4.0. You can download Connector/J and find out additional info regarding JDBC 4.0 support here.

MySQL 5.1 and MySQL 5.1 Connector/J 5.1 have been officially released. Connector/J 5.1 adds support for JDBC 4.0. You can download Connector/J and find out additional info regarding JDBC 4.0 support here.