Re: [sqlalchemy] MySQL has gone away

Perfect - Thanks. :-) > On Jan 7, 2013, at 7:47 PM, Warwick Prince wrote: > >>> >>> On Jan 7, 2013, at 7:20 PM, Diego Woitasen wrote: >>> I'm back to this :) My problem was that I'm not closing the session properly. My new question is... is there a way to au

Re: [sqlalchemy] MySQL has gone away

On Jan 7, 2013, at 7:47 PM, Warwick Prince wrote: >> >> On Jan 7, 2013, at 7:20 PM, Diego Woitasen wrote: >> >>> >>> I'm back to this :) >>> >>> My problem was that I'm not closing the session properly. >>> >>> My new question is... is there a way to autoclose the session? My example, >>>

Re: [sqlalchemy] MySQL has gone away

> > On Jan 7, 2013, at 7:20 PM, Diego Woitasen wrote: > >> >> I'm back to this :) >> >> My problem was that I'm not closing the session properly. >> >> My new question is... is there a way to autoclose the session? My example, >> at the end of the scope? >> >> What's the recommend way to d

Re: [sqlalchemy] MySQL has gone away

On Jan 7, 2013, at 7:20 PM, Diego Woitasen wrote: > > I'm back to this :) > > My problem was that I'm not closing the session properly. > > My new question is... is there a way to autoclose the session? My example, at > the end of the scope? > > What's the recommend way to do this? > > I'

Re: [sqlalchemy] MySQL has gone away

On Thursday, December 27, 2012 10:22:08 PM UTC-3, Michael Bayer wrote: > > > On Dec 27, 2012, at 6:28 PM, Diego Woitasen wrote: > > Hi, > I know that this was discussed several times in the past but I can't > solve the problem with the tip that I read in this list. Every morning my > applicati

Re: [sqlalchemy] MySQL has gone away

On Dec 27, 2012, at 6:28 PM, Diego Woitasen wrote: > Hi, > I know that this was discussed several times in the past but I can't solve > the problem with the tip that I read in this list. Every morning my > application dies with the msg "MySQL has gone away". My app has different > modules (wh

[sqlalchemy] MySQL has gone away

Hi, I know that this was discussed several times in the past but I can't solve the problem with the tip that I read in this list. Every morning my application dies with the msg "MySQL has gone away". My app has different modules (which are process) and this errors appears in the simplest one an

[sqlalchemy] MySQL has gone away error

I have the follwing setting and I create engine from config. sqlalchemy.url : "mysql://sfdev:sf...@localhost:3306/sfdev" sqlalchemy.pool_recycle : 3600 sqlalchemy.convert_unicode : true I am getting the following error. Seems like recycle required, but I have mentioned recycle in the configuratio

[sqlalchemy] MySQL has gone away (again)

Hi, I know this problem shows on group from time to time, but suggested solutions does not work for me (pool_recycle). Here is my situation: 1. I am using SQLAlchemy 0.4.7p1-2 from Pylons 0.9.6.2-2 on Debian Lenny (xen-amd64) 2. From time to time I see in logs: "MySQL has gone away" and this is

[sqlalchemy] MySql has gone away

Hi All, I was getting My Sql has gone away, then i set sqlalchemy.pool_recylce=3600 in prod.cfg. it was woking fine but but still some time i get the same error i.e MySql has gone away. Can any one tell me what should i do? Thanks anD Regards Reetesh Nigam --~--~-~--~~---

[sqlalchemy] MySQL Has Gone Away

This isn't unique to SQLAlchemy, but when using MySQL after long periods in inactivity (in a web-app server) with the objectstore session, the error: MySQL server has gone away comes up, meaning the database conneciton has timed out. Is there anyway to inject in a simple test query (and possibl