#31337: [mysql] Django loses track of renamed table when recreating a foreign
key,
resulting in "Table 'foo.bar' doesn't exist"
-------------------------------------+-------------------------------------
Reporter: Stephen Finucane | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => invalid
Comment:
> I was unable to reproduce this bug with 2.0 or higher, which means this
has since been resolved. However, I wasn't able to find a bug nor identify
the change that fixed it though so I'm filing in case anyone else stumbles
upon this. I expect it to be closed but I'd really appreciate pointers to
the actual fix since not being able to identify it myself is annoying :-)
You're looking for #25530 (b50815ee418b38e719476c2d5f6e2bc69f686927).
Please TicketClosingReasons/UseSupportChannels to get help doing that in
the future.
--
Ticket URL: <https://code.djangoproject.com/ticket/31337#comment:2>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.23014df444e85b17a1470f7a0309d2ea%40djangoproject.com.
