|
@@ -739,13 +739,13 @@ class Content(DeclarativeBase):
|
739
|
739
|
# The only sorting that makes sens is ordering by "updated" field. But:
|
740
|
740
|
# - its content will soon replace the one of "created",
|
741
|
741
|
# - this "updated" field will then be dropped.
|
742
|
|
- # So for now, we order by "updated" explicitly, but remember to switch to
|
743
|
|
- # "created" once "updated" removed.
|
|
742
|
+ # So for now, we order by "revision_id" explicitly, but remember to switch
|
|
743
|
+ # to "created" once "updated" removed.
|
744
|
744
|
# https://github.com/tracim/tracim/issues/336
|
745
|
745
|
revisions = relationship("ContentRevisionRO",
|
746
|
746
|
foreign_keys=[ContentRevisionRO.content_id],
|
747
|
747
|
back_populates="node",
|
748
|
|
- order_by="ContentRevisionRO.updated")
|
|
748
|
+ order_by="ContentRevisionRO.revision_id")
|
749
|
749
|
children_revisions = relationship("ContentRevisionRO",
|
750
|
750
|
foreign_keys=[ContentRevisionRO.parent_id],
|
751
|
751
|
back_populates="parent")
|