Joel Goldstick, would definitely not recommend doing an all in one update. That'd be like going from windows XP to 10 in one go. For personal projects, you could do it, but would side-eye any professional who suggested doing this with a company or workplace project.
https://docs.djangoproject.com/en/4.0/releases/2.1/#model-view-permission is liekly the permission being hit. OP, would it be possible for you to rename the original permission name in a migration in 1.11, and then move forward with the migration? On Friday, July 1, 2022 at 9:35:31 AM UTC-4 mma...@gmail.com wrote: > > 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 django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/29923fb3-d7d8-4206-91d8-765ed452e585n%40googlegroups.com.
