dbshell command for MySQL backend uses "passwd" instead of "password".

[Maruti N Sharma]

For MySql, "passwd" has been replaced with "password" long time ago, please check here https://code.djangoproject.com/ticket/5024
But dbshell command still looks for "passwd" key in the settings for db password, resulting in connection error.
This behaviour is also slightly different than other back-ends.

Pull request submitted: ​https://github.com/django/django/pull/12763

steps to reproduce:

---

• create a new django project, set env
• choose mysql as db back-end
• specify db setting as following (ref: ​https://docs.djangoproject.com/en/3.0/ref/settings/#std:setting-DATABASES)

# use actual db username, password etc
DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'mydatabase',
        'USER': 'mydatabaseuser',
        'PASSWORD': 'mypassword',
        'HOST': '127.0.0.1',
        'PORT': '5432',
    }
}

• Open a terminal and activate respective environment
• run: python manage.py dbshell
• You should get following error: Access denied for user 'mydatabaseuser'@'localhost' (using password: NO)

(My apologies for any mistake, I am new to bug-tracking system)

[Maruti N Sharma]

patch file

[Mariusz Felisiak]

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.

[Maruti N Sharma]

Replying to 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, actually I was using "OPTIONS" field for database settings, that is where this caused issue on my end.

If you wish to unify this behaviour, I have submitted the pull request.