[SERVER-6592] improve FieldPath validation behavior Created: 25/Jul/12 Updated: 28/Oct/15 Resolved: 26/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.0-rc1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
See comments. |
| Comments |
| Comment by Aaron Staple [ 26/Jul/12 ] |
|
Documentation should describe characteristics of valid field paths. FieldPaths are validated as follows: uassert(15998, "FieldPath field names may not be empty strings.", fieldName.length() > 0); |
| Comment by auto [ 26/Jul/12 ] |
|
Author: {u'date': u'2012-07-26T00:04:46-07:00', u'email': u'aaron@10gen.com', u'name': u'Aaron'}Message: |