tmlab/majortom

Changes in Changeset in wrong order

Closed this issue · 1 comments

What steps will reproduce the problem?
1. Creating an association (association type exists already) while history is 
empty

What is the expected output? What do you see instead?
One revision of type "ASSOCIATION_ADDED" with 3 changes (ASSOCIATION_ADDED, 
TYPE_SET, SCOPE_MODIFIED, in this order). Instead, the order is changed.



Original issue reported on code.google.com by schulze....@googlemail.com on 12 Nov 2010 at 10:15

Problem was solved by adding an explicit ordering by time.

Original comment by Sven.Kro...@googlemail.com on 18 Nov 2010 at 6:28

  • Changed state: Fixed