OpenEdge Data Management: DataServer for Microsoft SQL Server

RDBMS Stored Procedure Details
3–36
FIELD tRecid AS ROWID /* must be changed to ROWID type */
FIELD tRECID_ident AS INTEGER.
If the table uses computed-column PROGRESS_RECID option, then ttCustomer
temp-table definition should be:
DEFINE TEMP-TABLE ttCustomer LIKE Sports.Customer
FIELD tRecid AS ROWID /* Must be changed to ROWID type */
FIELD tRECID_ident AS INT64
FIELD tRECID_alt as INT64.
• The TEMP-TABLE must be defined to the ProDataSet. The following line excerpted from
Example 3–26 shows this definition:
DEFINE DATASET dsCustomer FOR ttCustomer.
• The technique, demonstrated in Example 3–26, does not change the default behavior of
the ROWID function, but provides a mechanism for the ROWID value to be stored along side
its corresponding result rows; therefore, using the ROWID value to access database rows is
unconventional with respect to the normal, or more typical, association between ROWID and
a database table row. The following code demonstrates this difference.
Default use of ROWID function on a record buffer, as excerpted from Example 3–26:
FIND FIRST Customer WHERE Customer.CustNum = 1 NO-LOCK.
rid-1 = ROWID(Customer).
In contrast, the following code excerpt from Example 3–26, demonstrates an alternative
use of the ROWID value with a temp-table:
FIND FIRST Customer WHERE Customer.CustNum = 1 NO-LOCK.
rid-2 = ttCustomer.tRecid.
Additional ProDataSet support
As previously demonstrated in Example 3–26, the LOAD-RESULT-INTO functionality provides a
very fast and efficient way to populate the temp-table(s) of a ProDataSet Object.
Example 3–27, a two-part example, builds on the techniques demonstrated in Example 3–26,
but shows the ProDataSet object BEFORE-FILL procedure can be modified to provide a single
ProDataSet data access object that can be used against native OpenEdge or against MS SQL
Server and other DataServer data sources.