[DOCS-3775] Documentation for regex under an $in is misleading Created: 17/Jul/14 Updated: 19/Aug/14 Resolved: 19/Aug/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 26 weeks, 1 day ago | ||||||||
| Description |
|
Refers to server ticket SERVER-14595 and this page: The documentation makes it sound like either the {$regex: /pattern/} syntax or the raw /pattern/ syntax for regular expressions is allowed inside an $in. However, to my knowledge only the raw /pattern/ syntax has ever been allowed. Versions of 2.6 through 2.6.3 will reject $regex inside an $in explicitly. The docs should state explicitly that only the /pattern/ syntax is currently allowed. |
| Comments |
| Comment by Githook User [ 19/Aug/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 19/Aug/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 19/Aug/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |