When looking at the revision history of a given file (say with a change made once a month over the past 2 years), and performing a get on a given revision (say, from last year), the 'Get XXXX - Version Y' dialog appears. Here it is possible to 'Set file time:' to Current, Modification, or Check In.
As expected, 'Current' sets the time correctly to the current time. 'Check In' also seems to work, timestamp the file on the hard drive to the check in time. 'Modification' however, does not work properly. It sets the time on the hard drive to the time of the latest revision, not the revision you are actually getting.
This appears to me to be a bug. Please confirm. FYI, I am running Vault V3.5.1 (4786).
Best regards,
David
"Set file time" to Modification fails
Moderator: SourceGear
"Set file time" to Modification fails
David Carr
Senior Systems Analyst
ESSA Technologies Ltd.
Senior Systems Analyst
ESSA Technologies Ltd.
I wasn't able to reproduce this. Are you looking at the modification time in the file properties on disk, or in the GUI Client file list?
If you're looking the the GUI Client, the Local Date column will show the modification time, since that's the timestamp of the file.
A screenshot might be helpful.
If you're looking the the GUI Client, the Local Date column will show the modification time, since that's the timestamp of the file.
A screenshot might be helpful.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Screenshots
Hi Linda,
Here are the screenshots:
1. First, Show History on file 'EMHPS.Tech.doc'
2. Perform a get on version 2 of this file, which has a date of "15-02-2005 9:07:23 AM", where time is set to Modification.
3. Now, looking in Explorer at the hard disk we see a timestamp of "09-03-2007 7:28 AM".
This time in #3, however, is not the Modification time of version 2 of this file, but rather the modification time of the latest version of this file. So this is the problem.
Hope this helps.
David
PS: Note that if 'Set file time:' in the Get dialog is set to 'Check In', then it seems like it is working correctly by setting it to the 'Check In' time - but of course I want the 'Modification' time.
Here are the screenshots:
1. First, Show History on file 'EMHPS.Tech.doc'
2. Perform a get on version 2 of this file, which has a date of "15-02-2005 9:07:23 AM", where time is set to Modification.
3. Now, looking in Explorer at the hard disk we see a timestamp of "09-03-2007 7:28 AM".
This time in #3, however, is not the Modification time of version 2 of this file, but rather the modification time of the latest version of this file. So this is the problem.
Hope this helps.
David
PS: Note that if 'Set file time:' in the Get dialog is set to 'Check In', then it seems like it is working correctly by setting it to the 'Check In' time - but of course I want the 'Modification' time.
- Attachments
-
- FileTimeModification3_FileMgr.png (38.31 KiB) Viewed 3799 times
-
- FileTimeModification2_GetDlg.png (7.48 KiB) Viewed 3799 times
-
- FileTimeModification1_History.png (43.28 KiB) Viewed 3799 times
David Carr
Senior Systems Analyst
ESSA Technologies Ltd.
Senior Systems Analyst
ESSA Technologies Ltd.
Ok - I was able to reproduce this. If you get the file itself from history, this works properly. However, based on your screenshot, you're getting from a label, and that gets the file with the modification date of the latest version -- which is incorrect.
I'll log this as a bug. Meanwhile, if you want to get version 2 of the file with mod time, get the checked in version, rather than the labeled version 2. If you are getting a folder, show folder history by version, then find the version that was labeled.
I'll log this as a bug. Meanwhile, if you want to get version 2 of the file with mod time, get the checked in version, rather than the labeled version 2. If you are getting a folder, show folder history by version, then find the version that was labeled.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
'Modification' never works, regardless of from label
Hi Linda,
Glad to see that it is a bug. Just to clarify, all that I did was a 'Show History' on the given file. I also went through and tested each case, performing a 'Get' on each record in the 'History Explorer' (ref. image #1).
In all cases where the 'Set file time:' is set to Modification, the filestamp on the machine is always set to the modification time of the last checkin revision (i.e. 09-03-2007, 08:28) - not the modification time of the actual revision. So it doesn't matter whether I am doing a 'get' on a label or a revision, the result is the same.
So it doesn't matter (at least on my machine) whether I am performing a get on revision 2 (i.e. the checked in version) or a label. At this point there is no way to obtain the Modification time for anything other than the revision on the tip.
Thx,
David
PS: Can you pls post the link to the bug that you logged.
Glad to see that it is a bug. Just to clarify, all that I did was a 'Show History' on the given file. I also went through and tested each case, performing a 'Get' on each record in the 'History Explorer' (ref. image #1).
In all cases where the 'Set file time:' is set to Modification, the filestamp on the machine is always set to the modification time of the last checkin revision (i.e. 09-03-2007, 08:28) - not the modification time of the actual revision. So it doesn't matter whether I am doing a 'get' on a label or a revision, the result is the same.
So it doesn't matter (at least on my machine) whether I am performing a get on revision 2 (i.e. the checked in version) or a label. At this point there is no way to obtain the Modification time for anything other than the revision on the tip.
Thx,
David
PS: Can you pls post the link to the bug that you logged.
David Carr
Senior Systems Analyst
ESSA Technologies Ltd.
Senior Systems Analyst
ESSA Technologies Ltd.
You are correct, Mod time from history on a revision does not work properly. Actually, there was already a bug logged for that.
We don't make our bug database public. It's Item: 8827 in our database, for future reference.PS: Can you pls post the link to the bug that you logged.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager