On Jun 17, 11:26 am, Martijn Faassen <[EMAIL PROTECTED]> wrote:
>
> We wouldn't recreate the engine on each request, just each time a
> session is constructed for a new thread (or actually new
> application/thread combination). (that is, ScopedSession would get a
> session_factory that did this).
yeah that also kind of defeats the connection pool's purpose as it's
intended to handle all connections for a particular database across
threads. Having a single point of pooling for a certain database has
the advantage that you can tune the total number of connections at a
single configuration point, and also that a database restart can be
detected just once, resulting in a bounce of the entire pool (this is
a distinct advantage of using a pool over a non-pooled approach).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
