Re: Persistence
- From: frebe73@xxxxxxxxx
- Date: 13 Jul 2006 11:06:28 -0700
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 ...
I think I agree with this. If objects should be persisted I think a
database similar to a network database need to be used.
Why do you think OODB never succeeded?
By many reasons. Some of them - OODB has troubles with object identity
when making objective views.
Why does one need objective views? Does objective views correpond to
relational views? If yes, doesn't it break encapsulation?
Also when OODB implemented as active server then thread synchronization
and isolations is more complex task than transactions isolation in RDB.
I think this is one of the reasons why network databases were abandoned
in favour of relational (SQL) databases.
Fredrik Bertilsson
http://frebe.php0h.com
.
- Follow-Ups:
- Re: Persistence
- From: Dmitry Shuklin
- Re: Persistence
- References:
- Persistence
- From: frebe73
- Re: Persistence
- From: Dmitry Shuklin
- Re: Persistence
- From: frebe73
- Re: Persistence
- From: Dmitry Shuklin
- Persistence
- Prev by Date: Re: Observer pattern limitations
- Next by Date: Re: Biz Modeling - let's try again
- Previous by thread: Re: Persistence
- Next by thread: Re: Persistence
- Index(es):
Relevant Pages
|