[SERVER-30735] DBDirectClient should use its own LastError Created: 18/Aug/17  Updated: 30/Oct/23  Resolved: 29/Aug/17

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 3.5.13

Type: Task Priority: Major - P3
Reporter: Mathias Stearn Assignee: Mathias Stearn
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-30867 Add a resmoke hook to ensure no failp... Backlog
Backwards Compatibility: Minor Change
Sprint: Repl 2017-08-21, Repl 2017-09-11
Participants:
Linked BF Score: 0

 Description   

This will avoid poluting the user's last error with errors on internal operations, while still allowing those operations to read their own errors.



 Comments   
Comment by Mathias Stearn [ 29/Aug/17 ]

The minor change is because GLE after db.eval() will only have an error if the eval throws. It will not automatically get the status of the last operation performed on db inside of the eval. However, since drivers (other than the shell) stopped exposing GLE helpers and db.eval() is deprecated, this should not affect many users.

Comment by Githook User [ 28/Aug/17 ]

Author:

{'username': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}

Message: SERVER-30735 Make DBDirectClient use its own LastError
Branch: master
https://github.com/mongodb/mongo/commit/a3a02da6327b4995a75912c4fde4022b089d4947

Generated at Thu Feb 08 04:24:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.