make QueuedQuery.Fn property public, closes #1878 #1996
Merged
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.
This commit fixes the overlook of the #1886 where
QueuedQuery.SQL
andQueuedQuery.Arguments
properties were exposed.And if for
SQL
andArguments
we had an opportunity to use reflection, forQueuedQuery.fn
it's impossible.One more benefit exposing
QueuedQuery.Fn
for developers is the ability to execute batched functions without knowing the kind of a queued query and mandatory callingBatchResults.Close()
, e.g.