StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODjango - OperationalError: (2006, 'MySQL server has gone away')
primarykey
Id
7835272
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-20T11:30:55.527
FavoriteCount
1
LastActivityDate
2018-01-10T10:30:42.057
LastEditDate
2017-05-23T12:32:14.287
LastEditorUserId
-1
OwnerUserId
348545
ParentId
0
PostTypeId
1
Score
11
ViewCount
6238
LastEditorDisplayName
text
Body
Bottom line first: How do you refresh the MySQL connection in django? Following a <code>MySQL server has gone away</code> error I found that <a href="http://dev.mysql.com/doc/refman/5.0/en/gone-away.html" rel="nofollow noreferrer">MySQL documentation</a> and other sources (<a href="https://stackoverflow.com/questions/2582506/2006-mysql-server-has-gone-away-in-wsgi-django">here</a>) suggest increasing the <code>wait_timeout</code> MySQL parameter. To me this seems like a workaround rather than a solution. I'd rather keep a reasonable <code>wait_timeout</code> and refresh the connection in the code. The error: <pre><code> File "C:\my_proj\db_conduit.py", line 147, in load_some_model SomeModel.objects.update() File "C:\Python26\lib\site-packages\django-1.3-py2.6.egg\django\db\models\manager.py", line 177, in update return self.get_query_set().update(*args, **kwargs) File "C:\Python26\lib\site-packages\django-1.3-py2.6.egg\django\db\models\query.py", line 469, in update transaction.commit(using=self.db) File "C:\Python26\lib\site-packages\django-1.3-py2.6.egg\django\db\transaction.py", line 142, in commit connection.commit() File "C:\Python26\lib\site-packages\django-1.3-py2.6.egg\django\db\backends\__init__.py", line 201, in commit self._commit() File "C:\Python26\lib\site-packages\django-1.3-py2.6.egg\django\db\backends\__init__.py", line 46, in _commit return self.connection.commit() OperationalError: (2006, 'MySQL server has gone away') </code></pre> Setup: Django 1.3.0 , MySQL 5.5.14 , innodb 1.1.8 , Python 2.6.6, Win7 64bit
Tags
<mysql><django>
Title
Django - OperationalError: (2006, 'MySQL server has gone away')
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USJonathan
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PODjango - OperationalError: (2006, 'MySQL server has gone away')
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PODjango - OperationalError: (2006, 'MySQL server has gone away')
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.