[SERVER-6226] findAndModify return value inconsistent between 2.0.x and 2.1.2 when using upsert Created: 27/Jun/12 Updated: 05/Nov/12 Resolved: 03/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.1.2 |
| Fix Version/s: | 2.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bernie Hackett | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | findAndModify | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Minor Change | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Found this while testing PyMongo against 2.1.2. In 2.0.x mongod returns {'ok': 1.0, 'value': {}}, in 2.1.2 it returns {'ok': 1.0, 'value': null}.
This will cause problems for code that expects a document as return value. |
| Comments |
| Comment by auto [ 13/Jul/12 ] | |||||||
|
Author: {u'date': u'2012-07-13T09:52:17-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: release notes: | |||||||
| Comment by auto [ 13/Jul/12 ] | |||||||
|
Author: {u'date': u'2012-07-12T15:46:47-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: | |||||||
| Comment by auto [ 03/Jul/12 ] | |||||||
|
Author: {u'date': u'2012-07-03T11:06:41-07:00', u'name': u'behackett', u'email': u'bernie@10gen.com'}Message: Fix test failure due to 2.1.2 behaviour change. See | |||||||
| Comment by auto [ 03/Jul/12 ] | |||||||
|
Author: {u'date': u'2012-07-03T10:22:01-07:00', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: | |||||||
| Comment by Bernie Hackett [ 27/Jun/12 ] | |||||||
|
This behavior is new in 2.1.2:
|