>>Our group has made decision to abandon relational database design and start using "post-relational" DBMS Cache' from InterSystems.
>>I don't say traditional DBMS are bad. I don't say procedural programming is bad. OOP inherits procedural programming concept but allows to deal with high code complexity more easily.
>>And I believe post-relational databases will be the same for DB world as objects for programming world.
>>I don't advertise Cache', I believe there will be more other "postrelational" DBMS from other vendors.
>>
>>Hope this information will help somebody facing same problems.
>
>This different in design been OOP and relational data has long bothered me and they don't mesh all that well. I hope that object oriented databases will become more mainstream and more high preformance. The last thing I want to inflict on my users and co-workers in a niche database system that is difficult to support after I'm gone.

Just as a point of historical perspective, OODBMSs were not designed to outperform RDBMSs. The relational model remains pretty hard to beat when it comes to traditional columnar data. They can churn through character, numeric, boolean, and date fields like nobody's business. OODBMSs are aimed at more complex data such as images and the like.