[SERVER-622] element_.eoo assertion on invalid upsert Created: 10/Feb/10 Updated: 12/Jul/16 Resolved: 10/Feb/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Colin Snover | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
mongodb-linux-x86_64-1.3.1 (binary release) running on Linux 2.6.31-17-generic (Ubuntu 9.10), PHP 5.2.10-2ubuntu6.4 |
||
| Participants: |
| Description |
Assertion (same for both operations):
|
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 10/Feb/10 ] |
|
see set5.js |
| Comment by auto [ 10/Feb/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: test for |
| Comment by Kristina Chodorow (Inactive) [ 10/Feb/10 ] |
|
This does seem to be a server bug, the equivalent JS code reproduces the assertion on the command line: > db.foo.update( {'url':'http://example.com'},{$set:{url:'http://example.com', 'title':null}}, true) Seems like ending the $set with a null messes things up. |
| Comment by Colin Snover [ 10/Feb/10 ] |
|
Argh...can't edit description! I am not sure that the upsert I am doing is actually invalid; I was just confused based on the response to Also, this is actually a SERVER issue, not PHP; I didn't think it was initially, but then I realized that the test I was doing on the command-line was not the same (I was omitting $set). Sorry! |