Opened 3 years ago

Last modified 2 years ago

#27751 new Bug

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

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

Description (last modified by Tim Graham)

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

Change History (1)

comment:1 Changed 3 years ago by Tim Graham

Description: modified (diff)
Triage Stage: UnreviewedAccepted

The report seems credible, although I did not attempt to reproduce myself.

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