It appears that Vault's ADD command is case insensitive. One cannot add a file to a folder whose name is the same as an existing file when compared in a case insensitive way. Please see the attached. This is a nuisance when running automated software that does adds and deletes. The case that I ran into was that I wanted to add a file that was case sensitive and that started with a capital letter, and delete an image that was in all lower case letters. Sorting caused the add to appear before the delete, and therefore the ADD command failed. It could be a real issue if someone ever needs to have the same file in a case sensitive way saved in the same folder.
This was tested under Vault 3.0.
Vault 3.0 ADD command appears to be case insensitive
Moderator: SourceGear
-
- Posts: 55
- Joined: Thu Dec 02, 2004 1:59 pm
Vault 3.0 ADD command appears to be case insensitive
- Attachments
-
- ADD_casesensitivity_bug.doc
- (63 KiB) Downloaded 281 times
Yes, Vault was designed to not allow filenames of the same name after a case-insenstive compare. While Unix file systems support this, Windows does not, and we have to be careful to make sure that a Get from a working folder will retrieve all the files in the Vault folder.
You might need to auto-commit your operations as they happen, so the delete happens immediately, and then it won't run into problems when later adding a file of the same name.
You might need to auto-commit your operations as they happen, so the delete happens immediately, and then it won't run into problems when later adding a file of the same name.
re: case-sensitivity in MS-Windows
MS-Windows NT introduced the POSIX subsystem, which was required to handle case-sensitive filesystem behavior; an obvious & common example is having both MAKEFILE and Makefile in the same directory.
However, as a developer I'm not sure how to access such behavior when programming against the Win32 subystem APIs.
However, as a developer I'm not sure how to access such behavior when programming against the Win32 subystem APIs.
Yes, the POSIX subsystem is capable of that functionality, but the Microsoft .Net Framework FileStream classes on NTFS drives will constrain Vault to using case insensitive files.
It seems MS chose to "ignore" this capability for most Win32 applications - http://support.microsoft.com/default.as ... -us;100625
It seems MS chose to "ignore" this capability for most Win32 applications - http://support.microsoft.com/default.as ... -us;100625
Jeff Clausius
SourceGear
SourceGear
-
- Posts: 55
- Joined: Thu Dec 02, 2004 1:59 pm