I'd like to chip in that I have this problem too, and gathered (from the fact that I could find no other documented instances of the problems) that it was something I was doing wrong. Perhaps it is - if someone else has deployed Turbogears on a low-traffic site on MySQL and has no problems please let us know here :)
Apparently increasing the wait_timeout variable on your mysql server is supposed to help, though I saw no difference in my case. This bug drives me nuts, because everything else about turbogears is very slick, and it isn't exactly in a feature that rarely gets used. 500 Server errors don't look terribly professional to end users, and telling them to "Just refresh, and it'll work the second time" isn't an option either. Surely this isn't a difficult bug to fix? How about if the server discarded any connection that has not been used for x seconds before executing a query? Thanks, Patrick -- http://www.labyrinthdata.net.au --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
