Re: Persistence

Hi,

4. Something else.

A SQL database should NOT be used for object persistense at all.
Because OODB can handle transactions, integrity, objective JOINs,
objective VIEWs, declarative queries, indexes and e.t.c.

WBR,
Dmitry

.

Relevant Pages

  • Re: Observer pattern limitations
    ... that's exactly what you must do or you won't have integrity. ... transactions cannot enforce integrity. ... class Mandelbrot: public Window ... The two mutable members represent dependents. ...
    (comp.object)
  • Re: Observer pattern limitations
    ... that's exactly what you must do or you won't have integrity. ... If transactions are simple and fine grained it is generally quite ... class Mandelbrot: public Window ... The two mutable members represent dependents. ...
    (comp.object)
  • Re: Observer pattern limitations
    ... subject to a reasonable definition of integrity. ... Transactions are defined at the application level - this tells ... The separation between independents / dependents is easy to understand. ... For the same reason distributed and concurrent programs ...
    (comp.object)
  • Re: Observer pattern limitations
    ... subject to a reasonable definition of integrity. ... When you claim "transactions cannot enforce integrity" do you mean ... The separation between independents / dependents is easy to understand. ... we're discussing here: Dependency graphs. ...
    (comp.object)
  • Re: Where do business rules belong... OCP and SPs
    ... Responding to Levin... ... > modify my account balance, I want to save the original account ... I could argue that the reason one wants this is a form of data integrity ... >>The other problem is generating transactions against the DB. ...
    (comp.object)