On Aug 31, 1:33 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> I dont think theres a connection pooling issue; its just that the
> Session being remove()'d still references a checked out connection,
> which has been fixed in the latest trunk. please issue Session.close
> () before Session.remove(
On Aug 31, 8:58 am, Ben Bangert <[EMAIL PROTECTED]> wrote:
> I've started getting this same overflow error after upgrading to the
> latest beta4, I don't recall having the problem with beta3 but during
> beta3 I used Session.mapper and now I'm using plain mapper. No
On Aug 29, 8:16 am, "Mike Orr" <[EMAIL PROTECTED]> wrote:
> I've been getting a similar but not identical error after upgrading to
> SQLAlchemy 0.4, and somebody else on the list also mentioned this
> recently. I don't have the traceback but it was the error for
> exceeding the 'max_overflow' nu
