Re: SE Trigger/Exception problem

Clifford Frisby: >I'd always assumed that a triggers was a watertight basis for preventing >non-privileged users of a database from inserting rows which result in a >semantic inconsistency. I'm now trying to 're-educate' myself on this >view, having considered Art's reply! Ah, here's where my tunnel vision reared its ugly head in my original response: I tend to code such beasts as pre-insert logic. Unless some new and exciting technology has arrived, I believe the only way to render a database "watertight" is to revoke all access from the tables and force the non-privileged user to execute stored procedures. That way the wrapper procedure performs all the requisite business logic prior to modifying data. -mka Michael Ackerbauer SP System Test