> I think we've been through this discussion quite a few times. > In theory, I mean PURE theory, you're absolutely right. > However, a relational database is not for storing exclusively > relational data. > In some accasions, one needs a list of a small number of > items, with no relation to anything in the database, and the > relation, if ever there exists one, is handled in the soft, > not in the database.
What does this buy you, that you couldn't do just as easily without violating the theory? The only example I can think of is a bitmap field, but that's obviously not what you're using. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:235686 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
