On Jun 21, 2013, at 4:42 PM, graf <[email protected]> wrote: > > > Any way the problem is not related to singleton. As far as I understand the > Session creates the transaction after first commit/rollback/close and this > locks the Oldest transaction and after a while slow down the db speed. > "sweep" don't help in this situation. I can't restart my application to > remove lock because it is 24/7.
I dont understand what an "Oldest transaction" or a "sweep" is. A Session does only one transaction at a time. If your app uses more than one transaction at a time, you need more than one session, one per concurrent transaction to be exact. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
