@@ -28,7 +28,7 @@ b) identifiable does not exist: check the to_be_inserted dict(key is a hash comp
...
@@ -28,7 +28,7 @@ b) identifiable does not exist: check the to_be_inserted dict(key is a hash comp
Maybe keep another dict that tracks what Record objects are in the to_be_updated dict (id(rec) as key?)
Maybe keep another dict that tracks what Record objects are in the to_be_updated dict (id(rec) as key?)
After treating leave Records, Records that could not be checked before can be checked: Either referenced Records now have an ID or they are in the to_be_inserted dict such that it is clear that the identifiable at hand does not exist in the server.
After treating leaf Records, Records that could not be checked before can be checked: Either referenced Records now have an ID or they are in the to_be_inserted dict such that it is clear that the identifiable at hand does not exist in the server.
This way, the whole structure can be resolved except if there are circular dependencies: Those can be added fully to the to_be_inserted dict. (???)
This way, the whole structure can be resolved except if there are circular dependencies: Those can be added fully to the to_be_inserted dict. (???)
