#33715: Prevent MySQL dbshell from exiting on Ctrl-C
-------------------------------------+-------------------------------------
               Reporter:  andrew-    |          Owner:  nobody
  cybsafe                            |
                   Type:             |         Status:  new
  Cleanup/optimization               |
              Component:  Core       |        Version:  4.0
  (Management commands)              |
               Severity:  Normal     |       Keywords:
           Triage Stage:             |      Has patch:  0
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 Currently, pressing Ctrl-C in a MySQL dbshell will exit the program with a
 KeyboardInterrupt exception. In the mysql command line client, Ctrl-C will
 cancel the current command or clear the current command buffer if a
 command is not running. This is a similar issue to one that affected the
 PostgreSQL dbshell - see: #27954.

 To fix this, we can override the SIGINT handler in the same way as for the
 PostgreSQL client. Or perhaps we can move this functionality from the
 django.db.backends.postgresql.client to the django.db.backends.base.client
 module, so that all db backends can benefit from Ctrl-C working as per the
 underlying db command line client.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33715>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070180d2f2c7a2-08797b83-41a8-4cc6-9bce-1ad4244ac2f7-000000%40eu-central-1.amazonses.com.

Reply via email to