-
Type:
Improvement
-
Resolution: Won't Fix
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: manual
-
Labels:
-
Environment:
*Location*: http://docs.mongodb.org/manual/reference/javascript/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31
*Referrer*: http://docs.mongodb.org/manual/
*Screen Resolution*: 1440 x 900
*repo*: docs
*source*: reference/javascript
*Location*: http://docs.mongodb.org/manual/reference/javascript/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31 *Referrer*: http://docs.mongodb.org/manual/ *Screen Resolution*: 1440 x 900 *repo*: docs *source*: reference/javascript
- add something, somewhere noting that the v8 engine is used under the covers with links to the v8 page at google (https://code.google.com/p/v8/) and the ECMA-262 spec (http://www.ecma-international.org/ecma-262/5.1/#sec-9.8) which the v8 library conforms to
- several of the built-in functions like cat(), cd(), run() aren't resolving and I could not figure out what was different about them as compared to other methods.
- also better clarity on allowable field names, eg: "$date" is perfectly valid JavaScript / JSON but invalid inside mongodb javascript. "$date" is allowed in imports and you might see "$oid" in exports but they're translated to other fields on import. We're not clear on this.
- is related to
-
-
- Closed
-