#27614: Storing the DB used in the state before calling `_save_table` -------------------------------------+------------------------------------- Reporter: Joseph Kahn | Owner: nobody Type: Uncategorized | Status: closed Component: Database layer | Version: 1.10 (models, ORM) | Severity: Normal | Resolution: needsinfo Keywords: | Triage Stage: | Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Joseph Kahn): I created a PR with a change that doesn't break that test but fixes it for a lot of the edge cases I run into with multiple databases. https://github.com/django/django/pull/7841 -- Ticket URL: <https://code.djangoproject.com/ticket/27614#comment:3> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/064.f0d61f5e74e7a919cea2b1b5a927b214%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.