Re: Persistence



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

.



Relevant Pages

  • Re: OOP style
    ... Component classes have all their main logic in a Custom base class ... database access unit if they didn't already start with a full DB layer; ... My latest application started with an extensively designed object model ... Typing in the implementation of the database interface is ...
    (comp.lang.pascal.delphi.misc)
  • Re: Form quit, bypasses cancel in textboxes BeforUpdate
    ... Just about every pc database product. ... would love to find that shortcut, and the instant pain killer. ... >> have to resort to using the forms before update event). ... there is lots of reasons for the above: ...
    (microsoft.public.access.formscoding)
  • Re: Local Table vs. Class for Public Variables with simple types
    ... properties and tables are better because they are carried with the database. ... Dim rs1 As ADODB.Recordset ... Dim stm As ADODB.Stream ... >> I you are persisting values which can be altered by the user (i.e. user ...
    (comp.databases.ms-access)
  • Re: OOP - a question about database access
    ... >> You can design your app and object model as if the database didn't ... What's wrong with improving the design table by table, ...
    (comp.object)
  • Re: OOP - a question about database access
    ... >> Your concern should be the object model, which you don't even hit on. ... to reinvent database features from scratch, ... > The persistence of said object is controlled by the object, ... I've seen systems that load entire object trees ...
    (comp.object)