30,997
edits
Language and development rules: Difference between revisions
Jump to navigation
Jump to search
m
→Denormalized field
Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 267: | Line 267: | ||
==Denormalized field== | ==Denormalized field== | ||
Fields that store a data that is result of calculation of other data already stored is a "denormalized field". It must be avoid if we can, and must be used only for performance purpose. | Fields that store a data that is result of calculation of other data already stored is a "denormalized field". It must be avoid if we can, and must be used only for performance purpose. | ||
In such a case, to allow developper to understand that the data is not the value that rule, we must prefix the nameof fiel with "denormalized_". | In such a case, to allow developper to understand that the data is not the value that rule, we must prefix the nameof fiel with '''"denormalized_"'''. | ||
For example the field "denormalized_lower_planned_end_date" to store the ending date of the last membership of a member. We already have the information, but doing search or filter on it is difficult as it is store into a nother table into another level, so we can duplicate the information into a such field. | For example the field "denormalized_lower_planned_end_date" to store the ending date of the last membership of a member. We already have the information, but doing search or filter on it is difficult as it is store into a nother table into another level, so we can duplicate the information into a such field. | ||