Hey everyone, I am not sure if this is the best place to put this, so kindly let me know if I need to shift this somewhere else. I am working on a patch (https://link.getmailspring.com/link/245d649a-96bd-4577-a3d0-ebeb368f1...@getmailspring.com/0?redirect=https%3A%2F%2Fgithub.com%2Fdjango%2Fdjango%2Fpull%2F12687&recipient=ZGphbmdvLWRldmVsb3BlcnNAZ29vZ2xlZ3JvdXBzLmNvbQ%3D%3D) for ticket #31335. (https://link.getmailspring.com/link/245d649a-96bd-4577-a3d0-ebeb368f1...@getmailspring.com/1?redirect=code.djangoproject.com%2Fticket%2F31335&recipient=ZGphbmdvLWRldmVsb3BlcnNAZ29vZ2xlZ3JvdXBzLmNvbQ%3D%3D) The patch is working, but I am having trouble writing a clean test case for the same. The test involves removing an index on ForiegnKey, renaming the ForeignKey and adding the index back on the same. Since the schema tests involve using the editor directly, it doesn't affect the ModelState, which leads to a bit of a problem. When we alter the ForeignKey field, the column name is changed, while the field name remains the same. This leads to an inconsistent state when I try to add the index back on the renamed ForiegnKe y field. Since, the fields property of `Model._meta` is immutable, is it advisable to use migration operations to update the same?
Cheers Sanskar -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/245D649A-96BD-4577-A3D0-EBEB368F193B%40getmailspring.com.
