It's probably best to do both: Check in CF for things that are most likely
to break, but always build your referential integrity into the DB in case
something gets past your code (and then catch & handle, of course!) When
you're dealing with forms, you can also add client-side validation.
Not that I've always operated this way.... ;(
Eric
-----Original Message-----
From: Cyrill Vatomsky [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 22, 2001 11:49 AM
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 (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/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
