Continuously blocking query result data for a remote query
Continuously blocking query result data for a remote query is provided. Included is: creating a first connection, using a communications network, between a database server and a client. At least one secondary connection is created, using the communications network, between the database server and the client, based on the database server supporting a continuous block fetch protocol. Using the at least one secondary connection, the database server receives at least one cursor-based fetch query. The database server generates continuous blocks of result data, based on the received at least one cursor-based fetch query and sends to the client, using the at least one secondary connection, the continuous blocks of result data.
1. A method for continuously blocking query result data for a remote query comprising:
creating a first connection, using a communications network, between a database server and a client;
creating a plurality of secondary connections, using the communications network, between the database server and the client, based on the database server supporting a continuous block fetch protocol, wherein each of the plurality of secondary connections corresponds to a cursor-based fetch query, and wherein the plurality of secondary connections and the first connection belong to a same transaction and share session data of the same transaction;
receiving from the client, at the database server, the cursor-based fetch query using a corresponding secondary connection;
generating, by the database server, continuous blocks of result data, for the cursor-based fetch query;
sending the continuous blocks of result data to the client, using the secondary connection corresponding to the cursor-based fetch query, wherein the database server sends the continuous blocks of result data until the cursor-based fetch query is exhausted, and wherein the database server adheres to network congestion protocols in pacing the sending the continuous blocks of result data; and
closing the corresponding secondary connection when the cursor-based fetch query is exhausted.
2. The method of claim 1 , wherein the client creates one secondary connection with the database server for each cursor-based fetch query.
3. The method of claim 1 , wherein the database server continuously transmits query result blocks to the client, using the secondary connection corresponding to the cursor-based fetch query.
4. The method of claim 1 , wherein the database server sends session data to the client, based on the session data being changed in the transaction, wherein the session data is synchronized across the first connection and the plurality of secondary connections, and wherein the session data includes global variables shared by the same transaction.
5. The method of claim 1 , wherein the database server sends session data to the client upon creating the secondary connection.
6. A computer program product for continuously blocking query result data for a remote query comprising:
a computer readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising:
creating a first connection, using a communications network, between a database server and a client;
creating a plurality of secondary connections, using the communications network, between the database server and the client, based on the database server supporting a continuous block fetch protocol, wherein each of the plurality of secondary connections corresponds to a cursor-based fetch query, and wherein the plurality of secondary connections and the first connection belong to a same transaction and share session data of the same transaction;
receiving from the client, at the database server, the cursor-based fetch query using a corresponding secondary connection;
generating, by the database server, continuous blocks of result data, for the cursor-based fetch query;
sending the continuous blocks of result data to the client, using the secondary connection corresponding to the cursor-based fetch query, wherein the database server sends the continuous blocks of result data until the cursor-based fetch query is exhausted, and wherein the database server adheres to network congestion protocols in pacing the sending the continuous blocks of result data; and
closing the corresponding secondary connection when the cursor-based fetch query is exhausted.
7. The computer program product of claim 6 , wherein each secondary connection remains open, based on the database server continuously transmitting query results to the client;
and wherein the client fetches query result blocks from any open secondary connection.
8. The computer program product of claim 6 , wherein the database server continuously transmits query result blocks to the client, using the secondary connection corresponding to the cursor-based fetch query.
9. The computer program product of claim 6 , wherein the database server sends session data to the client, based on the session data being changed in the transaction, wherein the session data is synchronized across the first connection and the plurality of secondary connections, and wherein the session data includes global variables shared by the same transaction.
10. A computer system for continuously blocking query result data for a remote query comprising one or more processors, one or more computer-readable storage devices, and a plurality of program instructions stored on at least one of the one or more storage devices for execution by at least one of the one or more processors, the plurality of program instructions comprising:
a computer readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising:
creating a first connection, using a communications network, between a database server and a client;
creating a plurality of secondary connections, using the communications network, between the database server and the client, based on the database server supporting a continuous block fetch protocol, wherein each of the plurality of secondary connections corresponds to a cursor-based fetch query, and wherein the plurality of secondary connections and the first connection belong to a same transaction and share session data of the same transaction;
receiving from the client, at the database server, the cursor-based fetch query using a corresponding secondary connection;
generating, by the database server, continuous blocks of result data, for the cursor-based fetch query;
sending the continuous blocks of result data to the client, using the secondary connection corresponding to the cursor-based fetch query, wherein the database server sends the continuous blocks of result data until the cursor-based fetch query is exhausted, and wherein the database server adheres to network congestion protocols in pacing the sending the continuous blocks of result data; and
closing the corresponding secondary connection when the cursor-based fetch query is exhausted.
11. The computer system of claim 10 , wherein each secondary connection remains open, based on the database server continuously transmitting query results to the client; and wherein the client fetches query result blocks from any open secondary connection.
12. The computer system of claim 10 , wherein the database server continuously transmits query result blocks to the client, using the secondary connection corresponding to the cursor-based fetch query.
13. The computer system of claim 10 , wherein the database server sends session data to the client, based on the session data being changed in the transaction, wherein the session data is synchronized across the first connection and the plurality of secondary connections, and wherein the session data includes global variables shared by the same transaction.
14. The computer system of claim 10 , wherein the database server sends session data to the client upon creating the secondary connection.