Thoughts and MaxDB and MySQL
So... I was talking with my cohort, Ulf about the future of MySQL and MaxDB.
He got me thinking about what the relationship between MySQL and SAP/MaxDB really is. What does the "partnership" mean a few levels below the VP?
To me, it means that, going forward, I expect to see a lot of communication and camaraderie between the MySQL and MaxDB developers. I expect to see a lot of MaxDB's rock solid, tried and true code become shared libraries which are then linked against by MySQL. I expect to see a lot of MySQL's tools that provide the usability and simplicity that the community has come to expect from them generalized in such a way that they can be used to administer a MaxDB system. I expect to see MaxDB adopt MySQL's modular storage engine architecture.
But I think that this partnership should not stop at MaxDB and MySQL. I think that the PostGres and BDB projects should also share some of their most valuable code with others in the community.
Which brings me to one of the things that starting at MySQL has brought to my attention. The PostgreSQL community is (or at least many of its most vocal members are) violently opposed to anything MySQL. PostGres is a great database. There's no disputing that. But being great does not mean that anything that is not your product is worthless.
I suppose saying this can be considered an olive branch of peace.
The truth of the matter is this: We are all trying to make a great free database. Free means different things to different people. Let us find our common ground and share our ideas and ideals there.