Data Constraints AND Application Constraints
From: FrankHamersley <FrankHamersleyZat_at_hotmail.com>
Date: Thu, 17 Mar 2005 11:19:18 GMT
Message-ID: <WId_d.1485$C7.1054_at_news-server.bigpond.net.au>
Now that the "vs" thread has subsided I got to wondering how many practitioners of database constraints as a key element of schema designs consider there remains a need for further constraint (related) checking in the application code itself?
Date: Thu, 17 Mar 2005 11:19:18 GMT
Message-ID: <WId_d.1485$C7.1054_at_news-server.bigpond.net.au>
Now that the "vs" thread has subsided I got to wondering how many practitioners of database constraints as a key element of schema designs consider there remains a need for further constraint (related) checking in the application code itself?
I will declare in advance my predilection is that no one design layer trusts the layers above or below it. I accept the overheads it incurs and often find this multiple sieving approach often traps inadvertent design or rendition faults in the layers above or below. These are not (often) technical integrity failures, more likely business rule oversights, but when left in place they do occasionally trap "real weird sh:t" - especially the intermittent bugs that almost always combine with Murphy's Law for maximum impact.
What is the consensus/spectrum of views?
Cheers, Frank. Received on Thu Mar 17 2005 - 12:19:18 CET