The following is a little SQL challenge I have so far been unable to complte myself. Lets say I have a table with transactions for different products.

I am not sure why this thread ended up on the pgsql hackers list, but nobody took any measures from stopping it and instead a very interesting and detailed discussion of the pros and cons of surrogate keys in RDBMS schema design ensued. So this thread should be of interest to anyone using an RDBMS be it MySQL, PostGreSQL, SQLite or any other alternative.

Well it has becoming increasingly clear that one of the last major IT companies that has not joined the TCPA might even become the first one to make a TPM a major part of their product strategy. I am talking about Apple. But then again at least they are not yet an official member of the TCPA.

So it seems that my original plan of just a few RCs for MDB2 did not go through. I am now at RC4. I have spend alot of time over christmas just reading the source up and down. That way I found a number of bugs and ugly spots that I fixed within those 4 RCs.

Personally last year was very interesting. Not necessarily successful, but enlightening on so many levels, that I am sure 2006 can only be a success. Now over the last few days I afforded myself the luxury (or torture) to look at other peoples code, besides pushing out one RC after another on MDB2 and related packages. Specifically I looked at some of the latest ActiveRecord, CRUD in no time, hyped up frameworks: QCodo, Cake and Symfony.