On Tue, 13 Nov 2007, Heikki Linnakangas wrote:
> Oh, I had forgotten about that. The difference is the close() between the
> getConnection()s.
>
> I started having second doubts about that case you posted in June, so I
> tested what Derby does if you call getConnection() twice, without a close in
> between. You get an error ("Cannot close a connection while a global
> transaction is still active."), so at least they consider it incorrect as
> well.
I'm not super happy that explicit close vs implicit close has different
transactional behavior, but people really shouldn't be writing code like
this, so I've applied your patch to 8.1, 8.2 and HEAD.
Kris Jurka
