On 18/09/2004 22:59 Jeffrey Tenny wrote:
> [snip]
> I'm still running against 7.3.x, but if the above two paragraphs
> are true that's very problematic for me if I'm going to upgrade.
> My app also runs 24/7 and uses serializable transactions in pooled
> connections.
>
> Are you saying that I will see stale database state at the logical
> "start" of my transaction from a pooled connection?
>
> That's a showstopper for sure. If I'm confused please enlighten me.
> I've been holding off on upgrading because of the amount activity on this
> list about 7.4+ systems.
>
> This is the first thing that's been sufficiently integrity threatening
> that it prompted me to de-lurk. I need data as of when the transaction
> starts, not when the database last committed a transaction via that
> connection.
Our web app deploys on 7.3 and 7.4. There's no problem with the 7.3
db/driver but you could be bitten using the 7.4 driver. My solution is to
always setAutoCommit(true) before returning the connection to the pool.
HTH
--
Paul Thomas
+------------------------------+-------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for Business |
| Computer Consultants | http://www.thomas-micro-systems-ltd.co.uk |
+------------------------------+-------------------------------------------+
