[SERVER-11556] insert command does not move _id field to the front of BSON obj Created: 04/Nov/13 Updated: 11/Jul/16 Resolved: 30/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.5.3 |
| Fix Version/s: | 2.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
Not sure if moving _id field to the front is the desired behavior, but eval8.js fails if we switch to using write commands because of this. |
| Comments |
| Comment by Githook User [ 30/Dec/13 ] |
|
Author: {u'username': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by Scott Hernandez (Inactive) [ 11/Nov/13 ] |
|
I take it back and we should always have _id first. |
| Comment by Eric Milkie [ 11/Nov/13 ] |
|
This can result in replicated data that does not match the primary. |
| Comment by Scott Hernandez (Inactive) [ 04/Nov/13 ] |
|
This is not desired behavior and the test can be fixed by using the assert.docEq function, which is order independent. |