> Jochem wrote, > > Do you consider data integrity fancy stuff? If so, we should > > probably agree to disagree. > > Indeed. I've always preferred to handle cascading > deletes/referential integrity in the application. I realize > this is anathema to some, and strictly speaking a performance > detriment, but long ago I decided I wanted to use the db > solely as a container that follows the express instructions I > give it. Only. Perhaps a now-antiquated view that sprang > from better error handling at the application level, back in > the day. > > If an operation violates referential interity, I should have > done a better job writing the app.
I think this is the scariest thing I've read in a while. There's a reason that we don't use things like xBase any more. Yes, I'd agree that this is anathema to me at least. Declarative referential integrity prevents errors in your application from becoming errors in your data. For any non-trivial application which will be used and modified over time, it's a big deal. For any case where the same database might be used by multiple applications, it's essential. What happens when someone modifies the code you wrote, without understanding something or other within that code? Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/lists.cfm?link=t:4 Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
