docs: adds Reserved Field Names section to migration guide #11308
+51
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ed-field-names-migration-guide
DanRibbens
requested changes
Feb 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added a new Reserved Field Names section to the migration guide.
Clarified that certain field names (
__v,salt,hash,file, etc.) are reserved for internal use and will be sanitized from the config if used.Included additional reserved names specific to MongoDB, authentication-enabled collections, and upload-enabled collections.
Added a note recommending against using field names with an underscore (
_) prefix, as they are reserved for internal columns and may cause conflicts in SQL and other contexts.Fixes #11159