>> Its my understanding from reading the prior threads on this that
>> somewhere
>> after jdbc 213 they moved the initial BEGIN to the first SQL Execute
>> rather
>> than immediately upon Connection.
>>
>
> This change only occured in the 8.0 development branch, and not on the 7.4
> branch. I produced a patch and then current versions of the 7.4 jar files
> for people to try this out on their 7.4 servers, but no one ever got back
> to me about it, ...
I'm amazed... Sounds like noone is doing any serious work with JDBC, or
only has short lived 'applet' kind of applications where long persistance
connections aren't an issue.
I can think of a bunch of scenarios where this would cause problems...
* An service app that opens several connections for various threads,
and one or another of them goes idle for a long time ... No vacuuming
during this state.
* Thread has been idle for awhile, then goes to do a SELECT and it will
only see data that was committed prior to this threads last COMMIT.
etc etc etc.
