Re: Persistence

Hi,

If you are forced by your boss to use a SQL database because of other
reasons like reporting, legacy code, etc, would you still create a
object model on top of the database, despite the problems with
persisting objects?

Yes I will create object model. But I will try avoid object
persistence. I will try to use object model only for data processing &
visualization. Of course it depends ...


Why do you think OODB never succeeded?

By many reasons. Some of them - OODB has troubles with object identity
when making objective views. As i know none of production OODB can
solve this. I played with my own OODB implementation and found
decision: We should allow to one ID address many instances in different
contexts and allow different IDs address one instance.

Also when OODB implemented as active server then thread synchronization
and isolations is more complex task than transactions isolation in RDB.


WBR,
Dmitry

.