eventprefor

Logical Entity Name | eventprefor
Default Table Name | eventprefor
Definition | Summary information on preferred origins for an event

eventprefor Columns

ColumnName | Domain | Datatype | NULL | Definition
type |  | VARCHAR2(2) | NO | Type of location
evid |  | NUMBER(15, 0) | NO | Event identifier. Each event is assigned a unique integer which identifies it in a database. It is possible for several records in the Origin relation to have the same evid. This indicates there are several opinions about the location of the event. The evid does not have to be identical to the local network’s event identifier, which is stored in the Origin table. This allows merging data for a single event from multiple sources without insisting that database evid is identical to the source’s local event identifier
orid |  | NUMBER(15, 0) | NO | Origin identification. Each origin is assigned a unique positive integer which identifies it in the database. The orid is used to identify one of the many hypotheses of the actual location of the event
lddate |  | DATE | YES | Load date. Date and time that the record was created, in Oracle date datatype

eventprefor Primary and Unique Keys

Key Name | Key Type | Keys
EventPrefOr_PK | PrimaryKey | type, evid

eventprefor Foreign Keys

Parent Relationships:

Table Name | Type | Cardinality | Constraint Name | VerbPhrase | InversePhrase | Foreign Keys | Is Supertype | Deferrable | Initially Deferred
event | Non-Identifying | One To Zero or More |  |  |  | evid | NO | NO | NO
origin | Non-Identifying | One To Zero or More |  |  |  | orid | NO | NO | NO

Child Relationships:

Table Name | Type | Cardinality | Constraint Name | VerbPhrase | InversePhrase | Foreign Keys | Is Subtype | Deferrable | Initially Deferred

eventprefor Check Constraints

Check Constraint Name | CheckConstraint
EventPrefOr_CHKTYP | type in ('h','H','c','C','a','A','d','D','u','U')