Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
*Location*: https://docs.mongodb.org/getting-started/node/indexes/
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.89 Safari/537.36
*Referrer*: https://docs.mongodb.org/getting-started/node/aggregation/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: indexes
*Location*: https://docs.mongodb.org/getting-started/node/indexes/ *User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.89 Safari/537.36 *Referrer*: https://docs.mongodb.org/getting-started/node/aggregation/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: indexes
Description
JavaScript objects aren't guaranteed to preserve order, yet the compound index example seems to rely on this.