@thinkt4nk i had to modify the original migration because it couldn't run on newer versions of django. the old uuid field includes a class that no longer exists. when these migrations are run on a newer version of django, the second one really doesn't matter, since it isn't actually altering anything.
@thinkt4nk i had to modify the original migration because it couldn't run on newer versions of django. the old uuid field includes a class that no longer exists. when these migrations are run on a newer version of django, the second one really doesn't matter, since it isn't actually altering anything.