[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: bugtraq pros and cons

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2005-10-13 17:40:35 CEST

Faron Dutton wrote:

> I am experimenting with issue tracking integration and wish to understand
> why the issue ID is stored in the artifact's comment instead of storing it
> in a versioned or an unversioned property.
> I think that the follow are true but I would appreciate confirmation or
> clarification.
> * Storing the ID in an unversioned property (revision level property) would
> require the client to call the server each time it wished to know the value.
> This would increase the network traffic and make it impossible to work
> off-line.

This of course could be done. But, it wouldn't be an atomic commit
anymore. It could well be that the commit succeeds, but then the setting
of the revision property could fail. What should we do in such a case?
Since we rely on the Subversion library and its exported API's, we can't
guarantee that the revision property is set if the commit succeeds.

> * Storing the ID in a versioned property (artifact level property) would
> increment the repository's version number and the ID would no longer be
> associated with the correct revision of the artifact.

Yes, it would create a new revision. So not an option either.

> Is it possible to set the value of a versioned property on a changed
> artifact and then commit, thus preventing the scenario above?

No, you can't change history in Subversion.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Oct 13 16:50:20 2005

This is an archived mail posted to the TortoiseSVN Users mailing list.