Fix of DBRef resaving/deserialization weird behaviour #261
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using mongodb driver with native deserializer i've descovered strange bug:
1 Object created and saved with DBRef field
2 Then loaded (deserilizer processed their fields) and saved again.
3 After saving DBRef field became corrupted! IMHO due to $db field value (empty string) in DBRef //see patch
I've created test case and fix.
PS.
All test cases checked agains pure BSON serializer! Regardless of 'native_parser' option value!
Due to small typo:
But correct: