On Tue, Feb 14, 2012 at 03:16:00PM -0800, Jonathan Vanasco wrote:
I recently learned that pyramid_tm closes the session on a
transaction.commit()
I also learned that either transaction or pyramid_tm automatically
commits at the end of a request
I'm not comfortable with either of these
On Wed, Feb 15, 2012 at 8:47 AM, Marius Gedminas mar...@gedmin.as wrote:
On Tue, Feb 14, 2012 at 03:16:00PM -0800, Jonathan Vanasco wrote:
I recently learned that pyramid_tm closes the session on a
transaction.commit()
I also learned that either transaction or pyramid_tm automatically
Mike-
From what I read: the multiple attempts are to deal with issues where
you lose the database connection through an API. I think by default
it tries 3 times, then fails for real.
The exact error didn't happen on a get(), it happens like this:
useraccount= add() or get()
On Wed, Feb 15, 2012 at 10:26:50AM -0800, Mike Orr wrote:
On Wed, Feb 15, 2012 at 8:47 AM, Marius Gedminas mar...@gedmin.as wrote:
On Tue, Feb 14, 2012 at 03:16:00PM -0800, Jonathan Vanasco wrote:
I recently learned that pyramid_tm closes the session on a
transaction.commit()
I also
On Wed, Feb 15, 2012 at 09:05:01PM +0200, Marius Gedminas wrote:
On Wed, Feb 15, 2012 at 10:26:50AM -0800, Mike Orr wrote:
On Wed, Feb 15, 2012 at 8:47 AM, Marius Gedminas mar...@gedmin.as wrote:
On Tue, Feb 14, 2012 at 03:16:00PM -0800, Jonathan Vanasco wrote:
I recently learned that
I recently learned that pyramid_tm closes the session on a
transaction.commit()
I also learned that either transaction or pyramid_tm automatically
commits at the end of a request
I'm not comfortable with either of these behaviors, particularly the
latter
I've run into too many situations where
