Ticket #21 (closed bug: fixed)

Opened 9 years ago

Last modified 9 years ago

wsgi.py - database.session.clear() called too late

Reported by: bertrand.croq Owned by: apoirier
Priority: major Component: database tier
Version: 0.1.0 Keywords:
Cc:

Description

In wsgi.py, database.session.clear() is called before phase1, but after security.set_user() is called. If the user is fetched from the database, this is a problem.

Shouldn't the session be cleared (or closed, as this seem to be prefered in  http://www.sqlalchemy.org/docs/04/session.html#unitofwork_using_expunge) at the end of each wsgi call ?

Change History

comment:1 Changed 9 years ago by apoirier

  • Status changed from new to closed
  • Resolution set to fixed

(In [a8e1e18819f43639277725b656699b9dcb9568b3]) Fixes #21. remove() is applied on the session at the end of each request processing

Note: See TracTickets for help on using tickets.