In a performance tips seminar that Ben Forta gave, he said that referential
integrity was best left in the database rather than coding it yourself.
Then use CF to catch the errors.
Having said that, for deletes, I still check to see if children exist!!!
> From: "Cyrill Vatomsky" <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Thu, 22 Feb 2001 11:48:57 -0800
> To: CF-Talk <[EMAIL PROTECTED]>
> 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
