Re: SQL for Modeling Generalization Hierarchies

<ctcgag_at_hotmail.com> wrote in message news:20040602125733.647$6f_at_newsreader.com...
> robertbrown1971_at_yahoo.com (Robert Brown) wrote:
> If the main or only goal is to satisfy nosy Nellies, I would either go
> with a auxilliary table of name-value pairs (and another auxilliary table
> with listing allowed or suggested attributes for each job type, or just
> do away with all those tables and make a "free text" clob column on the
> employee table (or call it XML rather than free text, if that type of
> things turns you on).

Yeah, right, make it XML, and watch your performance going down the drain.

If you want "flexible" structure, use auxilliary name-value table. Convert it into nested collection if you have object fever. Received on Wed Jun 02 2004 - 19:25:01 CEST