Infobright announced today that Xerox has selected Infobright to provide an Analytic Data Warehousing solution for improved customer insight.

BrightHouse is an analytic data warehouse that takes advantage of the MySQL database server's pluggable storage engine architecture . Using BrightHouse, Xerox will have a solution that allows business intelligence analysts to quickly and easily analyze customer data to more rapidly react to changes in the market. BrightHouse has very low administrative and maintenance requirements, resulting in a very low IT overhead for the solution.

MySQL Toolkit version numbers are based on Subversion revision number. This release is the first past the 1,000-commit milestone. It also marks several days of being in Sourceforge’s top 100 most active projects. It has been in the top 300 for a couple of months, and the top 1000 for, um, a long time. While I would hasten to say I’m not a popularity-contest-focused person, it’s rewarding to see that people think this project is important and useful.

I’m on the select board of elite people who were duped into reviewing proposals for the upcoming MySQL Conference and Expo 2008, and I’m here to tell you how to get your proposal accepted. Aside from bribing me with chocolate, that is. These are my opinions. Believe it or not, I have not been instructed how to evaluate proposals. And by the way, I have no authority to get your session accepted – I only get to say how good I think it is.

Work continues apace on High Performance MySQL, Second Edition (the link leads to the chapter outline). I’m working now on Chapter 6, Advanced SQL Functionality, and thought I’d solicit input on it. Are there things you’d like to see us cover? Do you have any favorite techniques you’d like to see us include? Feel free to leave feedback in the comments. The chapter is already significantly done, with 26 pages written, but the ink’s not on paper yet, so there’s still time to correct omissions!

As the opentaps Open Source ERP + CRM community continues to grow, I will try to publish a regular update to keep all our users, contributors, and services providers up to date with our progress.

Recent Developments

The past few months have been a period of significant changes in opentaps. By incorporating several new open source applications into our core framework, we are now positioned to transform opentaps from an ERP application to an enterprise-wide application platform. The new opentaps 1.0 will offer a full range of capabilities, including mobile connectivity and a choice of open source business intelligence tools, on top of our core ERP and CRM features.

Some of key developments include:

• Integration of the Funambol Data Synchronization via the …

So last week MySQL was on site at work for MySQL DBA Certification prep. class (which was very awesome and highly recommended, by the way) and one of the things that came up was how much faster enumerated types would be over using JOINs, say to store things like the categories of a blog not unlike this one. Well, the issue had been bugging me so I thought I would figure it out. This time around, I wanted to get my feet wet with mysqlslap, since it basically does the same thing as my SQLBuster, only better :)

What I did was basically run two tests. One was running my original query to pull up a single blog post, which contained two JOINs to de-normalize the categories and moods. The categories and moods tables are very small - less than 20 records, but I do have indexes setup …

This is a friendly reminder that we have opened our Call for Participation for the MySQL Users Conference 15-18 April 2008 in Santa Clara, California.

Yes, 15 April next year may seem far away. But 30 October this year isn’t. And that’s when the Call for Paper closes.

Some UC 2008 highlights:

• Conference theme is “Harnessing the Power of MySQL”
• We expect to bring over 1,500 open source and database users together
• Over 100 sessions, geared toward many skill levels (novice to expert)

Consider to present, especially if you belong to one or more of the below …

Thought I’d mention that a new case study featuring Pentaho and Kettle showed up over at the Database Trends and Applications. The name of the paper is called “Loma Linda University Health Care Deploys Pentaho BI” (PDF).

To quote :

With commercial products you don’t know if you are getting what you want, but with open source you can create proofs-of-concept. And the TCO is so much lower.

Until next time!

Matt

Recent couple of days our team was pointed to number of bugs in MySQL 5.0 which again seriously shakes the confidence in both MySQL Quality Control and bug fix promptness.

Let me just take couple of bugs as examples:

Triggers broken with auto-increment columns for Innodb tables (bug 26316). As you can see this bug is reported in February - over 6 months ago and it is still in verified state even though it has "serious" severity.

ORDER By DESC broken for Innodb tables (bug 31001) This is also very interesting - the VERY basic functionality gets broken and passes quality control. And why it is broken ? Because minor optimization was implemented in MySQL 5.0.

Surely …

We use a lot of dual master setups for redundancy and recoverability. Typically, most apps can't write to both masters at the same time, so for consistency we keep only one of the masters read-write at any given instant. To switch over gracefully, turn the primary read-only, wait for replication to catch up, turn the secondary read-write. Simple, eh?

Well, I've just had a report that setting the primary read-only caused a transaction to be partially replicated to a slave. Wait, what? If I'm reading the email correctly, they switched masters in the middle of a transaction. The transaction commit correctly failed on the master with a read-only error, but somehow the other master (or a slave) got part of the transaction that failed and had to be skipped.

This was an innodb table in MySQL 5.0. My first thought was that XA was disabled (though we typically use 4.1 here, so I thought of innodb_safe_binlog). I verified that the …