Re: Storing objects in a RDBMS? - OT

Pounding a square peg into a round hole is actually a useful thing in some contexts.

For example, when I was a young lad my grandfather and I were sitting in his kitchen. There was an antique floor standing cupboard in the room. He pointed out that while the IQ tests where you have to put the matching shapes into the matching hole always graded you higher if you matched them correctly that was not the way to make furniture. Furniture made in that manner falls apart quickly. He pointed out that the antique floor standing cupboard was in fact made with round holes and octagonal pegs and it had lasted 200 years so far...
Jim

"Pablo Sanchez" <pablo_at_dev.null> wrote in message news:l05r8.1005$c02.102089_at_news.uswest.net...
>
> "damorgan" <damorgan_at_exesolutions.com> wrote in message
> news:3CACC064.9D7D0B7D_at_exesolutions.com...
> > You wrote:
> > "I try to read and answer posts based on what the posterintended."
>
> Actually, I wrote: ".... what the poster intended." :)
>
> > And I absolutely agree. But a posting to an RDBMS forum, whether
> Oracle or
> > Sybase or both leads me to think of storing objects inside the
> database
> > ... not C++ concepts of encapsulation, inheritance, and
> polymorphism.
>
> Mebbe it's because I happen to be working on an application that is
> heavily into OO and the OO has creeped into the RDBMS. All the issues
> with pounding a round peg into a square whole exist too.
>
> > What the poster indended ... is implicit in where the poster chooses
> to
> > post.
>
> I believe this is "you like strawberry and I like vanilla"
> --
> Pablo Sanchez, High-Performance Database Engineering
> mailto:pablo_at_hpdbe.com
> Available for short-term and long-term contracts
>
>
Received on Thu Apr 04 2002 - 21:52:20 CST