-
Couldn't load subscription status.
- Fork 81
DOCSP-45398-detail-large-number-queries #742
New issue
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
Merged
sarah-olson-mongodb
merged 9 commits into
mongodb:master
from
shuangela:DOCSP-45398-detail-large-number-queries
Apr 11, 2025
Merged
Changes from 8 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
f78dd1c
add large integer limit note
shuangela a48e0c4
fix note syntax
shuangela 6077959
formatting
shuangela b320eb0
change wording
shuangela 01ba2ab
wording
shuangela eaea07f
grammar
shuangela 2996c85
wording
shuangela dec6b5a
jp suggestion
shuangela e817b0d
bb feedback
shuangela File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| .. note:: Large Integer Limitations | ||
|
|
||
| To query for integers larger than the JavaScript maximum integer size, | ||
| wrap the integer in string characters. | ||
|
|
||
| For example, to find all documents with a ``number`` value of ``507550989629521900``, use | ||
| this query filter: | ||
|
|
||
| .. code-block:: javascript | ||
|
|
||
| { "number": "507550989629521900" } | ||
This file contains hidden or 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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This example doesn't actually work. It's important to mention the need for
NumberLongin the example. This is how Compass knows the type to search for. In the example given in the current draft, Compass would interpret the search value as a string, not as a Long (aka large integer).For example,
{ restaurant_id: NumberLong(507550989629521900) }would not work, but{ restaurant_id: NumberLong("507550989629521900") }would workThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, thanks for the clarification! I'll change the example