[SERVER-4184] date max index bound value looks messed up in shell as IsoDate Created: 31/Oct/11 Updated: 14/Apr/16 Resolved: 29/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Aaron Staple | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | confirm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
> c.find({a:{$gt:new Date()}} ).explain() } > c.find({a:{$gt:new Date()}} ).explain().indexBounds.a[0][1].valueOf() I think this value is generated by void BSONObjBuilder::appendMaxForType( const StringData& fieldName , int t ) { Potentially this numeric value is invalid for a javascript date, but we might want to do something so the output looks a little nicer. Also, there could potentially be other issues relating to date values outside an allowed js date range (round tripping, $where style queries, etc). So might be worth spending some time looking into these. |