Re: [Twisted-Python] Consensus on how to handle "MySQL server has gone away"

2012-10-05 Thread Glyph
Le Oct 4, 2012 à 12:26 PM, E S a écrit : > On Wed, Oct 3, 2012 at 3:39 PM, Glyph wrote: >> >> Le Oct 3, 2012 à 6:36 AM, Augusto Mecking Caringi >> a écrit : >> >>> On Wed, Oct 3, 2012 at 8:27 AM, Itamar Turner-Trauring >>> wrote: On 10/03/2012 04:28 AM, Phil Mayers wrote: > I thin

Re: [Twisted-Python] Consensus on how to handle "MySQL server has gone away"

2012-10-04 Thread E S
On Wed, Oct 3, 2012 at 3:39 PM, Glyph wrote: > > Le Oct 3, 2012 à 6:36 AM, Augusto Mecking Caringi > a écrit : > >> On Wed, Oct 3, 2012 at 8:27 AM, Itamar Turner-Trauring >> wrote: >>> On 10/03/2012 04:28 AM, Phil Mayers wrote: I think the behaviour it should be aiming for is clear: 1

Re: [Twisted-Python] Consensus on how to handle "MySQL server has gone away"

2012-10-03 Thread Glyph
Le Oct 3, 2012 à 6:36 AM, Augusto Mecking Caringi a écrit : > On Wed, Oct 3, 2012 at 8:27 AM, Itamar Turner-Trauring > wrote: >> On 10/03/2012 04:28 AM, Phil Mayers wrote: >>> I think the behaviour it should be aiming for is clear: >>> 1. Test each connection with "good_sql" before beginning t

Re: [Twisted-Python] Consensus on how to handle "MySQL server has gone away"

2012-10-03 Thread Phil Mayers
On 03/10/12 12:27, Itamar Turner-Trauring wrote: > On 10/03/2012 04:28 AM, Phil Mayers wrote: >> I think the behaviour it should be aiming for is clear: >> 1. Test each connection with "good_sql" before beginning the user >> interaction/query > > The problem is that this adds latency; this can add

Re: [Twisted-Python] Consensus on how to handle "MySQL server has gone away"

2012-10-03 Thread Augusto Mecking Caringi
On Wed, Oct 3, 2012 at 8:27 AM, Itamar Turner-Trauring wrote: > On 10/03/2012 04:28 AM, Phil Mayers wrote: >> I think the behaviour it should be aiming for is clear: >> 1. Test each connection with "good_sql" before beginning the user >> interaction/query > > The problem is that this adds latency;

Re: [Twisted-Python] Consensus on how to handle "MySQL server has gone away"

2012-10-03 Thread Tobias Oberstein
> On 10/03/2012 04:28 AM, Phil Mayers wrote: > > I think the behaviour it should be aiming for is clear: > > 1. Test each connection with "good_sql" before beginning the user > > interaction/query > > The problem is that this adds latency; this can add up to quite a slowdown if > your database ser

Re: [Twisted-Python] Consensus on how to handle "MySQL server has gone away"

2012-10-03 Thread Itamar Turner-Trauring
On 10/03/2012 04:28 AM, Phil Mayers wrote: > I think the behaviour it should be aiming for is clear: > 1. Test each connection with "good_sql" before beginning the user > interaction/query The problem is that this adds latency; this can add up to quite a slowdown if your database server is on a

Re: [Twisted-Python] Consensus on how to handle "MySQL server has gone away"

2012-10-03 Thread gelin yan
On Wed, Oct 3, 2012 at 4:28 PM, Phil Mayers wrote: > On 10/02/2012 06:09 PM, E S wrote: > > I have a service running that occasionally connects to a MySQL > > database. When there is no activity on it for some time, I eventually > > get the the error > > > > _mysql_exceptions.OperationalError: (2

Re: [Twisted-Python] Consensus on how to handle "MySQL server has gone away"

2012-10-03 Thread Phil Mayers
On 10/02/2012 06:09 PM, E S wrote: > I have a service running that occasionally connects to a MySQL > database. When there is no activity on it for some time, I eventually > get the the error > > _mysql_exceptions.OperationalError: (2006, 'MySQL server has gone away') > > I have found a few posts o

[Twisted-Python] Consensus on how to handle "MySQL server has gone away"

2012-10-02 Thread E S
I have a service running that occasionally connects to a MySQL database. When there is no activity on it for some time, I eventually get the the error _mysql_exceptions.OperationalError: (2006, 'MySQL server has gone away') I have found a few posts on this group related to this issue http://twis