#22646: MySQL dbshell command should respect the encryption flag
-------------------------------------+-------------------------------------
Reporter: zsoldosp | Owner: zsoldosp
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 1
Keywords: | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by erikr):
* needs_better_patch: 0 => 1
* stage: Ready for checkin => Accepted
* needs_docs: 0 => 1
Comment:
I can see the use for `dbshell` here, but `ca` is not a [[http://mysql-
python.sourceforge.net/MySQLdb.html|supported parameter in MySQLdb]]. As
far as I can see, all currently supported `OPTION`'s are, i.e. they are
both MySQLdb options and can be translated to `mysql` command line
options. However, this change would only apply to `dbshell`, which may be
entirely unexpected by users.
The [[https://docs.djangoproject.com/en/dev/ref/databases/#connecting-to-
the-database|current documentation]] simply refers to MySQLdb to figure
out which options exist, so the `ca` option also has no documentation in
this patch, as MySQLdb doesn't mention it, as it's not a MySQLdb option.
--
Ticket URL: <https://code.djangoproject.com/ticket/22646#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.b50fcf10e4b5d584ba760f834bcaaef2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
