> What do I do about this? Clearly I should remove the permission I created. How do I deal with the migration? Should I remove the permission while I run the app as Django 1.11 before moving on to a 2.2 environment?
You could rename the current view_inventorychangelog record with a data migration to avoid the constraint, upgrade to 2.2, and then move any references to the old DB record to the new using a data migration. > Sorry, I can't answer your question. But, I am wondering why you are > upgrading to a very out of date version of Django that is no longer > supported. I think 3.2 is the oldest supported version. Why not > upgrade to 4? The options for uplifting severely out of date projects are to either step-by-step migrate through older versions, or rewrite in the target version. Cheers, Michael Manfre -- You received this message because you are subscribed to the Google Groups "Django users" 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-users/e1fd50ee-97da-4ccd-86ba-90743ebf908cn%40googlegroups.com.
