You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, rows result are eagerly deserialized to Vec<Row>. We can definitely improve that.
We do not need to store Vec<CassRow> in CassRowsResult. This because there is no API function that returns a row at given index. We only need to deserialize the first row (cass_result_first_row) and store it in CassRowsResult.
We do not need to (and should not) deserialize values to CqlValue. Because of this, we are not able to implement cass_value_get_bytes, which should return serialized value. We should rather deserialize to some partially-serialized type, which contains the bytes and information about the CQL column type.
The content you are editing has changed. Please copy your edits and refresh the page.
Currently, rows result are eagerly deserialized to
Vec<Row>
. We can definitely improve that.Vec<CassRow>
inCassRowsResult
. This because there is no API function that returns a row at given index. We only need to deserialize the first row (cass_result_first_row
) and store it inCassRowsResult
.CqlValue
. Because of this, we are not able to implementcass_value_get_bytes
, which should return serialized value. We should rather deserialize to some partially-serialized type, which contains the bytes and information about the CQL column type.Tasks
The text was updated successfully, but these errors were encountered: