🚀 go-pugleaf

> > If the exception (in the database) causes the client app to rollback
> > it's changes, the data won't be in the table either.
>
> Good point. The rollback must be done after you get any information you
> need from the database.

There's more to it, actually. Stored Procedure/Trigger code has implicit
savepoints that are rolled back as soon as an exception occurs in the
block that has the exception handling. I've researched some of this for
a presentation I did last year at the Firebird Conference. It's quite easy
to get confused here.

It also matters if you're calling another procedure or writing code in-line.

So, whenever you catch an exception, you need to log your message
into another table and re-raise your exception from a different
begin..end block with it's own exception handler.

I think ... ;-)

Either way, this requires some careful testing :)


-- 
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