Kenneth Downs wrote:
> Troels Arvin wrote:
>
> > On Mon, 04 Oct 2004 18:40:56 -0400, Kenneth Downs wrote:
> >
> >> But if you use a trigger, you can do
tell-me-everything-I-did-wrong.
> >
> > I don't quite understand this: How can the trigger overcome
fail-on-first
> > error handling?
>
> The trigger records each error that it finds, but instead of stopping
it
> keeps going. So the more you have, the more that are recorded. It
> actually never raises an error in the strict sense, you might say it
always
> "returns true".
Sorry to keep bugging you, but what do you mean by this? If the
trigger "returns true", then who is responsible for aborting the
triggering statement - the application? In that case, you don't have
assured integrity at all: it is optional.
Received on Wed Oct 06 2004 - 10:22:21 CDT
