Re: Modeling question...

From: JOG <jog_at_cs.nott.ac.uk>
Date: Fri, 25 Jul 2008 07:19:10 -0700 (PDT)
Message-ID: <2bb55208-f6ae-4229-93c7-d1894e896e89@v26g2000prm.googlegroups.com>


On Jul 25, 3:05 pm, Volker Hetzer <firstname.lastn..._at_ieee.org> wrote:
> Bob Badour schrieb:
>
> >>> Ooooh! Reinventing EAV with levels...
>
> >> Possibly. I had a look at
> >>http://ycmi.med.yale.edu/nadkarni/eav_CR_contents.htmand didn't find
> >> anything exciting.
> >> All my attributes (key value pairs) are (for the purpose of this
> >> discussion) strings, so the Data tables hierarchy ends with
> >> EAV_Objects in the first image of that link.
> >> My problem is that, that I haveTest three different "Objects_1"
> >> tables and I'd like to avoid having to replicate the EAV_Objects-Table
> >> for each "Objects_1"-Table.
> >> OTOH, I could have the "level" entities all be children of an id table
> >> and
> >> put the key value pairs into a child of that table. I need to try this
> >> out.
>
> >> Thanks for providing the pointer!
> >> Volker
>
> > Just to be clear, I was more than offering a pointer. I was also
> > ridiculing the idea of EAV.
>
> I got that. :-)
> But "we want to be able to create and delete attributes" is a customer
> requirement. I think it's different from "I am too lazy to do a proper data
> model". There are plenty of "normal" attributes left to model ERD like.
>
> Lots of Greetings!
> Volker
> --
> For email replies, please substitute the obvious.

What's wrong with drop/add column? Received on Fri Jul 25 2008 - 09:19:10 CDT

Original text of this message