Columns
| Column | Type | Size | Nulls | Auto | Default | Children | Parents | Comments | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
| submission_matching_detail_id | serial | 10 | √ | nextval('nrfc.submission_matching_detail_id_seq'::regclass) |
|
|
Incremental id generated for a submission matching detail of a client. |
||||
| submission_id | int4 | 10 | null |
|
|
Incremental id generated for a submission of a client. |
|||||
| matching_fields | jsonb | 2147483647 | √ | null |
|
|
A JSON object provides information about matches found in the existing database. The matches can result from fuzzy search, like matching a name pattern, or from exact equality, such as matching incorporation number or good standing status. |
||||
| confirmed_match_status_ind | varchar | 1 | √ | null |
|
|
An indicator that determines whether a specific match has been approved, allowing the processing to continue, or denied, requiring immediate action to be taken during the submission process. |
||||
| confirmed_match_message | varchar | 1000 | √ | null |
|
|
A field with the reason for the denial of the submission. |
||||
| confirmed_match_timestamp | timestamp | 29,6 | √ | null |
|
|
The timestamp when the changes happened. |
||||
| confirmed_match_userid | varchar | 60 | √ | null |
|
|
The ID of the user submitting the changes. |
||||
| submission_matching_processed | bool | 1 | false |
|
|
A flag to indicate that the submission was finally processed. |
|||||
| submission_matching_processed_time | timestamp | 29,6 | √ | null |
|
|
The timestamp of when the processor started to process this specific entry |
Indexes
| Constraint Name | Type | Sort | Column(s) |
|---|---|---|---|
| submission_matching_detail_id_pk | Primary key | Asc | submission_matching_detail_id |
Relationships
Close relationships within degrees of separation
