ObjectId already set #288
Answered
by
Bios-Marcel
Bios-Marcel
asked this question in
Q&A
-
I am receiving the following error when trying to store an obejct that contains a
What could be the cause of this? I am rather clueless. |
Beta Was this translation helpful? Give feedback.
Answered by
Bios-Marcel
Sep 18, 2024
Replies: 1 comment
-
So, it appears that this was an issue caused by serialising an object that was previously copied via Manually "copying" the field by calling the setter (which creates a fresh Lazy-reference) did the job! Hope this helps anyone |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
Bios-Marcel
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So, it appears that this was an issue caused by serialising an object that was previously copied via
ObjectCopier
. The object in question contained the mentionedLazy
field.Manually "copying" the field by calling the setter (which creates a fresh Lazy-reference) did the job!
Hope this helps anyone