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

Add in a prepared statement cache #51

Open
berryware opened this issue Jun 30, 2020 · 0 comments
Open

Add in a prepared statement cache #51

berryware opened this issue Jun 30, 2020 · 0 comments
Assignees

Comments

@berryware
Copy link
Collaborator

berryware commented Jun 30, 2020

While cpo uses prepared statements, it does not cache these prepared statements for re-use. Caching prepared statements will reduce db roundtrips and shave time off the queries.

The cache will need to be maintained at the connection level for jdbc and session level for cassandra. We will need to make sure that clearParameters() is called between uses and need to make sure the cache does not cause any problems with connection pooling.

The cassandra driver has been whining that the prepared statements are not being re-used.

This cache is dependent on the cache being cleaned up and made more generic #6

@berryware berryware self-assigned this Jun 30, 2020
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