Opened 3 years ago

Last modified 3 years ago

#27751 new Bug

Teardown of a PG test database fails if it is an autogenerated test_MYDB database — at Initial Version

Reported by: Cynthia Kiser Owned by: nobody
Component: Testing framework Version: 1.9
Severity: Normal Keywords: database, testing
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


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 The commit that was made to the master branch at that time also works - until the commit to fix 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:

Change History (0)

Note: See TracTickets for help on using tickets.
Back to Top