Thanks for clarifying. I left an idea (reuse Oracle-specifc CREATE_DB
setting, if it has the same meaning) on the ticket. Maybe we continue the
discussion there for now.
https://code.djangoproject.com/ticket/29717
On Tuesday, August 28, 2018 at 8:32:56 PM UTC-4, Curtis Maloney wrote:
>
> On 08/
On 08/28/2018 08:33 PM, Tim Graham wrote:
Why is a new option needed? Why can't --keepdb be used for this use case?
Because that would be different behavior.
If you can convince me that using --keepdb is a solution, then I will
use your argument to say that --keepdb should be on always.
Wha
Why is a new option needed? Why can't --keepdb be used for this use case?
On Tuesday, August 28, 2018 at 2:23:52 AM UTC-4, Curtis Maloney wrote:
>
> Greetings,
>
> one problem that turns up more and more frequently, it seems, is that
> someone is trying to run tests but can't because of the foll
Greetings,
one problem that turns up more and more frequently, it seems, is that
someone is trying to run tests but can't because of the following scenario:
1. The user they connect to the DB using a role that does NOT have
permission to create a DB
2. Django's PG adapter, when keepdb is no
