CSO_DOC_QUEUE
This table refers to documents to be queued for processing.
Details
-
Schema: FUSION
-
Object owner: CSO
-
Object type: TABLE
-
Tablespace: Default
Primary Key
Name | Columns |
---|---|
CSO_DOC_QUEUE_PK |
RECORD_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
RECORD_ID | VARCHAR2 | 64 | Yes | RECORD_ID is a unique identifier, auto-generated by the Application code. | |
CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
FETCH_URL | VARCHAR2 | 1000 | Yes | FETCH_URL contains either an HTTP URI, or an IM structured URI used to determine the KB Articles this entry refers to. | |
PRIORITY | NUMBER | 11 | Yes | PRIORITY is an integer from 1 to 99 that will determine the order in which the entries are processed, with 1 being the highest priority. | |
ACTION | VARCHAR2 | 32 | Yes | ACTION is used to determine if this entry is meant for content updates, or content removal. Its value can be DELETE or CREATE_OR_UPDATE. | |
DATE_ADDED | TIMESTAMP | Yes | DATE_ADDED is the date and time that this particular entry was added to the queue. | ||
DATE_MODIFIED | TIMESTAMP | DATE_MODIFIED is the date and time that this entry was updated, if at all. Typically this is updated if the priority is increased. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
CSO_DOC_QUEUE_N1 | Non Unique | Default | FETCH_URL |
CSO_DOC_QUEUE_N2 | Non Unique | Default | PRIORITY, DATE_ADDED |
CSO_DOC_QUEUE_PK | Unique | Default | RECORD_ID |