[DERBY-3438] Allow SQL query text to be null in StatementKey

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.4.1.3
• Component/s: JDBC, Network Client
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 20/Feb/08 13:43
• Updated: 29/Feb/08 13:22
• Resolved: 26/Feb/08 14:02

Description

Because the SQL isn't checked before the cache is queried, StatementKey should allow the SQL query text to be null.
This simplifies handling this exceptional situations, hopefully without complications.
What will happen is, the cache is queried, null is returned (no match) and then prepare will fail in the driver. Because the statement is never prepared, it will never be inserted into the cached, nor (incorrectly) fetched from the cache in the first step.

Of course, one could also explicitly check for null in either the Logical(Prepared|Callable)Statement[40], StatementKeyFactory or StatementCacheInteractor.
However, the proposed change is small, isolated to one class and makes the exceptional case be handled by the normal code path.

Issue Links

• is related to: DERBY-3324 JDBC statement cache implementation