-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
Continuing to support getLastError, especially in mongos, is a minor ongoing nuisance. See, e.g., SERVER-28318. Could the server reasonably deprecate it in 3.6 and remove it in 3.8? What about just remove it in 3.6?
- is depended on by
-
SERVER-28318 make sharded getLastError work with paths that go over ASIO, or eliminate it
- Closed
- related to
-
SERVER-10637 Provide a mechanism to expose the connectionId so that drivers can log it
- Closed