Changes between Initial Version and Version 1 of Ticket #27751


Ignore:
Timestamp:
01/20/2017 06:29:39 PM (3 years ago)
Author:
Tim Graham
Comment:

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

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #27751

    • Property Triage Stage changed from Unreviewed to Accepted
  • Ticket #27751 – Description

    initial v1  
    11When 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}}}
    22
    3 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.
     3I 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.
    44
    55I 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]
Back to Top