Re: Terminology for composite attributes

dawn wrote:
>
> Yes, this is something I do regularly, with little effort, as do all
> those working with XML or older models.

Sounds like you're talking about the pick/universe/unidata/whatever model.

> > considering that it causes two new relations.
>
> in your logical model of choice, but not in mine. Date's new def of
> 1NF might also lead one to model multivalues in the same relation,
but
> most sql-dbms implementations would discourage it due to lack of
> support in odbc/sql-92, for example

If the "model" you speak of doesn't cause two new relations, there's something wrong.

And what the heck is Chris Date's "new" definition of 1NF? I haven't seen it, or anything from him, that would promote multivalued attributes. The very concept is anti-normalization and should make every DB professional nauseous. Received on Fri Apr 01 2005 - 16:25:33 CEST