- trigger can't stop transaction since it just give you a chance
to do some more stuff.
- do this could work:(server-end solution)
- write a package. put a varicables:
StopFlag -- flag to tell you want stop transaction
TheKey -- the key field type of your table to have
- the key value of the updated row
- write a row level trigger like you had. whenever your don't want
the trasaction, set the package flag and store the key.
- wirte a after update statement level triger. if the flag set,
delete
the row.
this method is same as dealing with mutation table.
- client side solution.
as you did raise the exception. if the client software can catch it,
issue a rollback statement.
Moxie
Moxie J. Zhang @ Deloitte & Touche Consulting Group, DRT System
zmoxie_at_dttus.com
Moxie.J.Zhang_at_worldnet.att.com, zmoxie_at_aol.com
Received on Wed May 28 1997 - 00:00:00 CDT
