Factor out SelectResult => List[Row] helper into a public function
#5
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.
Currently, the only means by which to issue a SELECT query and operate on a high-level representation of the results is to use
Client.selectand provide a function to map over anyRows that are returned. In cases where one wants to e.g. perform some computation on the entire result set rather than on individual rows, they must useClient.fetch. Thus, they're forced to deal with the rawFields andDataRows, in most cases duplicating theprivate[this]conversion code in Client.scala.This change moves the
SelectResult => List[Row]conversion function into a new public function,SelectResult.toRowList, which can be used in conjunction withClient.fetchto issue one-shot SELECTs and operate on the entire result set.