Attribute/Field Attribute
In addition to basic information such as field names, Chinese names, and data types, fields also have design attributes such as constraints, enumeration codes, and self-increment, as well as source and modeling attributes such as model library sources and role types. These properties are maintained in the list in the Field Editor and in the property bar below, with the role type in the Advanced Properties grouping.
Property Item Overview
| Attribute Items | Optional or Possible Values | Description | Applicable Levels |
|---|---|---|---|
| Check Constraints | Ranges, Enumerated Values, Custom Expressions | Generate check Constraints, Limit Field Values | Logical, Physical |
| Enumerated Codes | Fully referenced, crop references, custom references | Referenced standard codes form a list of values | Logical, Physical |
| Increment | On/Off | Field values are automatically incremented by the database | Physical |
| Model Library Source | Source Type, Source Model, Source Table | Record which online model action the field is generated from | Logical, Physical |
| Role Type | Optional by Table Type | Set in Advanced Properties, Mark Business Roles for Fields | Logical, Physical |
Check Constraints
The check constraint of the field corresponds to the check constraint of the database, and the type is selected according to the value characteristics when modeling.
| Constraint Type | Applicable Scenarios | Fill in Key Points |
|---|---|---|
| Value Range | Numeric or comparable interval limits | Clarify top and bottom boundaries and whether endpoints are included |
| Enum Value | Values are from a fixed set | List legal values item by item, consistent with the value of the enumeration code |
| Custom expressions | Require combinatorial conditions or function judgments | Write in the expression syntax of the target database, and output as-is when generating DDL |
The constraint writes the table building statement when generating DDL. When the target database does not support the corresponding writing method, it needs to be adjusted before generating.
Enumerate how the code is referenced
| Citation | Meaning | Applications |
|---|---|---|
| Full reference | Full use of all values of the standard code | Field values are exactly the same as the standard |
| Crop references | Only partial values in standard code are referenced | Fields use only subsets of the standard |
| Custom Reference | Custom Value Taking Based on Standard Code | Standard Not Overridden, Requires Local Extension |
The value of the enumeration code is derived from the data standard referenced by the field, so it is often used with the reference data standard.
Auto Increment
The auto increment token field value is automatically generated by the database and is common in proxy primary keys. After opening, the field no longer relies on business input, and it needs to be confirmed that the target database supports self-incrementing syntax and avoids conflicts with explicit assignment.
Model Library Source
When you do an inheritance transformation on an online model, or refer to a field from an online model, the newly generated field records the source of the model library, which is used to trace the generation process of the field.
| Subitems | Recording |
|---|---|
| Source Type | Which behavior produces the current field, such as inheritance transformations or shared entity references |
| Source Model | Path and Name of Corresponding Line Model |
| Source Table | Specific Table in Matching Line Model |
Source information is used only for traceability and is not involved in DDL generation. See Inheritance and Conversion and Shared Entity for related behaviors.
role-type
The role type is set in the Advanced Properties of the Field Editor. When the table type of the belonging table is set to "Dimension Table", the role type of the field is identified in the entity, which is used to distinguish the identifying field from the descriptive field in the dimension modeling scene. See Entity/Table Properties for settings for table types.
Notice
- Constraints, enumeration, and self-increment will eventually affect the DDL, and the table building statement should be previewed again after modification.
- The role type is only reflected when the table type is "Dimension Table", and settings under other table types have no effect.
- The model library source is read-only traceability information that is automatically written with inheritance or reference operations.