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
options for handling non-persisted node upon assignment of an association #686
options for handling non-persisted node upon assignment of an association #686
Conversation
Sorry for sleeping on this. @cheerfulstoic this all good with you? I'd like to get that coverage back up over 98.5 so we can keep our 99%. :-D |
I have a few comments (also sorry for sleeping on it):
|
Gah, I never know how to read coveralls. It says that coverage on some files went up and some went down, but only |
@cheerfulstoic you are right. The hook is kinda overengineering on this place. But I'm not sure if saving a node upon assignment should be turned off by default. I would not expect this on the user's place, though I also would not expect it to fail. |
When I run specs, I get 7 failures with weird cypher queries like in #700, but there is no order clause.
|
Update your neo4j-core, I think that'll fix those failures. On Tuesday, March 10, 2015, Dieter Pisarewski notifications@github.com
|
Thanks Chris, that solved the problem. |
No description provided.