keys should never return null #101
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For cypher statements that has no results, `resultCurson.keys` should return an empty list rather than `null`.
| @@ -78,4 +78,34 @@ public void shouldBeAbleToOpenTxAfterPreviousIsClosed() throws Throwable | |||
| // Then we should've gotten a transaction object back | |||
| assertNotNull( tx ); | |||
| } | |||
|
|
|||
| @Test | |||
| public void shouldNotBeAbleToUseSessionWhileOngoingTransaction() throws Throwable | |||
There was a problem hiding this comment.
These two tests has nothing to do with the fix, I just thought they were missing.
jakewins
added a commit
that referenced
this pull request
Dec 18, 2015
keys should never return null
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For cypher statements that has no results,
resultCurson.keysshould returnan empty list rather than
null.