Fix issue when VersionedResult can lose first row of the data #79
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.
Part of #61
This PR fixes the issue which can occur when the method
getLatestVersion
of theHasVersion
typeclass peeks the first element of theVersionedBatch
.In this case the stateful
ResultSet
inside this class moves forward and the first row of the set is being lost.To avoid this issue, the
CanPeekHead
trait was added. The implementation of this trait saves the first row of theResultSet
if the head of theResultSet
was requested.Checklist
latest
commit.