Saving trees of objects - should save objects that have the foreign keys after the related object

[jeff2001]

Redmine Issue #1721

When you're saving a tree of objects, it's currently add related objects on to the end of the transaction. This poses a problem if the object you're saving has a foreign key to the related object. In this case you have to manually save the related object before you save this object, which is not always correct (eg. 1 to 1 composition relationships). Instead the transaction committer should realise it needs to save the related object first instead of last.

Updated by Peter Wiles over 2 years ago
Some work done in rev 18257. Still to write some tests.