Re: Persistence
- From: frebe73@xxxxxxxxx
- Date: 14 Jul 2006 08:14:23 -0700
Object models aren't supposed to capture all the
relationships among the information components, only those that are
relevant to the business context of a particular application.
I don't know if "supposed" is the correct word. I think "isn't able to"
is more correct.
Are you here only for bashing, or are seriously interested in OO ?
I use OO every day for a living.
If you don't need anything but persistence, persisting objects directly
would make sense. But mostly you really need the other features
provided by a RDBMS.
I don't get you here... Do you mean that every OO program absolutely
needs a SQL DBMS ?
Absolutely not, did you notice the word "mostly"? There are also many
programs that don't need persistence, and there are programs that need
other kind of persistence than a SQL DBMS can offer.
Fredrik Bertilsson
http://frebe.php0h.com
.
- Follow-Ups:
- Re: Persistence
- From: Bruno Desthuilliers
- Re: Persistence
- References:
- Persistence
- From: frebe73
- Re: Persistence
- From: Daniel Parker
- Re: Persistence
- From: frebe73
- Re: Persistence
- From: bruno de chez modulix en face
- Persistence
- Prev by Date: Re: Design problem with inheritance
- Next by Date: Re: Design problem with inheritance
- Previous by thread: Re: Persistence
- Next by thread: Re: Persistence
- Index(es):