Architectural Principles Sequence Control
From PPDM Wiki
Sequences in the database may be ordered by observation, or by some other factor, such as a spatial relationship or an event. There are two types of sequences:
Contents |
Observation Sequence
Each occurrence is based on a separate observation, such as for well production tests. The order of events or occurrences is not significant.
- Example:
- WELL_PRESSURE.PRESSURE_OBS_NO
Guidelines
- All occurrences of observation sequences will be named using the class word OBS_NO:
NNNNN_OBS_NO
- The format will be number 8.0
- Example:
- AOF_OBS_NO
- PRESSURE_OBS_NO
Ordered Sequence
Occurrences are ordered based on sequential information, such as spatial location, sequence or chronology.
- Example:
- SEIS_POINT.POINT_SEQ_NO
Guidelines
- All occurrences of ordered sequences will be named using the class word SEQ_NO:
NNNNN_SEQ_NO
- The format will be number 8.0
- Example:
- POINT_SEQ_NO
- WELL_SEQ_NO
- REMARK_SEQ_NO
Chronological Event
Occurrences are ordered based on time, but the date or time may not always be known. In the case, a unique identifier is added to the PK, and the date is a nullable column in the table. Dates should not be added to primary keys.
- Example:
- WELL_STATUS
Go to
- Architectural Principles NULL Data
- Architectural Principles Dates
- Architectural Principles Versioning
- Architectural Principles Vertical Tables
- Architectural Principles Sequence Control
- Architectural Principles Economics and Financial
- Architectural Principles Column Precision
- Architectural Principles Column Field Type
- Architectural Principles Standardized Columns
- Architectural Principles SQL View Definitions
- Architectural Principles Other SQL Definitions
