LOBs: One of Two Locator-Based Problems.
First, the situation:
Connection has AUTOCOMMIT enabled (true).
The Application Issues a CALL statement to a procedure, one of whose OUTPUT parameters is a LOB.
PROBLEM/QUESTION: By what rationale is it justified for that OUTPUT parameter to be of any use to the calling application? By rights, with an exception for the case where the CALLed routine returns a ResultSet, the Locator that underlies the LOB should be freed in association with the completion of the execution of the CALL, when the transaction autocommits.
###@###.### 2004-02-02
First, the situation:
Connection has AUTOCOMMIT enabled (true).
The Application Issues a CALL statement to a procedure, one of whose OUTPUT parameters is a LOB.
PROBLEM/QUESTION: By what rationale is it justified for that OUTPUT parameter to be of any use to the calling application? By rights, with an exception for the case where the CALLed routine returns a ResultSet, the Locator that underlies the LOB should be freed in association with the completion of the execution of the CALL, when the transaction autocommits.
###@###.### 2004-02-02