caffecoder napisał(a):
Hello.
I have pylons 0.96 (SVN) and current SQLAlchemy (0.3), and I have bug
that
doesn't exist earlier.
My connection code:
code
import sqlalchemy.mods.threadlocal
from sqlalchemy import DynamicMetaData, objectstore
metadata = DynamicMetaData( case_sensitive =
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' number of
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. Not sure
if that affects it at all though.
I'd love to know why all of a sudden, there's
On Aug 31, 2007, at 4:33 PM, Michael Bayer 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. Not sure
if that affects it at all
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() as
On 8/28/07, caffecoder [EMAIL PROTECTED] wrote:
sqlalchemy.exceptions.DBAPIError: (Connection failed)
(OperationalError) FATAL: sorry, too many clients already
I've been getting a similar but not identical error after upgrading to
SQLAlchemy 0.4, and somebody else on the list also mentioned
