> The real benefit is with data integrity checking, where related table > contents may cascade adds or deletes where needed for complex > relationship maintenance. .... Since managing the intregity of the > data is part of the initial design phase, this code is 'carved in stone' > as if it were stone, and becomes part of the db definition.
true all the more reason to seek out the declarative referential integrity that the database offers and use that instead of stored procs of course, if the database doesn't have declarative RI, you're stuck > Allowing applications people to change (as if often required as user > requirements change) the stored procs in lieu of examining there own > sql logic may a mistake. indeed rudy http://rudy.ca/ - 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)
