Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lazy deserialization #216

Open
2 tasks
muzarski opened this issue Dec 9, 2024 · 0 comments
Open
2 tasks

Lazy deserialization #216

muzarski opened this issue Dec 9, 2024 · 0 comments
Assignees
Milestone

Comments

@muzarski
Copy link
Collaborator

muzarski commented Dec 9, 2024

Currently, rows result are eagerly deserialized to Vec<Row>. We can definitely improve that.

  1. 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.
  2. 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.

Tasks

Preview Give feedback
  1. muzarski
  2. muzarski
@muzarski muzarski added this to the 0.4 milestone Dec 9, 2024
@muzarski muzarski self-assigned this Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant