Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Remote Execute SQL Request

IP.com Disclosure Number: IPCOM000106100D
Original Publication Date: 1993-Sep-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 2 page(s) / 60K

Publishing Venue

IBM

Related People

Jordan, LE: AUTHOR [+4]

Abstract

In OS/2* Extended Edition 1.3, the implementation of Remote Execute SQL request is based on the concept of native SQLDA, which is the SQLDA generated by the database engine. The problem with the native SQLDA approach is twofold: first, an internal describe is issued for every Execute SQL request with output SQLDA. Second, since the server fetches data based on the native SQLDA, the requestor need to convert returned data from the native SQLDA data type to user SQLDA data type.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 55% of the total text.

Remote Execute SQL Request

      In OS/2* Extended Edition 1.3, the implementation of Remote
Execute SQL request is based on the concept of native SQLDA, which is
the SQLDA generated by the database engine.  The problem with the
native SQLDA approach is twofold: first, an internal describe is
issued for every Execute SQL request with output SQLDA.  Second,
since the server fetches data based on the native SQLDA, the
requestor need to convert returned data from the native SQLDA data
type to user SQLDA data type.

      For all Execute SQL requests with output SQLDA, the server
invokes a database engine function called internal describe.  What
the internal describe does is to get the column data type definitions
from the schema stored in the database.  An native output SQLDA is
generated by the internal describe function and returned back to the
server.  The server uses this native SQLDA to retrieve data from the
database.

      When the server finished retrieving data from the database, it
sends the native SQLDA and the output data back to the client.
However, since the native SQLDA might not be consistent with the user
output SQLDA.  The client needs to perform data type conversions on
the returned data.

The proposed approach follows the following steps:

1.  The client sends the user SQLDA along with the Execute SQL
    command to the server.
2.  The server uses this user SQLDA to get data from the database
    engine.
3.  The server sends the re...