Why the Connector/J statement.setPoolable(false) only works for server-side cache and not the client one
Posted by: Vlad MIhalcea
Date: September 16, 2015 08:58AM

JDBC defines the statement.setPoolable(false) method which only works for server-side cache and not the client.

Why is it like this. Shouldn't it be a way to manually control which statements go into the cache and which are skipped. This way, we could store only frequently used queries and avoid some occasional ones to get into the cache.

Options: ReplyQuote


Subject
Written By
Posted
Why the Connector/J statement.setPoolable(false) only works for server-side cache and not the client one
September 16, 2015 08:58AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.