Another reason to handle it in the database:
If you do it in your app, you've got to do it in every app that accesses
the database. If you do it in the database, it's a one-shot deal.
Always try to operate as close to the data as possible.
-David
On Thu, 22 Feb 2001 16:50:59 -0500 "Hal Helms"
<[EMAIL PROTECTED]> writes:
> Cyrill, I think everyone will advise you to always prefer the
> database functions--especially when dealing with referential integrity.
> Databases have had almost 40 years with some of the best minds applied
> to them. They're stable, elegant and fast.
>
> Hal Helms
>
> -----Original Message-----
> From: Cyrill Vatomsky [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 22, 2001 2:49 PM
> To: CF-Talk
> Subject: Referential Integrity
>
> HI,
>
> My question is whether it is better to write CF routines to
> maintain referential integrity of the database or to set up
> "Preserve Referential Integrity" rules in MS Access and
> try to catch errors?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
