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

"LUCAS DE RODRIGO IGNACIO" <idelucas@typsa.es> writes:

> Thanks a lot for your quick reply!
>
> > [...]; if the node-revision must have a freshly-assigned node-id or
> > copy-id, it uses "_" followed by a base36 unique to the transaction.
> > During the final phase of a commit, node-revision IDs are rewritten to
> > have unique node-ID and copy-ID fields and to have "r<rev>/<offset>"
> > txn-id fields.
>
> This is pretty much as I suspected, only it seems that that rewrite
> isn't working correctly in my case. What is very strange, though,
> is that svn_fs_node_id and svn_fs_paths_changed return different IDs;
> which would seem to imply that something weirder than a rewrite,
> failed or not, is going on (as one would expect only one of the IDs
> to survive, in either case).

I wonder if there is some nefarious node-ID caching going on here...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 14 16:14:12 2005