#33685: Tests crash when using only a service name on PostgreSQL.
-----------------------------------+------------------------------------
Reporter: Shane Ambler | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by Shane Ambler):
Replying to [comment:8 Mariusz Felisiak]:
> Using `['OPTIONS']['service']` and `['OPTIONS']['passfile']` is not a
"new" or only supported way for the `DATABASES` settings.
It looks like it has been available in "main" for a bit over a year, but
it is still "new" as it has only been available in one public release.
Yes, the old (or generic) method still works and will work properly if it
is the only config docs that you find.
Using `['DATABASE']['NAME']` and `['DATABASE']['USER']` will work for
runserver as well as test and they will override any service file
settings.
We shouldn't need to duplicate login details in two places to get basic
functionality.
I see having tests fail on the first tutorial as a big entry barrier for
new users.
--
Ticket URL: <https://code.djangoproject.com/ticket/33685#comment:9>
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/01070180acaa65b3-43a21ce8-8023-4f14-9fe8-cdbb8ff44719-000000%40eu-central-1.amazonses.com.
