CSO_CONTENT_LOCALE
This table will be populated from cso_content_text. It will reduce lookups to cso_content_text for Answer ID specific data. A new answer ID will be created whenever there is a new content ID, locale ID combination. The KM article aggregation job will check for new combinations and populate this table on an hourly basis.
Details
-
Schema: FUSION
-
Object owner: CSO
-
Object type: TABLE
-
Tablespace: Default
Primary Key
| Name | Columns |
|---|---|
|
CSO_CONTENT_LOCALE_PK |
ANSWER_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
| ANSWER_ID | NUMBER | Yes | A way to uniquely identify an article by locale ID and content ID. | ||
| DOCUMENT_ID | VARCHAR2 | 50 | This is the document ID of the article. | ||
| CONTENT_ID | VARCHAR2 | 32 | This is the reference to the article in the CSO_CONTENT table. | ||
| LOCALE_ID | VARCHAR2 | 32 | This is the reference to the locale in CSO_LOCALE table. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| CSO_CONTENT_LOCALE_PK | Unique | Default | ANSWER_ID |