We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
OObjectEntitySerializer.detachAll(o, db, returnNonProxiedInstance, new HashMap<Object, Object>(), new HashMap<Object, Object>());
with returnNonProxiedInstance= true return full detached object
return inner map as OTrackedMap
save simple object:
public class SimpleObject{ @Id private Object rid; @Version private Object version; private String objectId; private Map<String, String> templatePartsIds; public String getObjectId() { return objectId; } public void setObjectId(String objectId) { this.objectId = objectId; } public Map<String, String> getTemplatePartsIds() { return templatePartsIds; } public void setTemplatePartsIds(Map<String, String> templatePartsIds) { this.templatePartsIds = templatePartsIds; } }
read it from DB and try to deatachall
The text was updated successfully, but these errors were encountered:
Also with OTrackedList
Sorry, something went wrong.
Fix detaching of maps and collections in Object db
239565b
Resolves: #8256
Hi @ScoobyMax
I just pushed a fix for this in 2.2.x branch, now I'm porting it to develop (3.0) The fix will be released with 2.2.36 and 3.0.1
Thanks
Luigi
9d0ef3b
luigidellaquila
No branches or pull requests
OrientDB Version: 2.2.34
Java Version: 1.8
OS: windows
Expected behavior
with returnNonProxiedInstance= true return full detached object
Actual behavior
return inner map as OTrackedMap
Steps to reproduce
save simple object:
read it from DB and try to deatachall
The text was updated successfully, but these errors were encountered: