-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better handling of cypher query results #49
Comments
Hi @DenisVuyka Generally I tried keeping it as close to the original response from Neo4j since I didn't know how they develop their language. It's a good idea though; will investigate on how that can be implemented without breaking backwards compatibility. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now when 'cypherQuery' call results in a multi-dimensional array that requires knowing all positions of the data in the result set. For example when executing "[...] RETURN user, roles" I would ideally expect accessing data in the callback via some getters, similar to the following: "result.data[0].user" or "result.data[1].roles" without the need using "result.columns" for that. This should greatly simplify scenarios related to raw cypher query calls.
The text was updated successfully, but these errors were encountered: