Sadly, I wasn't able to make the trip to OOPSLA this year, but I found a few podcasts that covered the Objects and Databases: State of the Union in 2006, as well as a few other interesting ones. It's great to hear these issues being discussed, dealing with databases and objects in still one of the fundamental problems in our industry.
There aren't any easy answers, there are benefits to both object databases, and relational databases. The butchering of an object model so it can be shoehorned into a relational database via some mapping layer isn't the answer. Industry wide, the relational folk seem to think this is a solved problem and object databases are modern dinosaurs. Mathematically, they may be right, pragmatically, they're absolutely wrong, and the academics are wrong as well. I don't care how pretty the relational model is, programming to it is a nightmare and doesn't fit the way programmers actually work.
Databases will learn to deal with objects as objects, without crippling them, or they will be replaced with ones that can, period.
Whatever the future of databases are, they will need to learn to deal with random queries (a weakness of object databases) and fast access to objects with a nearly transparent API (a weakness of relational databases). As Esther Dyson says, "Using tables to store objects is like driving your car home and then disassembling it to put it in the garage. It can be assembled again in the morning, but one eventually asks whether this is the most efficient way to park a car.''
There has to be a better solution!