Fall back to GRAPH.QUERY when GRAPH.RO_QUERY
is not available.
#124
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.
Fix: #123
GRAPH.RO_QUERY
is unavailable in older versions. So fallback to GRAPH.QUERY when the command is not found.While there's a way to always use
GRAPH.QUERY
by settingread_only
toFalse
, methods that try to fetch the labels and other properties are hardcoded toTrue
.While we can have a param
read_only
to the above methods, introducing the same would actually change many methods that is calling the above methods directly or indirectly to haveread_only
param and that's huge.So checking for unknown command while executing the query makes it a simple fix.