Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only fragments roots are handled correctly when objects are moved #29

Closed
markus1978 opened this issue Mar 6, 2013 · 3 comments
Closed
Assignees

Comments

@markus1978
Copy link
Owner

When an object gets a new container its id index entry has to be updated and it also has to move from one UOC to another. But it looks like this is only done for objects that are root or become root of a fragment. However, this is not thoroughly tested.

This related to:

  1. Incremental remove #12
  2. Incremental reference updates #13
  3. Deletion of objects with extrinsic ID #14
@ghost ghost assigned markus1978 Mar 6, 2013
@markus1978
Copy link
Owner Author

When objects are moved, also their contents has to be moved with respect to the UOCs and IDs, see also #13.

@markus1978
Copy link
Owner Author

Removing a user object from one UOC and adding a new user object to another UOC is not really moving.

@markus1978
Copy link
Owner Author

Resolved, but not for multiple models. Incremental remove #12, #14 still a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant