Opened 9 years ago
Last modified 12 months ago
#25540 new Bug
Reusing databases doesn't work on PostgreSQL for migrations tests — at Initial Version
| Reported by: | Anssi Kääriäinen | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Ülgen Sarıkavak | Triage Stage: | Accepted |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
| Pull Requests: | How to create a pull request | ||
Description ¶
Running migrations tests with keepdb results in failures for the second run. To reproduce:
./runpython --settings=<your_postgresql_settings> --keepdb migrations # success ./runpython --settings=<your_postgresql_settings> --keepdb migrations # Lots of failures.
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR].
Note:
See TracTickets
for help on using tickets.