#31491: dbshell command for MySQL backend uses "passwd" instead of "password".
-------------------------------------+-------------------------------------
Reporter: Maruti N Sharma | Owner: Maruti N
Type: | Sharma
Cleanup/optimization | Status: assigned
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution:
Keywords: dbshell, db, | Triage Stage: Accepted
command-line |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Maruti N Sharma):
Replying to [comment:4 felixxm]:
> `passwd` from `OPTIONS` is passed to a `--password` argument so it
shouldn't cause any connection failures. However I agree that we can unify
this. We can add a small release note (even if it's not documented).
Please send patch via GitHub.
I understand that, but it should not attempt to get the "passwd" from
settings_dict instead of "password", which would cause connection failure
if there is no "passwd" key specified in django db settings (only
"password" key) .
I apologise if description wasn't clear enough. I will add reproduction
steps.
--
Ticket URL: <https://code.djangoproject.com/ticket/31491#comment:6>
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/067.223c123edab01f165e90e078e2a61ed4%40djangoproject.com.
