[DERBY-6082] Investigate if openOnServer_ field in org.apache.derby.client.am.Statement is still needed.

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.10.1.1
• Component/s: Network Client
• Assignee: Dyre Tjeldvoll
• Reporter: Mamta A. Satoor
• Created: 20/Feb/13 16:42
• Updated: 21/Jan/15 00:23
• Resolved: 07/Nov/13 07:48

Description

While working on DERBY-6053, there was some discussion over openOnServer_ field in org.apache.derby.client.am.Statement. This field has following comment in Statement class
// This means a DERBY server-side section for this statement is in the prepared state.
// A client-side jdbc statement may remain open across commits (openOnClient=true),
// but the server-side DERBY section moves to an unprepared state (openOnServer=false) across commits,
// requiring an implicit re-prepare "under the covers" by the driver.
// Unprepared jdbc query statements still have prepared sections on the server.
// This openOnServer_ only has implications for preparedstatement

Kathey commented following on that field in DERBY-6053
*******************************************************************************
I do not think that comment is true about statements not staying prepared across commits.
If I prepare a statement and execute it twice with a commit in between from client, I do not see a reprepare in the derby.log . I think maybe the openOnServer_ property may be a relic of some place or time in the original code base when that was true.
*******************************************************************************

Issue Links

• is related to: DERBY-4531 Client setCharacterStream closes its Reader argument stream in finalizer
• is related to: DERBY-6066 Client should use a prepared statement rather than regular statement for Connection.getTransactionIsolation