Command line client returns truncated history item name

[Tilman]

Hi,

I'm having a problem retrieving the history with the command line client.

For example, when I run this:

Code: Select all

D:\Work\sql dummy\trunk>"C:\Program Files\SourceGear\Vault Client\vault.exe" history "$/Red Gate/Internal projects/SQL Dummy/Trunk" -excludeactions label,obliterate -rowlimit 0 -begindate 2008-02-25T16:17:20 -enddate 2008-02-25T16:42:01 -host xxx -user xxx -password xxx -repository development

I get this:

Code: Select all

<vault>
  <history>
    <item txid="264944" date="25/02/2008 16:33:30" name="k/CCNet Test" type="10" typeName="Added" version="2" objverid="2795800" user="xxx" actionString="Added New Text Document.txt" />
    <item txid="264944" date="25/02/2008 16:33:30" name="k/CCNet Test/new text document.txt" type="70" typeName="Created" version="1" objverid="2795797" user="xxx" actionString="Created" />
  </history>
  <bugsreferenced />
  <result>
    <success>True</success>
  </result>
</vault>

Observe the 'name' attribute of both items, which specifies a folder of

Code: Select all

k/CCNet Test

Even weirder, when I do the same as another user I get a folder of

Code: Select all

Trunk/CCNet Test

I would suggest that it should actually be

Code: Select all

CCNet Test

Is this a bug, or am I doing something wrong?

Cheers,

Tilman

[lbauer]

We've had reports of truncated history, but we never able to reproduce it, even on a database provided to us by a user who say the truncated history.

We've had additional clues that it seems to be based on particular users, so we've going to try again to reproduce it on a database in-house. Previously we'd always logged in as Admin.

[lbauer]

We've been able to reproduce this in house, by logging into the affected database as a user, rather than admin.

A check of the database shows the path is properly stored in the database.

The problem appears to be with the stored procedure that returns the history information -- this may be affected by user rights.

No that we know where the problem is, we'll work on a fix.

[Tilman]

Thanks!

[jeremy_sg]

Tilman,

We've reproduced the error, and believe that we have a stored procedure which corrects the bug. Would you be interested in applying the updated stored procedure? Email me using the button below this post if you are.

[lbauer]

We have sent our stored procedure fix (a SQL Query) to users who have experienced the truncated history issue, and it appeared to resolve the problem.

This fix will included in Vault 4.1.1/Fortress 1.1.1