Closed javrasya closed 5 years ago
@javrasya of course, sorry for delay, I was posting the content of the migration but I guess you were able to recreate it.
@superandrew can you try v1.0.2 which has just been published. It must re-create the migration once and for all now.
I installed 1.0.2 from pip and I can confirm that the migration isn't generated anymore in my project.
Thank you for the contribution @superandrew . Please keep up reporting when you face some bugs. 🙏
Description:
Because
django-river
uses a random related_name in the state field, Django thinks that the state field got updated every time we runmakemigrations
. It should not be recreating it.