Language and development rules: Difference between revisions

Language and development rules (view source)

No change in size , 5 months ago

m

30

edits

@@ Line 269: / Line 269: @@
 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 stored into another table into another level, so we can duplicate the information into a such field.
 If this happen, we must :
 * check the any import profile has a function to update the denormalized value during import.
-* have a taks in the repair.php to recalculate the value and align the data with the original source.
+* have a task in the repair.php to recalculate the value and align the data with the original source.
 * into the crud method that update any data that impact the field, we must include the update or the denormalized value.