sharing / pinning / rename problem

[kasti]

Hi,

We have had sharing problems in the past and after a lot of testing we found out what the problem was. The problem can be reproduced as follows:


1. Create 2 projects:

Proj
Component

2. Put a file into Component folder (e.g. sharedfile.cpp)

3. share file "sharedfile.cpp" to Proj

4. Pin file "sharedfile.cpp" in Proj to version 1

5. rename file "sharedfile.cpp" in Component Folder to "newsharedfile.cpp"

6. reshare file "newsharedfile.cpp" to Proj folder

-> now there will be two files in Proj, "sharedfile.cpp" and "newsharedfile.cpp"

-> these two file are really the same file!!!!!!

-> now, if for example "sharedfile.cpp" is unpinned in component folder, both files dissappear

-> all resharing for newsharedfile.cpp to Proj folder will end with a db error

-> there is no recovery from this (nothing helps, not even obliterate).

A solution to this would be that step 6 above should not be possible.


Please let me know if you can confirm the above problem in vault 3.0.1.



Thanks for now,
Herbert.

[lbauer]

Yes, I was able to reproduce this. We'll have to take a look at the database to see what happened to the file(s). The files still exist in some way, though it's not clear why they disappeared from the tree view.

[lbauer]

Follow-up: When I logged in with a client on another machine, I was able to see the "newsharedfile.cpp" in both Component and Proj folders. I then went back to the original client machine and deleted the client side cache folder and the hidden state folders (_sgvault). After closing and reopening the client, the file appeared again in Proj, correctly renamed and shared.

It looks like the database handled this correctly, but the cache and hidden state files were confused.