[SERVER-54910] WTRecordStore setKey should take key by pointer to avoid usage errors Created: 03/Mar/21 Updated: 29/Oct/23 Resolved: 03/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2021-03-08 |
| Participants: |
| Description |
|
The setKey function accepts a key by const reference, but this is problematic because the WT set_key API requires the key to exist after the API call. To avoid misuse of the API by callers passing in a temporary, require callers to pass a key by pointer. |
| Comments |
| Comment by Githook User [ 03/Mar/21 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |