[SERVER-12852] v2.6.0-rc0 update $setOnInsert still saves invalid element names Created: 23/Feb/14 Updated: 11/Jul/16 Resolved: 24/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | 2.6.0-rc1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Roman Kuzmin | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Release notes say: "Starting in MongoDB version 2.5.4, update operations no longer supports saving field names that contain a dot (.) or a field name that starts with a dollar sign ($)." There is a case where update still saves a field name with a dot (.). The steps:
As a result, we have a new document which has a nested document with the element name with a dot: "bad.1". |
| Comments |
| Comment by Githook User [ 24/Feb/14 ] | |||||||||||
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: | |||||||||||
| Comment by Roman Kuzmin [ 23/Feb/14 ] | |||||||||||
|
Yet another case with a saved element name started with ($). If we try this with invalid name "$bad"
then it fails with a message "unknown operator: $bad". Good. But if we make "$bad" nested
then we can see that update saves this nested document with an element name "$bad". |