Hello,

When developing my OLTP system, I'm putting great care to avoid long running
transactions.

However, I might have to give access to other developpers for different
projects. Those developpers are not used to IB/FB and the "Long running
transaction" issue.
I can "advise" them not to issue long running tx, but I can't "force" them
to do so while coding or even using an admin tool to look at data.

Is there something I can do at the DB level to prevent the problem ?

Thanks for your help.

--
Jerome