Hi, On Fri, May 9, 2008 at 10:04 AM, saurav gangulyy <[EMAIL PROTECTED]> wrote: > I clone a versionable node1 into workspace2 from workspace1, with base > version 1.0. And I checkout and checkin node1 in workspace1, and I checkout > and checkin node1 in workspace2.
Checkout just makes a node "writable", i.e. it doesn't modify the base version of the node. So both of your checkins will create a new version with 1.0 as a predecessor. > Base Version in both workspaces should be same(1.1) but version in workspace1 > is 1.1, and in workspace2 is 1.1.1. What is the reason for this unexpected > behaviour? As explained above, your checkins create two branches in the version history. If you want both checkins to be a part of the same branch in the version history, you need to update (or merge, or restore) the node in workspace2 to version 1.1 before checking it in. But in this case the base version of the node in workspace1 would still be 1.1, and in workspace2 the base version would be 1.2. > And what is the way to maintain version consistency in two workspaces? I'm not sure what you mean by "version consistency" here. What's your use case? > (We have to checkout and checkin both workspaces seperately, we can't > use node.update()) . Checkout and checkin will only move the base version of a node to the new checked in version created by checkin. You need to use update, merge, or restore to "rebase" a node to a different base version. BR, Jukka Zitting
