Release 10.1A: OpenEdge Development:
Java Open Clients

> ## Passing temp-tables as ProDataGraph parameters

> OpenEdge supports passing an individual Progress 4GL temp-table parameter as a `ProDataGraph`, similar to a ProDataSet. This temp-table `ProDataGraph` must contain a single `ProDataObject` collection specified by a single `ProDataObjectMetaData` that maps to the schema of the temp-table. Of course, there is no `ProDataRelationMetaData` in a temp-table `ProDataGraph` and it provides no change tracking.

> Similar to a ProDataSet, OpenEdge automatically builds the appropriately formed `ProDataGraph` for a `TABLE` or `TABLE-HANDLE` parameter passed as `OUTPUT`. You must also prepare a `ProDataGraph` mapped to temp-table parameters passed as `INPUT` or `INPUT-OUTPUT` in a manner similar to a `ProDataGraph` mapped to ProDataSet parameters. In all other ways, programming with a temp-table `ProDataGraph` is identical to programming with a ProDataSet `ProDataGraph` that has no data-relations and no change tracking enabled (`getBImageFlag()` on the `ProDataObjectMetaData` returns `false`).

> So, for information on passing a temp-table `ProDataGraph` as `OUTPUT`, see the "Passing a ProDataGraph as OUTPUT" section, and on passing a temp-table `ProDataGraph` as `INPUT` or `INPUT-OUTPUT`, see the "Passing a ProDataGraph as INPUT or INPUT-OUTPUT" section.

> Note: The `ProDataGraph` is the default mechanism for passing temp-table parameters to a Java Open Client. An alternative mechanism for passing temp-table parameters is available using the SQL `ResultSet` interface. For a comparison of these mechanisms for passing temp-table parameters, see the sections on passing temp-tables and ProDataSets in Chapter 4, " Passing Parameters."

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095