On 4/10/06, Eugene Lazutkin <[EMAIL PROTECTED]> wrote: > > kopikopiko wrote: > > Hi, > > > > I have an application set up under: > > Django 0.91 > > Windows 2000 Server > > MySQL 5.0 > > which reads scheduled events from a table then spawns threads (using > > the Thread module) to process the events and update the table. As soon > > as my threads started writing to the database I ran into MySQL error > > 2013 - 'Lost connection to MySQL server during query'. Googling led me > > to Eugene Lazutkin's blogging on the issue and patches 463 and 1442 to > > deal with the problems of the conflict over the MySQL connection > > between the threads and the original app. I applied patch 1442 as it > > seemed more recommended and the problem seemed to go away. > > #1442 was applied to trunk some time ago. Most probably you are running > an old version of Django. > > > I'm looking at how to address this by perhaps: > > 1) applying patch 1539 > > #1539 was applied to trunk as well. > > > 2) creating a new database connection in the thread (but don't know how > > to do this) > > > > Any advice would be appreciated... > > svn up your Django installation and test again. Let us know the results.
The patch on #1590 was also recently applied, and it may also be a factor. -- The Pythonic Principle: Python works the way it does because if it didn't, it wouldn't be Python. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
