On Sat, Dec 17, 2011 at 6:53 PM, Chris Angelico <rosuav@gmail.com> wrote:
> Some of my code involves transactions which will not have significant
> effect on the database. It might be a read-only transaction (possibly
> declared as one, but possibly not), or perhaps a completely empty
> transaction - I have a framework that will always open a transaction,
> then call on other code, and then complete the transaction at the
> bottom.
>
> In these instances, is it better to commit or to rollback? Are there
> performance penalties to either option?
I do not believe there are performance penalties for either. All
commit or rollback does is determine visibility of changes made.
Best Wishes,
Chris Travers