Re: Duplicate Record Monitoring

There's a difference between and error and an exception too. An error might
be 'the disk drive failed', while an exception may a record lock or a
trigger failed. You probably want to handle the exceptions, and maybe blow
up on the errors.

On 2/27/06, Booth Martin <booth@xxxxxxxxxxxx> wrote:
>
> Whatever the error, the wanted event did not complete successfully.  How
> one deals with that is a design decision to be made by management of
> course.  I can see a case being made for "we'll trap for, and handle,
> every error possible."  I can also see "Some errors happen so seldom it
> is cheaper to fix them as they occur than it is to program for every
> possible error.  Take the low road."
>
>
>
> rob@xxxxxxxxx wrote:
> > I disagree with "assuming" error is because of a duplicate error.  The
> > error could be:
> > - trigger threw an error because it didn't like it.
> > - referential constraint violation
> > - any of the numerous other errors possible.
> > Look at the list of error codes possible.
> >
> > Rob Berendt
>
> --
> -----------------------------------
> Booth Martin
> http://martinvt.com
> -----------------------------------
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>