#19 The alpha and the omega

[Tony Ennis]

I'd like to see a mechanism to help me manage database
transactions.

Before a CallBack.execute(), it would be nice if an
application method was called that started the
transaction. After the execute completed, another
application method would be invoked which would allow
me to commit or rollback.

Another idea is a subclass of Callback which would
allow this

MyCallback extends Callback
{
...yadda...
public Object execute(Object whatever) {
try
{
beginTransaction();
super.execute(whatever);
commitTransaction();
}
finally
{
rollbackTransaction();
}
}

I kinda like this since the rollback is ironclad.

Now that I stop to think about this, I can do this very
thing in my application, and not really have to change
Lakeshore at all. I'll post this anyway since it is a
nice survival technique.

[Tony Ennis]

Logged In: YES
user_id=1093826

Ok, CallBack is an Interface so the solution is a little
different.