It should be wherever your application can recover. The method that calls the DB is probably not going to know how to deal with the error in any meaningful way. The "right" method will probably be the same method that handles any other validation errors (the ones that are checked pre-INSERT), which is likely several steps above your actual database call.
cheers, barneyb On Thu, 4 Nov 2004 11:28:30 -0600, Dawson, Michael <[EMAIL PROTECTED]> wrote: > At what level, then, should your code check for the database error? > Should it be within the actual method that performs the database call; > should it be in the code that calls the method? > > What is your plan? > > Thanks > M!ke > > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/blog/ I currently have 0 GMail invites for the taking ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
