It will appear in the next release.
W dniu poniedziałek, 7 listopada 2016 14:38:46 UTC+1 użytkownik Carsten
Fuchs napisał:
>
> Am 05.11.2016 um 15:55 schrieb Carsten Fuchs:
> > Am 2016-11-05 um 13:11 schrieb Mariusz Felisiak:
> >> Yes. Please, make sure that your main oracle user has *ALTER USE
Am 05.11.2016 um 15:55 schrieb Carsten Fuchs:
Am 2016-11-05 um 13:11 schrieb Mariusz Felisiak:
Yes. Please, make sure that your main oracle user has *ALTER USER*
permission.
I'll check (it may take until Monday or Tuesday though) and post an update here.
Indeed, after having added the ALTER
Hi Mariusz,
Am 2016-11-05 um 13:11 schrieb Mariusz Felisiak:
Yes. Please, make sure that your main oracle user has *ALTER USER*
permission.
It is well possible that that is the culprit. I've set my database
user's privileges as described at
https://docs.djangoproject.com/en/1.10/ref/database
Hi Simon,
Am 05.11.2016 um 08:46 schrieb Simon Charette:
[0] https://code.djangoproject.com/ticket/27435#ticket
Thank you!
Best regards,
Carsten
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receivi
W dniu piątek, 4 listopada 2016 17:12:09 UTC+1 użytkownik Carsten Fuchs
napisał:
>
> supposed to work without having an explicit test password set?
>
>
Yes. Please, make sure that your main oracle user has *ALTER USER*
permission.
--
You received this message because you are subscribed to th
Hi Carsten,
> In other words, without setting an explicit (non-random) password,
database
> errors are expected when starting the tests with --keepdb ?
You are right. I just created a ticket[0] about preventing usage of
`--keepdb`
without defining a `TEST.PASSWORD` setting.
Simon
[0] https://
Dear Django fellows,
using Django 1.10.3 with Oracle database, is running
./manage.py test --keepdb
supposed to work without having an explicit test password set?
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.oracle',
# ...
'TEST': {
# --kee
7 matches
Mail list logo
