#30178: Support duck-typing for database passwords in settings
-------------------------------------+-------------------------------------
Reporter: Dan Davis | Owner: Dan Davis
Type: Bug | Status: assigned
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Dan Davis):
> I'll close this once I've succeeded and convinced my colleagues. His
reservation will be the 20 or so django projects that will need to change
said boiler plate.
My colleagues are convinced, but looking at `django/db/backends/base.py`,
I see that the settings_dict is passed in, and there are even instances,
possibly for the test database, where it is copied with `copy.deepcopy`.
Certainly, this is not guaranteed to work with all backends. What about
the username and password for the test database? I will try it, and if
it works with Oracle, PostgreSQL, and MySQL, then we're out of the woods.
--
Ticket URL: <https://code.djangoproject.com/ticket/30178#comment:10>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.5ae3f090f6a89e265486c9509c5c577f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
