I imagined a new method to test whether a data migration worked correctly. Because I’m fascinated about how well my dpy fixtures work, I wrote a new section about this in https://www.lino-framework.org/admin/datamig.html
One detail came up while exploring this method:
models that used
did show differences because their modified field gets
touched when the fixture is being loaded.
This was because of Djangos auto_now
option on that field.
That’s why we now handle this in a overridden save() method (touching the field only if
lino.Lino.loading_from_dump is False.