Re: Error Handling Coming Out of a Trigger
- From: "Kevin Frevert" <kevin@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 20 Jun 2007 15:52:49 -0500
"Brian Hollister" <bhollisterATfuturaintlDOTcom> wrote in message
news:46798b8f@xxxxxxxxxxxxxxxxxxxxxxxxx
Try raising the exception, then rolling back the transaction.
That's weird. I swear I've done that and it (raising an exception from
inside a trigger) worked just fine. I'll dig around and see what I can
find.
That did not work, but thank you though. What I have decided to do is to
separate the business rule enforcement from the database and try to allow
the database to just maintain data integrity through keys and constraints
and not forced logic, as much as possible. Kevin, I got this idea from a
conversation you and two other guys were having. I googled it up in
groups...
Did you go this way as well? If so, are you happier with it?
In some/most cases yes and so far so good. From what I see you are needing
to do, a trigger might be the ideal solution and should be working just as
you expect.
For a little nostalgia, do you have a link of that conversation?
krf
.
- Follow-Ups:
- Re: Error Handling Coming Out of a Trigger
- From: Brian Hollister
- Re: Error Handling Coming Out of a Trigger
- References:
- Error Handling Coming Out of a Trigger
- From: Brian Hollister
- Re: Error Handling Coming Out of a Trigger
- From: Kevin Frevert
- Re: Error Handling Coming Out of a Trigger
- From: Brian Hollister
- Error Handling Coming Out of a Trigger
- Prev by Date: Re: Error Handling Coming Out of a Trigger
- Next by Date: Re: Error Handling Coming Out of a Trigger
- Previous by thread: Re: Error Handling Coming Out of a Trigger
- Next by thread: Re: Error Handling Coming Out of a Trigger
- Index(es):
Relevant Pages
|