[SERVER-5227] Updates fail when zero-length keys exist Created: 06/Mar/12 Updated: 09/Mar/12 Resolved: 08/Mar/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Glenn Maynard | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | update | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
This was reported in SERVER-2051, but appears to be a bug of its own (although the problem might be masked if the change in that ticket was made): > db.left.insert( {field1: "whatever", "": null}) , {$set: {"field2": "test"}}, false, true) On a quick look at the source, it looks like the result of compareDottedFieldNames is incorrect when r is the null string. Probably related: > db.left.insert( {field1: "whatever"}) , {$set: {"": "test"}}, false, true) |
| Comments |
| Comment by Glenn Maynard [ 08/Mar/12 ] |
|
Looks like it works. I'll leave a note in SERVER-2051 as well. (I can't find how to close this bug. Surely reporters can close their own tickets?) |
| Comment by Eric Milkie [ 06/Mar/12 ] |
|
Hi Glenn. |