Hi,
I use "session.bind.dispose()"
León Domingo
ender
LA FACTORÍA DE SOFTWARE
Av. Cerro del Águila 7, 2ª planta - S23
28703 S.S. de los Reyes
Madrid
tlf. y fax: 902 01 44 01
www.ender.es
--
You received this message because you are subscribed to the Google Groups "sqlalchemy" group.
To post to this group, send email to sqlal...@googlegroups.com.
To unsubscribe from this group, send email to sqlalchemy+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
docs: http://www.sqlalchemy.org/docs/core/pooling.html#switching-pool-implementations
Is session.bind.dispose() the same as Engine.dispose()?I'm asking that because the docs says "A new connection pool is created immediately after the old one has been disposed", so you are destroying all connections in the pool to destroy one?I'm asking that because I need to close the current session connection after a current requests end, and destroying the pool for every request doesn't look right.
On Tuesday, April 5, 2011 3:14:09 PM UTC+3, León wrote:Hi,
I'm using "session.bind.dispose()"
León
On 5 abr, 07:47, Gary Shi <gary...@gmail.com> wrote:
> I found session.close() doesn't close the database connection (by
> calling session.close and sleep, then check the network connections),
> neither session.connection().close(). How to close the connection
> without quit my application?
--
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 sqlalchemy+...@googlegroups.com.
To post to this group, send email to sqlal...@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.