This is only my opinion... it all depends on your take.
Sometimes it is much easier to put a constraint on your database rather than
have to check for the constraint violation a million of times in your CF
code. However, this forces you to use try/catch blocks, which you really
should be using in the first place.
>From my experience, I've found that trying to catch constraint violations
that have not been set at the database level to be messy and sometimes
inefficient (involving other queries, etc.).
----- Original Message -----
From: "Cyrill Vatomsky" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, February 22, 2001 12:48 PM
Subject: Referential Integrity
> HI,
>
> My question is whether it is better to write CF routines to maintain
> referential integrity of the database (say, hiding a delete button or
> checkbox if child records exist in another table) or to set up "Preserve
> Referential Integrity" rules in MS access and try to catch errors?
>
> Which leads me to a theoretical question: should I rely more on built-in
> database functions or on CF?
>
> Thanks,
>
> Cyrill
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
