At 11:16 AM 8/30/01 -0400, Clark C . Evans wrote:
>I have a minor problem here... in the DB pool, when
>a connection is returned it may have one or more "active"
>transactions (esp when only used for selecting information).
>These transactions take up extra overhead in the database.
>Anyway... I'm too hammered with getting a product out
>that I don't have time to investigate... but I will
>invesigate and submit a patch in a few weeks when I
>have more time (beacuse I can't ship with this behavior).
>Either I can "bullet proof" all of my code to clean up
>the transaction; or we could fix DbPool to do this for us...
>I think the latter is the better "lazy-mans" solution.
>Thoughts? Also... I need some way where the number of
>connections will decrease to zero over time... say if
>the connection isn't used for 2-5 minutes.
The part about making DbPool automatically clean up transactions sounds
database-specific to me. Which DB are you using? Perhaps this belongs in
a subclass, not in the main DbPool?
On the other hand, the part about decreasing the number of connections down
to zero over time sounds generally useful for any database. I wouldn't
mind seeing that in the main DbPool.
- Geoff Talvola