> As for the ORs I'm a little lost on that too. Perhaps cases for > readability? Or would they be ORs in a select where a = a or > b = b statement that you're referring to Rudy?
yes, i was referring to conditions in the WHERE clause combined with ORs i've been data modelling for about twenty-five years (actually, an equivalent of only about ten -- see http://rudy.ca/20020514.cfm) and i have always been very, very careful not to store lists inside a column, because that violates first normal form still, when you have (custom) tags that can compare lists, i must say that the case against lists is weakened somewhat if you can guarantee that the individual entries inside the list will never need to be joined to some other table, then i guess it's okay nevertheless, i would still design the intersection table, just to be safe rudy - You are subscribed to the CFUGToronto CFTALK ListSRV. This message has been posted by: "rudy" <[EMAIL PROTECTED]> To Unsubscribe, Please Visit and Login to http://www.CFUGToronto.org/ Manager: Kevin Towes ([EMAIL PROTECTED]) http://www.CFUGToronto.org/ This System has been donated by Infopreneur, Inc. (http://www.infopreneur.net)
