Re: Object-relational impedence

From: JOG <>
Date: Mon, 3 Mar 2008 11:21:37 -0800 (PST)
Message-ID: <>

On Mar 3, 6:54 pm, Bob Badour <> wrote:
> topmind wrote:
> > JOG wrote:
> >>On Mar 3, 2:07 pm, Thomas Gagne <> wrote:
> >>>All attempts by applications to access a DB's tables and columns
> >>>directly violates design principles that guard against close-coupling.
> >>>This is a basic design tenet for OO. Violating it when jumping from OO
> >>>to RDB is, I think, the source of problem that are collectively and
> >>>popularly referred to as the object-relational impedance mismatch.
> >>I wondered if we might be able to come up with some agreement on what
> >>object-relational impedence mismatch actually means. I always thought
> >>the mismatch was centred on the issue that a single object != single
> >>tuple, but it appears there may be more to it than that.
> >>I was hoping perhaps people might be able to offer perspectives on the
> >>issues that they have encountered. One thing I would like to avoid
> >>(outside of almost flames of course), is the notion that database
> >>technology is merely a persistence layer (do people still actually
> >>think that?) - I wonder if the 'mismatch' stems from such a
> >>perspective.
> > This came up in a nearby message. I borrowed the following text from
> > wikipedia:
> The text had too many blatant errors to start enumerating them all. The
> problem with wikipedia is any ignorant fool can just start typing
> nonsense. Even when one follows the requirements for references to
> primary sources, the quality of the end product can vary over many
> orders of magnitude.

And yet wikipedia entries are often remarkably half-decent. However not in this case - the entry is a convloluted mess, and actually instigated my question.(I often wonder if it would not be better if opposing views on wikipedia could be treated as separate articles rather than the standard mish mash). Received on Mon Mar 03 2008 - 20:21:37 CET

Original text of this message