This is always mentioned that InnoDB is slower in giving results for COUNT(*) as compared to MyISAM. But as Peter points out in his blog that this fact only applies to COUNT(*) queries without WHERE clause. This text is from Peter's blog only - "If you have query like SELECT COUNT(*) FROM IMAGE WHERE USER_ID=5 this query will be executed same way both for MyISAM and Innodb tables by performing index rage scan. This can be faster or slower both for MyISAM and Innodb depending on various conditions." Let's see what EXPLAIN has in store for us.

   1: mysql> CREATE TABLE `test_index` (

   2:   `id` int(11) NOT NULL AUTO_INCREMENT,

   3:   `x` int(11) DEFAULT NULL,

   4:   `y` int(11) DEFAULT NULL,

   5:   `z` varchar(255) NOT NULL DEFAULT 'testing',

   6:   PRIMARY KEY (`id`),

   7: …

This article details how to setup MySQL 4.1 or later on Mac OS X Tiger 10.4.x. Additionally it tells you how to add java support and configure MySQL so that all new database tables use the InnoDB transaction-safe database engine instead of the default MyISAM engine. This is essential if you are writing applications with technologies such as WebObjects that automatically utilize the ACID commit or rollback capabilities of a transaction-safe database.

Dear Kettle fan,

While this first milestone release of Kettle version 3 is absolutely NOT YET READY FOR PRODUCTION, it’s a nice way to see the speed of our new architecture for yourself.
Version 3.0 is a complete refactoring of the complete Kettle code base and as such it will take a while for things to settle down again.
That being said, we have a number of tests that tell us this might be a good time to tell the world we’re still very much alive.

As noted above, this release focuses on performance.  Version 3.0 was reworked to completely separate data and metadata.  This has led to significant performance gains across the board.  At the same time we expect all your old transformations to run unchanged.  (if not, it’s a bug)

Get your new software fix over here: …

A few weeks ago, I had a chance to speak with Scott Swigart about MySQL, open source, development and community challenges, and other stuff. He sent me a link to the published interview, available on HowSoftwareIsBuilt.com. It was very interesting reading the comments of some of the other interviewees, like Stormy Peters, from OpenLogic, and Patrick Hogan, from NASA.

This article details how to setup MySQL 4.1 or later on Mac OS X Tiger 10.4.x. Additionally it tells you how to add java support and configure MySQL so that all new database tables use the InnoDB transaction-safe database engine instead of the default MyISAM engine. This is essential if you are writing applications with technologies such as WebObjects that automatically utilize the ACID commit or rollback capabilities of a transaction-safe database.

Matt Asay realises the "support" model is broken in an Open Source economy. Or at least buggy.

In Thinking about renewals in a productive fashion he starts wondering with Savio Rodrigues

What happens when 15 percent of your current paying customers decide they can use your (open-source software) product without paying you a dollar. Worse still, these are users you convinced to buy support/license from the mass of nonpaying users. Customers surely realize that their support/license payments enable the OSS vendor to continue developing the product in question. Sure, you get some free development from the community, but 95 percent-plus is still done by the vendor's employees. What happens when more and more customers pass the "pay for continued development" buck and …

Charlie Babcock of InformationWeek is reporting results of a Sun survey that finds PostgreSQL to perform just 12% lower than Oracle on similarly-priced hardware. Not bad.

The database, of course, is not "similarly priced." The punchline, therefore, is that customers who pony up seven figures for their Oracle databases may well find that $0.00 can deliver near-equivalent performance. If only CIOs were paid based on the savings they generate while still cranking out hefty IT performance, many IT professionals might find open source databases like PostgreSQL under their Christmas trees.

...

My framework of choice at the moment is called "everything". Everything has very few users in the world, but it holds to a certain number of
design characteristics that I like.

It deals with entities as objects
Objects are inheritable
Easy to hack
Revision control on objects

If I were a Java developer, which I have not been in more then a
decade, I would use Hibernate. Hibernate has many of the design characteristics that I list. Similar frameworks exist for PHP and Python.

Why do I like the approach of using objects? Objects are entities that I can serialize and store in caches as a single discrete item. Object caches are common in web architectures now(aka Memcached and other similar creatures). Object store works well, and it is constantly improving.

Many web infrastructures can be run out of object store systems, but not all.

Many, …

another month, another mysql connector/odbc release. it has almost become a trend. we only chipped it down to about 124 bugs this time, about a half-dozen less than last time. but we?re going back and re-evaluating some the open bugs now.

we didn?t manage to get windows x64 packaged up this time, but we might slip out a 3.51.17 package for that platform before the next full release. part of the problem in getting it together in time for this release was that odbc on win64 appears rather half-baked, and we couldn?t find much in the way of applications to test with it.

now i?m hip-deep in making sure that the way we calculate the various column lengths that you can retrieve from odbc are …