Fix: Schema Length Mismatch for ObjectId Non-id Fields in Collections #588
+3
−3
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.
Proposed changes
When a non-id field in a collection has a value of ObjectId type, an error is reported with the following message:
This occurs because when the ObjectId is converted to a string, it takes the form: {‘$oid’:‘67f8e2503d1bd029812b7767’}. The length becomes 35, which exceeds the predefined varchar(30) limit.
Problem Summary:
Checklist(Required)
Does it affect the original behavior: No
Has unit tests been added: No Need
Has document been added or modified: No Need
Does it need to update dependencies: No)
Are there any changes that cannot be rolled back: No
Further comments
Only the length of the ObjectId type when converted to Varchar type was changed.