#21597: (2006, 'MySQL server has gone away') in django1.6 when wait_timeout
passed
-------------------------------------+-------------------------------------
Reporter: ekeydar@… | Owner: aaugustin
Type: Bug | Status: new
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: mysql | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: closed => new
* resolution: wontfix =>
Comment:
That's a different issue and a good reason to reopen the ticket until we
figure it out.
Do you have any way to check if MySQL drops connections while a view
function is executing? In that case, Django 1.5 reopens a connection
automatically (possibly breaking transactional integrity) while Django 1.6
raises an error.
--
Ticket URL: <https://code.djangoproject.com/ticket/21597#comment:39>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/075.b24a111b1f1765870af83fb2914402e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
