There are few possible solutions to this so I'm happy to address it in a different way if required.
Possible solutions:
1) (Current one) g.CallProcedure takes an additional mode 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 running CALL dbms.procedures() (in read-only mode) which will show the mode required for a specific procedure.
2) g.CallProcedure can build available procedures lookup by calling dbms.procedures() internally and automatically setting up the mode required for a given procedure call. This however has a downside of additional call for each g.CallProcedure invocation. I've got that solution ready to go if there is preference for it.
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:
1) (Current one)
g.CallProceduretakes an additionalmodeparameter 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.2)
g.CallProcedurecan 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.CallProcedureinvocation. I've got that solution ready to go if there is preference for it.