The driver automatically maps Oracle Service Cloud data source objects and fields to tables and columns the first time it connects to an Oracle Service Cloud instance. The driver maps standard and custom objects and includes relationships defined between objects. You can use the getPrimaryKey(), getExportedKeys(), and getImportedKeys() methods to report relationships among objects.

Standard and custom objects are mapped to corresponding standard and custom tables. Every standard and custom object comes with a set of fields by default. These fields are collectively referred to as audit columns. By default, the driver includes the audit columns in table definitions when mapping objects to tables. If you do not want your application to see the audit columns, then you may use the ConfigOptions connection property to exclude audit columns. For details, see ConfigOptions.

The driver maps standard objects into the RIGHTNOW schema; however, custom objects are handled differently. Oracle Service Cloud custom objects are created in packages through the Oracle Service Cloud user interface. When mapping custom objects from the data model to the relational model, the driver exposes the different namespaces for the packages as different schemas within the relational model. For example, if you have created an object called bar in the foo namespace, the driver will expose a schema called FOO that contains a table called BAR. To access this table, the application would have to fully qualify it as FOO.BAR or change the current schema using ALTER SESSION SET CURRENT_SCHEMA = FOO.

The driver can map system fields to columns within a table so that they can be easily identified. If you want the driver to change the names of system columns, make sure the MapSystemColumnNames key of the ConfigOptions connection property is set to 1. For details, see ConfigOptions.