[SERVER-12986] getLastError should work across connections. Created: 01/Mar/14 Updated: 10/Dec/14 Resolved: 15/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Abhishek Kona | Assignee: | Ramon Fernandez Marina |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Currently the protocol defines that getLastError should be sent on the same connection as the Insert/Update/Delete operation. This makes writing a proxy for MongoDB hard. It would be a nice feature to have the ability to send GetLastErrors across connections. They could be identified by the requestTo/responseTo fields. |
| Comments |
| Comment by Ramon Fernandez Marina [ 15/Jul/14 ] |
|
In MongoDB 2.6 there's no need for a separate getLastError command, so this request is obsolete at this stage. We're now closing this ticket, but if you believe the 2.6 protocol is insufficient feel free to re-open and provide additional details. Regards, |