Re: Mixing OO and DB

Patrick May wrote:
> Marshall <marshall.spight_at_gmail.com> writes:

> >> The general ledger schema is not the schema for the content
> >> management application.
> >
> > Agreed. The general ledger schema and the general ledger
> > application cannot be decoupled.
>
> Now you're just being a twit. It is very straightforward to
> decouple application logic from the mechanism used to maintain the
> persistent state of that system,

Here you seem to be using the DB as *only* a dumb filing system. It can also be the "logic" part of your sentence. Just because YOU use it only as a dumb filing system does not mean that is the only way to use it.

If you are in a domain that cannot take advantage of the features of RDBMS, such as in intensive unstructured graph traversal, then such may be the case. But, that is not a universal statement since many domains are not like that. (Or maybe you never figured out how to structure it better.)

And, anything is probably separatable with enough levels of indirection (interfaces on top of interfaces). But managing levels of indirection can be expensive in itself. Indirection is not free. It is always possible, but not always "good".

> even if that mechanism is a
> relational database and corresponding schema. Your attempt to create
> some kind of strawman and score rhetorical points is transparent and
> ridiculous.
>
> Sincerely,
>
> Patrick
>

-T- Received on Sat Mar 01 2008 - 19:15:34 CET