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

(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, 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.

I have submitted the pull request.

[Mariusz Felisiak]

Maruti, steps are incorrect. Django looks for passwd in OPTIONS and for PASSWORD in DATABASES['alias'], if not provided. All works properly.

[Maruti N Sharma]

Of course, my mistake, I have updated my comment and the description as well. Thank you.

[Hasan Ramezani]

​New PR

[Mariusz Felisiak <felisiak.mariusz@…>]

In 9e8edc1:

Fixed #31491 -- Allowed 'password' option in DATABASESOPTIONS on MySQL.