[Fix] Allow CallProcedure to specify mode #75
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 PR addresses #74.
There are few possible solutions to this so I'm happy to address it in a different way if required.
Possible solutions:
(Current one)
g.CallProcedure
takes an additionalmode
parameter that tells it whether to run RW or RO query. This however requires the knowledge of what procedure mode is. It can be easily retrieved from the instance by runningCALL dbms.procedures()
(in read-only mode) which will show the mode required for a specific procedure.g.CallProcedure
can build available procedures lookup by callingdbms.procedures()
internally and automatically setting up the mode required for a given procedure call. This however has a downside of additional call for eachg.CallProcedure
invocation. I've got that solution ready to go if there is preference for it.