
|
If you were logged in you would be able to see more operations.
|
|
|
|
When we have an object graph and we want to attach, the AttachFieldManager will navigate to the leaf object in the tree and insert/update it, then the one before, then the one before etc. This means that each time we call updateObject() a call is made to NeoDatis
odb.store(obj);
which persists down the object graph. The problem is that related objects will have SCO wrappers, and so they will be persisted (since NeoDatis doesn't allow persist of a single object without persisting its relations).
What the solution is is not clear since attaching is handled by the StateManager and doesn't allow the datastore knowledge of what is the primary object. We could add a FieldManager to unwrap all SCO fields in a graph from an object, and then add a FieldManager to re-wrap all SCO fields in a graph from that object. This could be inefficient on a large graph.
|
|
Description
|
When we have an object graph and we want to attach, the AttachFieldManager will navigate to the leaf object in the tree and insert/update it, then the one before, then the one before etc. This means that each time we call updateObject() a call is made to NeoDatis
odb.store(obj);
which persists down the object graph. The problem is that related objects will have SCO wrappers, and so they will be persisted (since NeoDatis doesn't allow persist of a single object without persisting its relations).
What the solution is is not clear since attaching is handled by the StateManager and doesn't allow the datastore knowledge of what is the primary object. We could add a FieldManager to unwrap all SCO fields in a graph from an object, and then add a FieldManager to re-wrap all SCO fields in a graph from that object. This could be inefficient on a large graph. |
Show » |
Sort Order:
| There are no comments yet on this issue.
|
|