Closed iconara closed 10 years ago
There's a LazyQueryResult
in the protocol_v2 branch, and prepared statement results are now lazily decoded.
To clarify, this doesn't mean that frames are decoded in a streaming way, they are still buffered in memory, it's just that this chunk of memory is parsed in the client thread and not in the IO thread.
I think this is sufficiently implemented as of #74. Prepared statement results are lazily deserialized and you can page over large result sets. Streaming would be great, but that's for another release.
As it is all frame deserialization happens in the IO thread, which is find for small frames, but for big results it's probably not a good idea.
QueryResult
/RowsResultResponse
should be lazy and not deserialize anything until it's actually used). This would make it easier to support streaming in the future.