[SERVER-44173] Rename the 'wasGlobalLockTakenForWrite()' function in LockState Created: 23/Oct/19 Updated: 27/Oct/23 Resolved: 20/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
The name of this function could be improved as it is currently misleading. For example, I took a DBLock in MODE_IX and 'wasGlobalLockTakenForWrite()' returned true, and I thought to myself that I never took a GlobalLock in MODE_X. |
| Comments |
| Comment by William Olaleye [ 24/Oct/19 ] |
|
Suggestion is to add a comment to the header for this function with an explanation. |