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.

Sign up for GitHub

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

Jump to bottom

Request execution API changes - umbrella issue #978

Open

6 tasks

wprzytula opened this issue Apr 11, 2024 · 0 comments

Assignees

Labels

API-breaking API-stability

Milestone

Collaborator

wprzytula commented Apr 11, 2024

This is an umbrella issue to group all changes regarding the request execution API, as there are a number of them planned before the API gets stable.

Tasks

Beta Give feedback

Replace Query with a more fitting name #713 - we're currently planning to implement the Executable trait
Move set_timestamp out of Query/PreparedStatement #262 - necessarily consider this when implementing Executable
Internal reusable CQL statements should be prepared #417 - this needs to be resolved if we decide to forbid executing unprepared requests with values (which we want to, in order to make requests type-safe)
query_paged is a misleading name #940 - covered by Executable
Introduce BoundStatement #941 - solves multiple issues, e.g. Enhancement Proposal: Simplifying Token Calculation for High-Frequency Append-Log Style Operations #974
Provide an option to bind values to each separate statement in a batch #108 - possibly solved by Introduce BoundStatement #941
Options

The text was updated successfully, but these errors were encountered:

wprzytula added API-breaking API-stability labels

wprzytula added this to the 1.0.0 milestone

wprzytula self-assigned this

wprzytula mentioned this issue

Planned API breaking changes - umbrella issue #979

Open

avelanarius modified the milestones: 1.0.0, 0.15.0

wprzytula assigned Lorak-mmk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment