On 2002.12.13 09:47:08 -0500 Carlos Guzmán Álvarez wrote:

>
> Hello:
>
> > I don't think so. Can you be more specific about what you are
> proposing?
> >
> > Once we try to rollback once, there is nothing more we can do with the
> > transaction, ever, no matter if we got an exception or not. But if we
> try
> > to commit and fail, there are several possibilities:
> >
> > connection has failed, we can't do anything more.
> >
> > Work done at commit time (DDL) failed, we should roll back the
> transaction
> > (maybe)
>
> Correct, i´m wrong :) sorry, and if you make a rollback retaining ??

Hmmm, Well, the purpose of the changes to rollback were so you could call
rollback on the engine if there is any evidence a transaction was started,
and to mark the transaction over no matter what happens. This is only
required when you are making a last-ditch attempt to clean up after some
kind of serious problem and are about to discard the connection. I don't
think you would ever call rollback retaining and expect meaningful results
in such a situation, so I think the current implementation is ok. I'd
really appreciate you looking at this to see if you agree.

Thanks
david jencks

>
>
> Best regards
> Carlos Guzmán Álvarez
> Vigo-Spain
>
>
>
> To unsubscribe from this group, send an email to:
> Firebird-Java-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
>