SQL ResultSet streaming and call-back sequence
- Last Updated: January 16, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
Java Open Client support for TABLE and TABLE-HANDLE parameters depends
on a call-back mechanism used by both the client application and
the proxy code. Therefore, either the client application or the
proxy always must request data from the sender, rather than having
the sender set or send the data. As a result, the client application
calls back to the proxy for output parameters, and the proxy calls
back to the client application for input parameters.
The following table shows how the call-back sequence works when
passing an INPUT TABLE or TABLE-HANDLE parameter.
| Client application | Proxy |
|---|---|
|
– |
| – |
|
The following table shows how the call-back sequence works when
passing an OUTPUT TABLE or TABLE-HANDLE parameter.
| Client application | Proxy |
|---|---|
|
– |
| – |
|
|
– |
The following table shows how the call-back sequence works when
passing an INPUT-OUTPUT TABLE or TABLE-HANDLE parameter.
| Client Application | Proxy |
|---|---|
|
– |
| – |
|
|
– |
The input ResultSet object is an object written
by the Java client application. This also can be a standard ResultSet object
available as the result of a SQL query (a java.sql.ResultSet).
In contrast, the output ResultSet object always
is provided by the generated proxy.