Regarding OOP, I don’t think I ever said that it ought to be more important within the database, but outside it is as much a fact of life as SQL is for databases. If there is a story to be told about bringing these two sides together, other than ORM, than the post of the master storyteller is still vacant.

I’m not at all sworn in on object relational mapping, in fact, after reading about Object-Role Modeling (Halpin/Morgan) recently, I’m quite interested in other approaches and therefore will have a good look at your andromeda framework

But anyway, the cultural distance you mention ought in itself to be compelling. Could it possibly be that OOP is not as relevant to database management as current fashion suggests? I would contend that this is so, that to truly make use of a database effectively you should start with the obvious: it is what it is and not something else. Forget C, perl, java, PHP or whatever and learn the database on its own terms. Then decide how to interface to it.

In other news, your comment on my “Why I Do Not Use ORM” blog post I found to be challenging and compelling. I have put an addendum into the blog in which I do my best to spell out the different assumptions between my own approach and the ORM approach, and gave the most space to answering your challenge. Thanks for the comment, while we may never agree, it did help me to strengthen the thesis.