node_id for 'create' operations being "_0" instead of the new node's id?

[LUCAS DE RODRIGO IGNACIO <id...@typsa.es>]

Hello,
    I'm new to the mailing list and to SubVersion in general (and to 
make matters worse, English isn't my primary language), so please bear 
with me. :) I've read through the issues list thrice and searched the 
mailing lists on several occasiones, but I haven't been able to find 
any reference to this problem. 

I'm developing an application which makes use of the SubVersion 
repository. I'm asking for history elements through svn_fs_paths_changed, 
and then comparing their IDs through svn_fs_compare_ids with a given 
ID. The problem is, it seems that whenever one of the history elements 
is a creation, no matter if both operations refer to the same node, 
svn_fs_compare_ids returns "unrelated". This, oddly enough, happens 
even when they are the SAME history element, if one of them was obtained 
via svn_fs_node_history + svn_fs_history_prev and the other with 
svn_fs_paths_changed.

Upon further investigation, it seems that creation history elements 
obtained through svn_fs_paths_changed present the following in their 
ID: their node_id component, instead of housing the ID of the node 
(file/directory) created (as seen in following operations on that 
node), contains "_0" (or, if more than one creation was present in 
the same revision, "_1", "_2" and so on). This almost looks like a 
temporary placeholder ID that should be replaced later on with the 
ID of the node being created on commit, but isn't. 

I'm not sure if this problem is widespread; or if it's working as 
intended and it's just that I'm doing something wrong. Particularly
since it seems that this would effectively prevent creations from 
appearing on history logs as long as one relies on ID comparison 
alone. Whatever the case, any help would be greatly appreciated. :)
Thanks in advance!
    Ignacio de Lucas

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: node_id for 'create' operations being "_0" instead of the new node's id?

[Ben Collins-Sussman <su...@collab.net>]

I think you should resend to the dev@ list, since it's about deep svn  
internals, and it's about developing software on top svn's APIs.  :-)


On Jul 13, 2005, at 5:01 AM, LUCAS DE RODRIGO IGNACIO wrote:

> Hello,
>     I'm new to the mailing list and to SubVersion in general (and to
> make matters worse, English isn't my primary language), so please bear
> with me. :) I've read through the issues list thrice and searched the
> mailing lists on several occasiones, but I haven't been able to find
> any reference to this problem.
>
> I'm developing an application which makes use of the SubVersion
> repository. I'm asking for history elements through  
> svn_fs_paths_changed,
> and then comparing their IDs through svn_fs_compare_ids with a given
> ID. The problem is, it seems that whenever one of the history elements
> is a creation, no matter if both operations refer to the same node,
> svn_fs_compare_ids returns "unrelated". This, oddly enough, happens
> even when they are the SAME history element, if one of them was  
> obtained
> via svn_fs_node_history + svn_fs_history_prev and the other with
> svn_fs_paths_changed.
>
> Upon further investigation, it seems that creation history elements
> obtained through svn_fs_paths_changed present the following in their
> ID: their node_id component, instead of housing the ID of the node
> (file/directory) created (as seen in following operations on that
> node), contains "_0" (or, if more than one creation was present in
> the same revision, "_1", "_2" and so on). This almost looks like a
> temporary placeholder ID that should be replaced later on with the
> ID of the node being created on commit, but isn't.
>
> I'm not sure if this problem is widespread; or if it's working as
> intended and it's just that I'm doing something wrong. Particularly
> since it seems that this would effectively prevent creations from
> appearing on history logs as long as one relies on ID comparison
> alone. Whatever the case, any help would be greatly appreciated. :)
> Thanks in advance!
>     Ignacio de Lucas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org