Re: Multiplicity, Change and MV
From: Bob Badour <bbadour_at_pei.sympatico.ca>
Date: Thu, 13 Apr 2006 20:42:34 GMT
Message-ID: <_Iy%f.59462$VV4.1097654_at_ursa-nb00s0.nbnet.nb.ca>
Date: Thu, 13 Apr 2006 20:42:34 GMT
Message-ID: <_Iy%f.59462$VV4.1097654_at_ursa-nb00s0.nbnet.nb.ca>
Neo wrote:
> In RM, the proper method of allowing an attribute to have multiple
> values is to have a separate table.
You are an ignorant who doesn't know what he is talking about.
> If the separate table is not
> included in the initial schema, adding it later usually requires schema
> changes, data migration and script/query/code updates.
Your statement is a tautology. "Changing the schema requires schema changes." Well, duh.
> MV allows an attribute to have multiple values without schema changes.
Not if the attribute was originally constrained to single values. Changing from a single value to multiple values is a schema change. Duh! Received on Thu Apr 13 2006 - 22:42:34 CEST