Community
Participate
Working Groups
When committing a local change using an offlineClone the timestamp is not set on the replicatorSession. This causes a problem since bug #328352 has been fixed, as the fix makes use of the timestamp to ensure the correct order of the updates.
Created attachment 182025 [details] Testcase
Created attachment 182026 [details] Proposed patch
Looks good, Pascal ;-)
Committed to HEAD.
Available in R20110608-1407