eventprefmec

Logical Entity Name | EventPrefMec
Default Table Name | eventprefmec
Definition | Summary information on preferred mechanisms for an event

eventprefmec Columns

ColumnName | Domain | Datatype | NULL | Definition
mechtype |  | VARCHAR2(2) | NO | Mechanism type
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
mecid |  | NUMBER(15, 0) | YES | Mechanism identification. Each mechanism is assigned a unique positive integer which identifies it in the database
lddate |  | DATE | YES | Load date. Date and time that the record was created, in Oracle date datatype

eventprefmec Primary and Unique Keys

Key Name | Key Type | Keys
EventPrefMec_PK | PrimaryKey | mechtype, evid

eventprefmec Foreign Keys

Parent Relationships:

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

Child Relationships:

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

eventprefmec Check Constraints

Check Constraint Name | CheckConstraint
EvPMec02 | mecid > 0
EvPMec03 | mechtype IN ('FP','MT')
EvPMec01 | evid > 0