>>>> articleID - articleRelations 1 3,14,33 2 3,4,12 3 11,1,2 4 7,8,5 5 7,8 <<<<< The problem with this, is 1) that you're still storing a list, and 2) you will have either redundant or inconsistent information. Meaning, article 1 says it is related to 3, and 3 says it is related to 1. Depending on your business rules, this could be redundant. Also, when you delete article 3, you'll need to go through every list and remove all 3's from all the lists.
>>>>> OR... would there be a separate row for every relation. So if my articleID was 4, it would search all records below and pull out relationsIDs 1,2 and 5 and display all the articleRelations accept for the number 4's? >>>>> RelationID - articleRelations 1 2,4 2 3,4 3 11,2 4 7,5 5 7,4 <<<<< This is more on the right track. Though rather than "2,4" being a comma-separated-pair, it should be two seperate fields. Now when you delete article 3, you can easily do a query that deletes all the relations relating article 3 to another article. This approach is also much more scalable. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net http://www.cfhosting.net Message: http://www.houseoffusion.com/lists.cfm/link=i:4:184396 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
