-
Notifications
You must be signed in to change notification settings - Fork 54
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
Calling methods on nodes returned by CypherQuery is awkward #60
Comments
Right now Neoism doesn't distinguish between a Check out |
hm, got this problem today too. I was querying for a result struct with a node in it, see:
so far so good, got the node with all the data, but calling
after setting |
I agree, it would be better if Neoism could set this variable automagically. However please see my comment above as to why doing this is decidedly non-trivial. If you would like to take a shot implementing this behavior, I will be very happy to accept the Pull Request. |
+1 also hit this today, the documentation example returning a Node object is misleading. Otherwise thanks for a really useful lib! :) |
Glad you enjoy Neoism! Please feel free to update the docs in a way you think would clarify the current behavior and make things easier for other users. I will be happy to accept the PR. :) |
I was stuck for a few hours today trying to figure out what I was doing wrong until the helpful guys at StackOverflow pointed me in the right direction. See here for details and example code:
http://stackoverflow.com/questions/27405705/golang-neoism-calling-methods-of-objects-returned-by-query-leads-to-panic
It turns out that you have to initialize the Db property of nodes returned by CypherQuery manually before you can call methods like SetProperty. Of course, you can do that once you are aware it has to be done, but it feels very awkward. Is there a more intuitive way of handling this?
The text was updated successfully, but these errors were encountered: