#33685: Using new postgresql settings fails when running tests
-----------------------------------+--------------------------------------
Reporter: Shane Ambler | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: 4.0
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
If you want to user PostgreSQL's password files, all required databases
must be included, i.e. `postgres`, `dbname`, `test_dbname`, e.g. the
following configuration works for me
{{{
localhost:5432:postgres:postgres_username:SeCrEtPassworD
localhost:5432:dbname:postgres_username:SeCrEtPassworD
localhost:5432:test_dbname:postgres_username:SeCrEtPassworD
}}}
`settings.py`:
{{{#!python
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.postgresql',
'HOST': 'localhost',
'PORT': 5432,
'NAME': 'dbname',
'USER': 'postgres_username',
'OPTIONS': {
'passfile': '.custompgpass',
}
},
}
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33685#comment:5>
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/01070180a739fa8e-3c1e4607-973c-4e9c-8ddb-3377a7c5d89d-000000%40eu-central-1.amazonses.com.
