[DERBY-3313] JDBC client driver statement cache

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.4.2.0
• Component/s: JDBC, Network Client
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 10/Jan/08 16:22
• Updated: 02/May/13 02:29
• Resolved: 10/Jul/08 11:08

Description

A statement cache in the JDBC client driver will help increase performance in certain scenarios, for instance some multi-tier systems using connection pooling.
Please consult the comments and documents attached to this issue for more information.

Issue Links

• depends upon: DERBY-3192 Cache session data in the client driver
• relates to: DERBY-3596 Creation of logical connections from a pooled connection causes resource leak on the server
• relates to: DERBY-3779 Add client side JDBC statement pool documentation

Sub-Tasks

• JDBC statement cache implementation: Closed
• Add 'maxStatements' property to ClientConnectionPoolDataSource: Closed
• Introduce a caching logical connection and logical prepared statement in the client driver: Closed
• Extend client JDBC object factory with methods to create objects required for statement pooling: Closed
• Run suites.All with statement pooling enabled and classify the problems occurring: Closed
• Determine and implement a proper procedure for resetting a prepared statement for reuse in a statement pool: Closed
• Enable statement pooling in the client JDBC driver: Closed