I'm currently living in an ORM DBA nightmare. Pulling data for reporting requires an inordinate amount of complex code. Maintenance is hell. I really wish the developers had consulted a database professional when the project was in the design phase. Now, 6 years later, we are stuck with a monster.
Joe said it best in his book "Joe Celko's SQL Programming Style"
3.15 Do Not Use Object-Oriented Design for an RDBMS
Rationale:
Many years ago, the INCITS H2 Database Standards Committee (née
ANSI X3H2 Database Standards Committee) had a meeting in Rapid
City, South Dakota. We had Mount Rushmore and Bjarne Stroustrup as
special attractions. Mr. Stroustrup did his slide show about Bell Labs
inventing C++ and OO programming for us, and we got to ask
questions.
One of the questions was how we should put OO stuff into SQL. His
answer was that Bell Labs, with all its talent, had tried four different
approaches to this problem and came to the conclusion that you should
not do it. OO was great for programming but deadly for data.
