Unique keys identifying the columns that are application-level (non-dictionary) children of the sensitive column.
The name of the application associated with the sensitive column. It's useful when the application name is different from the schema name. Otherwise, it can be ignored.
The composite key groups to which the sensitive column belongs. If the column is part of a composite key, it's assigned a column group. It helps identify and manage referential relationships that involve composite keys.
The name of the sensitive column.
The data type of the sensitive column.
Unique keys identifying the columns that are database-level (dictionary-defined) children of the sensitive column.
The estimated number of data values the column has in the associated database. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The unique key that identifies the sensitive column. It's numeric and unique within a sensitive data model.
Details about the current state of the sensitive column.
The current state of the sensitive column.
The database object that contains the sensitive column.
The type of the database object that contains the sensitive column.
Unique keys identifying the columns that are parents of the sensitive column. At present, it tracks a single parent only.
The type of referential relationship the sensitive column has with its parent. NONE indicates that the sensitive column does not have a parent. DB_DEFINED indicates that the relationship is defined in the database dictionary. APP_DEFINED indicates that the relationship is defined at the application level and not in the database dictionary.
Original data values collected for the sensitive column from the associated database. Sample data helps review the column and ensure that it actually contains sensitive data. Note that sample data is retrieved by a data discovery job only if the isSampleDataCollectionEnabled attribute is set to true. At present, only one data value is collected per sensitive column.
The database schema that contains the sensitive column.
The OCID of the sensitive data model that contains the sensitive column.
The OCID of the sensitive type associated with the sensitive column.
The source of the sensitive column. DISCOVERY indicates that the column was added to the sensitive data model using a data discovery job. MANUAL indicates that the column was added manually.
The status of the sensitive column. VALID means the column is considered sensitive. INVALID means the column is not considered sensitive. Tracking invalid columns in a sensitive data model helps ensure that an incremental data discovery job does not identify these columns as sensitive again.
The date and time, in the format defined by RFC3339, the sensitive column was created in the sensitive data model.
The date and time, in the format defined by RFC3339, the sensitive column was last updated in the sensitive data model.
A sensitive column is a resource corresponding to a database column that is considered sensitive. It's a subresource of sensitive data model resource and is always associated with a sensitive data model. Note that referential relationships are also managed as part of sensitive columns.