[DERBY-3324] JDBC statement cache implementation

• Type: Sub-task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.4.1.3
• Component/s: Network Client
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 17/Jan/08 16:59
• Updated: 21/Feb/08 10:20
• Resolved: 08/Feb/08 10:56

Description

Implement a cache for storing JDBC prepared statement objects.
The cache will be responsible for holding free prepared statement objects that can be reused, and also to throw away objects if the cache grows too big.
All objects in the cache must belong to the same physical connection, but they can be reused across logical connections obtained from a single physical connection in a connection pool.

This component is probably a candidate for code sharing between the client and the embedded driver. Sharing will not be part of this issue.

Issue Links

• is depended upon by: DERBY-3326 Introduce a caching logical connection and logical prepared statement in the client driver
• is depended upon by: DERBY-3328 Extend client JDBC object factory with methods to create objects required for statement pooling
• relates to: DERBY-3438 Allow SQL query text to be null in StatementKey