You may know about the MySQL Cluster, which is a complex architecture to achieve high availability and performance. One of the advantages of MySQL Cluster is that each node is a peer to the others, whereas in a normal replicating system you have a master and many slaves, and applications must be careful to write only to the master. In this article, Giuseppe Maxia, CTO of Stardata IT, provides unique insight into circular replication (multi-master replication) with failover.

When we talk about the future of the web, we often think of web sites from the big guys, like Google, Yahoo or huge phenomena like the FaceBook, or NeoPets.  But open source is actually enabling a new generation of entrepreneurs and individual developers to create applications that are in some cases just garbage.  And I mean that in the best way possible.  Let me explain.

A few weeks ago when I was at LinuxWorld, Bill Hilf from Microsoft demonstrated a very cool site called GarbageScout.  If you haven't seen it, you really need to check it out; it's the perfect example of a Web 2.0 "mashup" that combines Google maps information with photos that people post of random …

This coming week, we will be releasing opentaps version 0.9 at MySQL Users Conference 2006 in Santa Clara, CA. This release is a major milestone in our quest to bring forth a powerful, flexible, well-architected, and truly open source Enterprise Resource Planning (ERP) application. It is the culmination of a three-year effort by myself, our team here at Open Source Strategies, Inc., and the entire global community of Open For Business (OFBiz) developers, contributors, and users.

What Does it Do?

Imagine if you had a very complex business. You sell custom design services to your customers, manufacture products for them, and then warranty your products. At the same time, you also sold off-the-shelf complementary products. Your products are sold online, in retail stores, and by a direct sales force to larger customers. Those larger customers require design documents and contracts.

Now imagine that your …

So who's going to MySQL UC this year besides me? :)

Coming sometime:

Adventures with LSI MegaRAID and SATA RAID
initramfs and brain damage
blah blah blah.

Been reading a lot of the LKML lately. About 90% I delete by subject, the other 10% I try to read and use wikipedia/google to get caught up in terms I don't know. Learn learn learn. I'm a boring person.

Got up at 3:30am to make a 6:10 direct flight from Boston to San Fransicso this morning. Excited to get there and be a part of the MySQL action. Will be spending the day up in San Fransicso doing a little sightseeing and then headed down to Santa Clara in the evening.

Much to my delight the Logan airport WiFi, which has always required a registration (including $$), seems to have let me in without issue so I can get some stuff done while I wait for boarding.

I just got an e-mail from a desperate MySQL user who stumbled across a discussion on the forums that I had some time ago with MySQL's Oleksandr Byelkin. The user hit the same problem I had (and have) when using VIEWs: Whenever MySQL has to use ALGORITHM=TEMPTABLE it's virtually impossible to use the VIEW on all but very small tables.

This issue affects mainly VIEWs that make use of a UNION or GROUP BY. The problem is that the MySQL optimizer currently doesn't push down WHERE conditions from outer queries into subqueries and thus also VIEWs (at least not in these cases, I don't know if there are other situations where a pushdown occurs). This means that before MySQL can start to solve the final outer query, it has to build a temporary table using all the rows …

In a few hours, I'll hop a plane to Santa Clara for the 2006 MySQL Users Conference.  There will be many great MySQL people so I'm sure there will be excellent blog coverage the entire week.  I'll try to post a few thoughts myself.

Oh, and in case anyone missed it, the Visual Express products are now free permanently.  On Windows, I expect Visual C++ Express to be the preferred "free" tool for building MySQL.  As of right now, we build MySQL on Windows using Visual Studio 2003.

My talk at the MySQL Users Conference is officially called "Advanced User Defined Functions in MySQL 5," but if it weren't too late I'd change the name and call it "SQL as a Glue Language."

Sometimes logic should be as close to the data as possible; this is why triggers exist in SQL. MySQL 5 gives you a full-fledged programming language (SQL/PSM), lots of utility functions, and (this is where the "glue" comes in) the ability (using UDFs) to plug into existing C and C++ libraries with ease.

I hope to see you all there Tuesday at 4:30, and then at Jeremy & Hartmut's UDF Hackfest Tuesday night.

In their morning keynote presentation at the MySQL Users Conference, company founders Monty Widenius and David Axmark announced the winners of the 2006 MySQL Community Awards.

It is possible to explicitly insert values into an AUTO_INCREMENT in MySQL, but sometimes these inserts cause confusing behavior. In this article I’ll explain that behavior. Background Suppose I have the following table: create table number ( number int not null auto_increment primary key ) ; Now suppose I insert some values into the primary key explicitly, bypassing the AUTO_INCREMENT feature: insert into number(number) values (-100); select * from number; +--------+ | number | +--------+ | -100 | +--------+ So far, so good.