Re: Determining when a file has changed

Nahum.Wild wrote:
> Is there a way to control how Vault determines if a file has changed?  VSS
> offers CRC, Contents or Time as options for this.  I just checked in a file
> where the only part of it that had actually changed was the datetime stamp -
> the contents was unmodified.  I have 'Undo Check Out' set for 'Checking in
> unchanged files', but it was checked in anyway.  If I look in the history
> for it and do a diff there is no difference.

Vault 2.0 will include a fix that will make this situation a little
better.  There isn't a user option (like in VSS), but the default
behavior is to do the following when checking in a modified file (we
still detect modifications by date changes):

  Does the length differ from the length of the baseline?  If so,
  it's definitely modified and should be checked in.

  Does the CRC differ from the CRC of the baseline?  If so, it's
  definitely modified and should be checked in.

  If neither of the above is true, it's definitely NOT modified, and the 
  user's preference (check in unchanged or undo checkout of unchanged) 
  will be followed.

We only check the CRC of working files in this phase of check in/commit,
not while detecting changes as they happen (that would be very slow).

-- 
Shaw Terwilliger <[email protected]>
SourceGear LLC