ABL temp-table to ADO.NET DataTable mappings

The ABL temp-table maps closely to an ADO.NET DataTable. The temp-table can be passed in a remote ABL procedure or user-defined function, between .NET and the AppServer, as a parameter or as part of a ProDataSet parameter (see ABL temp-table to ADO.NET DataTable mappings). For static temp-table parameters, ProxyGen creates extended ADO.NET DataTable classes for each unique temp-table definition. For dynamic temp-tables, ProxyGen uses the standard ADO.NET DataTable class for the parameters.

In ABL, you can define a temp-table as being LIKE a database table, and you can add fields of any type to this definition, or you can define the table as a set of fields independent of any particular database table. You can also define indexes to manage large sets of data efficiently.

An ADO.NET DataTable shares all of these characteristics. Thus, OpenEdge supports:

To support the mapping of ABL temp-tables to ADO.NET DataTables, OpenEdge establishes detailed correspondences between temp-table components and similar ADO.NET objects. This includes the mapping of such elements as temp-table field data types and temp-table component attributes. For more information on the mapping of temp-table field data types, see Passing TABLE and TABLE-HANDLE parameters. The following sections describe the mapping of temp-table components and their attributes: