[sqlalchemy] Re: ODBC Connection is busy error - BruceC - com.googlegroups.sqlalchemy

18 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: ODBC Connection is b...

From	Sent On	Attachments
BruceC	23 Apr 2008 20:42
Paul Johnston	24 Apr 2008 10:04
Rick Morrison	24 Apr 2008 10:20
Michael Bayer	24 Apr 2008 11:14
BruceC	24 Apr 2008 20:54
Michael Bayer	24 Apr 2008 21:21
Esceo	26 Apr 2008 23:55
BruceC	27 Apr 2008 05:10
Michael Bayer	27 Apr 2008 16:13
Michael Bayer	27 Apr 2008 16:21
Rick Morrison	27 Apr 2008 17:54
Michael Bayer	27 Apr 2008 18:06
Rick Morrison	27 Apr 2008 18:26
BruceC	27 Apr 2008 18:58
Michael Bayer	27 Apr 2008 21:02
Michael Bayer	27 Apr 2008 21:04
BruceC	28 Apr 2008 01:03
Michael Bayer	28 Apr 2008 06:58

Subject:	[sqlalchemy] Re: ODBC Connection is busy error
From:	BruceC (bco...@manpower.com.au)
Date:	04/27/2008 05:10:12 AM
List:	com.googlegroups.sqlalchemy

Hi Michael,

Thanks for your persistence :)

I've searched through my app, & we don't seem to have any calls to fetchone(), so I'm not sure what else to look for, but I'll try to do some debugging with ResultProxys, & see if that leads to any possible answers.

On a side note, in our Pylons development.ini, we have these settings: sqlalchemy.default.max_overflow = -1 sqlalchemy.default.pool_size = 32

Is there anything there that could be having an effect on this?

On Apr 25, 2:21 pm, Michael Bayer <mike...@zzzcomputing.com> wrote:

only if youre leaving dangling ResultProxys opened with pending results, which should be a fairly rare occurence in a normal application. if you simply call fetchall() on results instead of fetchone(), that alone would eliminate any hanging cursors.