I have historical version data in a proprietary format that I would like to migrate to django-reversion, so that all versions can be seen in a single place in the Admin. However, the older migrated versions always show up out of order. (I am also using django-reversion-compare, which sets history_latest_first to True by default.)
In the screenshot below, the version on top is migrated data, and the version on the bottom was created natively by django-reversion.
As best I can tell, this is because the ordering is being done on Version.id instead of Revision.date_created (the migrated versions will have a higher id value, having been added later). This works fine as long as the revisions and versions are created sequentially, but it breaks when they are not. Is there a particular reason why the sort was implemented this way, or would you be willing to support a date-based sort at least as an option?
I have historical version data in a proprietary format that I would like to migrate to django-reversion, so that all versions can be seen in a single place in the Admin. However, the older migrated versions always show up out of order. (I am also using django-reversion-compare, which sets
history_latest_firsttoTrueby default.)In the screenshot below, the version on top is migrated data, and the version on the bottom was created natively by django-reversion.
As best I can tell, this is because the ordering is being done on
Version.idinstead ofRevision.date_created(the migrated versions will have a higheridvalue, having been added later). This works fine as long as the revisions and versions are created sequentially, but it breaks when they are not. Is there a particular reason why the sort was implemented this way, or would you be willing to support a date-based sort at least as an option?