Github user sandhyasun commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/1225#discussion_r138132569
--- Diff: core/conn/odbc/src/odbc/nsksrvrcore/srvrothers.cpp ---
@@ -6489,6 +6506,31 @@ odbc_SQLSrvr_ExtractLob_sme_(
exception_->u.SQLError.errorList._buffer =
QryLobExtractSrvrStmt->sqlError.errorList._buffer;
exception_->u.ParamError.ParamDesc =
SQLSVC_EXCEPTION_EXECUTE_FAILED;
}
+
+ IDL_long_long zeroValue = 0;
+ snprintf(LobExtractQuery, sizeof(LobExtractQuery), "EXTRACT
LOBTOBUFFER(LOB'%s', LOCATION %Ld, SIZE %Ld)", lobHandle, (Int64)lobDataValue,
&zeroValue);
+
+ retcode = QryLobExtractSrvrStmt->ExecDirect(NULL,
LobExtractQuery, EXTERNAL_STMT, TYPE_CALL, SQL_ASYNC_ENABLE_OFF, 0);
+
--- End diff --
So who is the caller of this with 'zero' value. It needs to be triggered by
the JDBC driver. But I am not seeing any changes in the driver ? The
'zeroLength' can be passed in only when the application decides to close the
resultset or the connection. It cannot be called soon after the extract
statement is executed. Can you clarify ?
---
