skip to main content
Using the driver : Using connection properties : Mapping properties
  

Try DataDirect Drivers Now

Mapping properties

The following table summarizes connection properties involved in mapping the REST API data model to a local schema map used to support SQL queries.
Table 8. Mapping properties
Property
Characteristic
Determines whether the driver creates the internal files required for a relational map of the native data when establishing a connection.
If set session, the driver uses memory to store the internal configuration information and relational map of native data. A REST file is not created when this value is specified. After the session, the view is discarded.
If set to forceNew, the driver deletes the current REST file, internal configuration files, and relational map in the location specified by the SchemaMap property and creates a new set at the same location.
If set to notExist, the driver uses the current REST file, internal files, and relational map in the location specified by the SchemaMap property. If the files do not exist, the driver creates them.
The default is session.
Specifies whether the driver automatically refreshes the map of the data model when a user connects to a REST service.
If set to true, the driver automatically refreshes the map of the data model when a user connects to a REST service. Changes to objects since the last time the map was generated will be shown in the metadata.
If set to false, the driver does not refresh the map of the data model when a user connects to a REST service.
The default is true.
Specifies the directory where the internal configuration files, REST file, and the relational map of the REST data model are written. The driver looks for these files when connecting to a REST service. If the file does not exist, the driver creates one.
The default varies based on your environment:
For Windows:
application_data_folder\Local\Progress\DataDirect\AutoREST_Schema\
For UNIX/Linux:
~/progress/datadirect/AutoREST_schema/
Specifies the host name portion of the URL endpoint to which you send requests. This property allows you to define endpoints without storing the host name component in the REST file property.
Determines the name of the table your endpoint maps to when specifying an endpoint using the Sample property. If the table already exists, including those defined in an input REST file, the driver will resample the endpoint associated with this table and add any newly discovered columns to the relational view.