#27751: Teardown of a PG test database fails if it is an autogenerated test_MYDB
database
-------------------------------------+-------------------------------------
Reporter: Cynthia Kiser | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution:
Keywords: database, testing | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* stage: Unreviewed => Accepted
Old description:
> When running tests using a Postgres instance where the user does not have
> access to the postgres database, the database teardown fails with the
> message: {{{django.db.utils.OperationalError: cannot drop the currently
> open database}}}
>
> I do not see any problems on 1.8 release branch starting from the commit
> referenced in [https://code.djangoproject.com/ticket/24791]. The commit
> that was made to the master branch at that time also works - until the
> commit to fix [https://code.djangoproject.com/ticket/25329]. That commit
> was before the branch for 1.9 was cut, so this bug affects all releases
> in the 1.9 and 1.10 series as well as the current master branch.
>
> I don't understand the issue well enough to resolve the apparent conflict
> between supporting MySQL and Postgres, but I do have a sample app (the
> polls tutorial) with a README that explains how to set up your database
> to reproduce the issue: [https://github.com/cnk/d110example]
New description:
When running tests using a Postgres instance where the user does not have
access to the postgres database, the database teardown fails with the
message: {{{django.db.utils.OperationalError: cannot drop the currently
open database}}}
I do not see any problems on 1.8 release branch starting from the commit
referenced in #24791. The commit that was made to the master branch at
that time also works - until the commit to fix #25329. That commit was
before the branch for 1.9 was cut, so this bug affects all releases in the
1.9 and 1.10 series as well as the current master branch.
I don't understand the issue well enough to resolve the apparent conflict
between supporting MySQL and Postgres, but I do have a sample app (the
polls tutorial) with a README that explains how to set up your database to
reproduce the issue: [https://github.com/cnk/d110example]
--
Comment:
The report seems credible, although I did not attempt to reproduce myself.
--
Ticket URL: <https://code.djangoproject.com/ticket/27751#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.f44e2f9e66736e18eb754e33d8e00007%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
