On 9/11/18 5:41 AM, Thomas Fox wrote:
> Another idea: Not TorqueConnectionImpl.rollback() and 
> TorqueConnectionImpl.commit() set the flag to not rollback on close(), but 
> TransactionImpl.rollback() and TransactionImpl.commit(). So in this case the 
> user can commit() and rollback() on the connection to his heart's content, 
> but only a call on  TorqueConnectionImpl.commit()/.rollback()(which closes 
> the connection anyway) changes the connection close behavior. What do you 
> think?

That sounds reasonable. The context is well-defined and the behavior can
be documented easily. I'll give it a try and see how it goes.

Bye, Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h...@db.apache.org

Reply via email to