#34666: Mysql issue using afirst "The client was disconnected by the server 
because
of inactivity"
-------------------------------------+-------------------------------------
     Reporter:  Bernardo Tavares     |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  4.2
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  needsinfo
     Keywords:  async, afirst,       |             Triage Stage:
  mysql, inactivity                  |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Bernardo Tavares):

 Replying to [comment:2 Mariusz Felisiak]:
 > > In my understanding, Django always opens a connection, executes a
 query and then closes a connection.
 >
 > Yes, if you're talking about request-response cycle and connections are
 not persistent.
 >
 > > Is it not closing the connection when using ''"afirst()"''? This feels
 seems like a bug to me, or is something in the documentation I'm not
 getting.
 >
 > As far as I'm aware, this has nothing to do with `afirst()`.
 >
 > > Any help? Thank you in advance!
 >
 > I don't think you've explained the issue in enough detail to confirm a
 bug in Django and Trac is not a support channel. Please reopen the ticket
 if you can debug your issue and provide details about why and where Django
 is at fault. A small project that reproduces the issue will also help. If
 you're having trouble debugging, see
 TicketClosingReasons/UseSupportChannels for ways to get help.

 Understood. I will try to go deeper on this.
 I opened a [forum discussion here](https://forum.djangoproject.com/t
 /debugging-the-client-was-disconnected-by-the-server-because-of-
 inactivity/21730) , if you can help me debug a bit further and explain why
 this is not related with afirst() I would be grateful.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34666#comment:4>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070188d84453fd-61f4c741-69d2-4145-b567-dd9f5998a71a-000000%40eu-central-1.amazonses.com.

Reply via email to