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
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