Ok that makes sense.
Thank you Mike.
On Jun 16, 10:42 pm, Michael Merickel wrote:
> On Thu, Jun 16, 2011 at 12:38 AM, Liju wrote:
> > The documentation says 'It’s sometimes advantageous to not use
> > SQLAlchemy’s thread-scoped sessions'.
>
> The issue isn't with scoped_session as much as it ha
On Thu, Jun 16, 2011 at 12:38 AM, Liju wrote:
> The documentation says 'It’s sometimes advantageous to not use
> SQLAlchemy’s thread-scoped sessions'.
>
The issue isn't with scoped_session as much as it has to do with using a
global variable to store your database connections. It just works out
On Wed, 2011-06-15 at 22:38 -0700, Liju wrote:
> The documentation says 'It’s sometimes advantageous to not use
> SQLAlchemy’s thread-scoped sessions'. Thread-scoped as I understand is
> done using scoped_session(), which will associate an SQLAlchemy
> session for currently running thread.
>
> WIt
The documentation says 'It’s sometimes advantageous to not use
SQLAlchemy’s thread-scoped sessions'. Thread-scoped as I understand is
done using scoped_session(), which will associate an SQLAlchemy
session for currently running thread.
WIth my experience from J2EE I understand that each request-re
