Re: set datatype
Breaking the atomicity rule with a representation like "1;3;4" is pretty much guaranteed to create havoc for data integrity, queries and maintenance. Even if you manage to prevail over these difficulties, those who follow you will curse you for your choice.
If by "products can have multiple values" you mean product.connectortype can have multiple values for a given product--eg product P can have connectortype BNC, SMA, both, or something else--then the rules of basic normalisation require connectortype to be broken out to its own table, with one row for each unique connectortype. And if, as you imply, multiple products can have the same connectortype--eg products X and V both have connectortype ABC--then the product-connectortype relationship is many-many, and you need three tables to model it: product(pid, etc), connectortype(cid, etc), and product_connectortype_bridge(pid,cid) which will acquire one row for each unique product-connectortype pairing.
Edited 3 time(s). Last edit at 04/05/2007 12:08PM by Peter Brawley.
Subject
Written By
Posted
Re: set datatype
April 05, 2007 12:05PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.