Synergy object times

Synergy has several time stamps on its objects.

create_time: the time when the object version in the database has been created.

source_create_time: the timestamp taken from the file system upon loading the object into the repository.

Note that when a new object has been created in the database the filesystem timestamp is not reflected in the database, and the db object creation time is reflected instead. When the new version of an already existing object is created, the filesystem timestamp is taken and reflected in the source_create_time attribute.

E.g.

new file has been created on a filesystem at Mon Dec 28 10:47:35 2009 and has been "synced" into the database at Mon Dec 28 10:56:45 2009. So the dbobject create time is set to Mon Dec 28 10:56:45 2009.

Later, when we check out the file again, a new version, 2, is created and it's creation time is set to Mon Dec 28 10:58:05 2009. Now the source_creation_time is set to the timestamp the file has on a file system, that is Mon Dec 28 10:47:35 2009.

ccm query -owner myuser "source_create_time>time('December 28 2009') and source_create_time<time('December 29 2009')" -f "%name %version %instance %create_time %source_create_time"
1) newfile.txt 1 1 Mon Dec 28 10:56:45 2009 Mon Dec 28 10:56:46 2009
2) newfile.txt 2 1 Mon Dec 28 10:58:05 2009 Mon Dec 28 10:47:35 2009

When the file is checked in its source_create_time is unchanged, even though the file on a fs has been edited immediately before the sync.

$ ccm query -owner myuser "source_create_time>time('December 28 2009') and source_create_time<time('December 29 2009')" -f "%name %version %instance %create_time %source_create_time %modify_time"

1) newfile.txt 1 1 Mon Dec 28 10:56:45 2009 Mon Dec 28 10:56:46 2009 Mon Dec 28 10:57:53 2009
2) newfile.txt 2 1 Mon Dec 28 10:58:05 2009 Mon Dec 28 10:47:35 2009 Mon Dec 28 13:17:17 2009