chore: refactored saved query id parameter to always expect int64 #792
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updated usage of the
saved_query.id
field to always expect int64. This includes reading the value in from the API handler and passing through to the database functions.Motivation and Context
This PR addresses: BED-4698
Light refactoring to make
savedQueryID
usages more consistent overall, including always treating as an int64 and using the same naming conventions everywhere.How Has This Been Tested?
Existing tests pass, no functional changes
Screenshots (optional):
Types of changes
Checklist: