🚀 go-pugleaf

Isaac,

> I am facing a strange behavior when raising an exception from inside a
> stored procedure
>
> I have three triggers that call one stored proc after insert , after
> update and after delete
>
> I check in the stored proc if a bal is < 0 if so then I raise an exception
>
> I also had to do the same check in my app so I can make sure bal is
> never < 0, so the result was one time the store exception is fired
> immediately after insert a record but all other tries never raised again
> and only my application check exception is the one that always raised
> although I made the check in a save button after the user inserted as
> many item as he want
>
> Please advice why the stored exception did not raised first !!

Hard to tell if you don't show us anything.


-- 
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com