-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: manual
-
Labels:
-
Environment:
*Location*: http://docs.mongodb.org/manual/reference/operator/query/regex/
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.104 Safari/537.36
*Referrer*: https://www.google.co.nz/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: reference/operator/query/regex
*Location*: http://docs.mongodb.org/manual/reference/operator/query/regex/ *User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.104 Safari/537.36 *Referrer*: https://www.google.co.nz/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: reference/operator/query/regex
This page mentions that Mongo uses PCRE, and specifies that you must use $regex over /.../ to pass PCRE-only options.
However, it does not mention what version of PCRE is used, nor what build options were used (e.g. UTF-8, UTF-16 etc), and does not mention that you also need to use $regex if your pattern contains features that PCRE supports but JS does not.