Architectural Principles Column Precision
Number columns in PPDM should be defined in terms of their total length and the number of decimals allowed, except for vertical tables, where the total length and precision are defined in PPDM_PROPERTY_COLUMN. This enforces application and use of a standard level of precision in the values stored.
Guidelines
1. For numeric columns that capture a single type of numeric information (such as depth), the total field length and the number of decimal places should be defined.
2. For numeric columns in a vertical table, the column length and precision should be NUMERIC UNCONSTRAINED. In these cases, the total length and precision for each kind of numeric value should be defined in the vertical control table using PPDM PROPERTY SET.
3. Column types used frequently should be controlled through a CASE domain, to ensure consistency of use. Following is a partial list of number domains in PPDM 3.7:
- AGE 15,5
- CURRENCY 12,2
- CURRENCY_CONVERSION 10,5
- DEPTH 10,5
- DIAMETER 8,3
- ELEV 10,5
- LAT 12,7
- LONG 12,7
- OFFSET 8,2
- PARAMETER_VALUE 10,5
- PARCEL_SIZE 13,5
- PERCENT_INT 15,12
- VELOCITY 10,5
- VISCOSITY 8,3
- VOLUME 14,4
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
