This section describes schema level configuration override feature.
The schema level configuration override feature provides a mechanism to override configuration properties for a REST enabled schema. This allows authorized database users to customize Oracle REST Data Services (ORDS) on the fly. For example, a database user can use this mechanism to enable or disable an optional feature. Only a predefined subset of database schema level configurations can be overridden, global configurations cannot be overridden.
4.1 Features of Schema Level Configuration Override
This section lists the features of schema level configuration override.
- Database users can override the configuration property for their schema with the ords PL/SQL API.
- Database administrator can override the configuration property for any schema in the database with our ords_admin PL/SQL API.
- The configuration value is cached for 10 mins. You must wait for 10 minutes before the new value becomes effective.
4.2 Overidable Configuration Properties
This section lists the overidable configuration properties.
Table 4-1 Overidable Configuration Properties
|Key||Descrption||Scope||Setting Override Value|
||Specifies whether the REST-Enabled SQL service is active. REST-
Enabled SQL is a prerequisite for SDW or Database Actions. SDW is
disabled if the value is set to
||Specifies whether the Database Actions feature is active.||Schema||
||Specifies whether the error responses include stack trace.||Schema||
4.3 Use Cases
This section shows some use cases for using the schema level configuration override feature.
Table 4-2 Use Cases of Schema Level Configuration Override feature
|An Autonomous Database user wants to debug their ORDS REST Services.||The database user sets the property to
|Administrator wants a REST-Enabled schema but not have a REST-Enabled SQL.||The administrator sets the property to
|Administrator wants to completely disable SDW for a database.||The administrator sets the property for every schema as shown in the
|REST-Enabled schema wants to clear a property value that was previously set.||The database user runs the following
4.4 Scope and Visibility Matrix
This section describes how to configure the visibility and the scope for the database and schema users.
Table 4-3 Scope and Visibility Matrix