Re: Data Constraints AND Application Constraints

On Thu, 17 Mar 2005 21:50:31 +0000 (UTC) in comp.databases.theory, hause011_at_tc.umn.edu (Steven Hauser) wrote:

>Many times a database is a data repository for more than one application.
>I usually follow this rule:
>
>- a constraint that is true for all should be in the database, otherwise
> it is implemented in the application.

I've found stored procs/packages useful to allow applications to do complex multi-column consistency checks (and get meaningful error messages) consistently, and avoid the overhead of adding those complex (and often somewhat application dependent) check constraints to the table.

-- 
Thanks. Take care, Brian Inglis 	Calgary, Alberta, Canada

Brian.Inglis_at_CSi.com 	(Brian[dot]Inglis{at}SystematicSW[dot]ab[dot]ca)
    fake address		use address above to reply