[DOCS-4727] Provide an example of comparison semantics Created: 23/Jan/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Mark Callaghan | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | groom | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 1 day ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
In http://docs.mongodb.org/manual/reference/bson-types/ it would be a lot easier for me to understand this statement if you gave an example, like 1 != "1" "When comparing values of different BSON types, MongoDB uses the following comparison order, from lowest to highest" — Also, I think the docs at http://docs.mongodb.org/manual/reference/bson-types/ should be more specific about the following. I assume this is a statement about the BSON numeric types (32-bit int, 64-bit int, double) because JSON doesn't have a choice. I think a few sentences would be sufficient to explain the precedence. Is it int32 -> int64 -> double? "MongoDB treats some types as equivalent for comparison purposes. For instance, numeric types undergo conversion before comparison." |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |