If your host is dropping the connection after 30 minutes of inactivity then you could keep it alive by creating a thread that performs a simple dummy SQLObject operation every 15 minutes or so to keep the connection live.
However it is actually possible, although unlikely I've found, for a connection to die and having a reconnection strategy would be a good thing. Justin On 5 May 2006, at 00:04, [EMAIL PROTECTED] wrote: > > Hi group, > Has anyone managed to resolve the mysql connection resiliency > problems? My hosting provider seems to run a 30 minute max on mysql > connections, so TG/SQLObject's inability to deal with this is a bit of > a non-starter. > > As suggested in this thread > (http://groups.google.com/group/turbogears/browse_frm/thread/ > eeb289d5a0ca36f9/d2cd5f7ee2674082?q=mysql+server > +away&rnum=1#d2cd5f7ee2674082) > I tried modifying the __get__ method in class PackageHub. It catches > the exception ok > but self.set_hub() doesn't seem to reset the connection. > > I also tried catching the exception in SQLObject's mysqlconnection.py, > recalling MySQLConnection.makeConnection(). This also doesn't seem to > help. > > I'm running TG0.8.8. Would upgrading help? > > Thanks for any leads! > Paul > http://pauleastham.com > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
