[SERVER-3930] Profiler shouldn't use 0 as default value Created: 22/Sep/11  Updated: 11/Jul/16  Resolved: 02/Dec/11

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: None
Fix Version/s: 2.1.0

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

0 is a valid value for things like nscanned and nreturned



 Comments   
Comment by auto [ 02/Dec/11 ]

Author:

{u'login': u'', u'name': u'milkie', u'email': u'milkie@SERVER02.(none)'}

Message: SERVER-3930 – record profiled statistics even if they are zero

Made profile member variables' initial values "-1" so that when they are updated with a value of 0, they will be
entered into the system.profile collection.
Changed keyUpdates to be signed so that it can be initialized to -1 like all the other integer values in the OpDebug class.
Branch: master
https://github.com/mongodb/mongo/commit/4c58b9c182d1c8b23591ae9d9d1d5260acfc36a4

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