Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)

From: x <>
Date: Tue, 13 Jun 2006 17:14:40 +0300
Message-ID: <e6mh1i$91k$>

"Robert Martin" <> wrote in message news:2006061313322384492-unclebob_at_objectmentorcom...
> On 2006-06-01 22:37:48 +0200, "erk" <> said:
> > Robert Martin wrote:
> >> The optimum structure for each application is local to it's particular
> >> function.
> >
> > While I agree that data and behavior will never be unified, you lost me
> > here. Maybe I'm misunderstanding what you mean by "optimum structures"
> > how they relate to the enterprise data?

> Imagine a circuit emulation application. It reads the circuit from an
> RDB in the form of many interlinked rows across many tables.

Why "it reads the form of ..." ?

> separate queries are needed because each row contains the keys of other
> rows to create a graph of components and connections.

> Once we have read the whole structure in, we have to emulate it. This
> requires a tranformation of the data into matrices so that we can solve
> the circuit equations.

And you will transform those matrices back into graphs so you can solve the equations. :-)

> Next, we'd like to draw a graph of the voltage on a set of signals over
> time. This requires yet another data structure related to the circuit.
> (One that will likely never be placed in the DB BTW).

Why "requires" ? Received on Tue Jun 13 2006 - 16:14:40 CEST

Original text of this message