OPALE - 10.0 - Utilisation - MAPPING TRACEDATA/en
Différence entre versions
De MappingDoc
| (6 révisions intermédiaires par le même utilisateur non affichées) | |||
| Ligne 12 : | Ligne 12 : | ||
Example: | Example: | ||
| − | The following calculation | + | The following calculation would be: |
| − | DB. | + | DB.integer3 = $DB.integer1 -$DB.integer2 |
At level 1: | At level 1: | ||
| − | DATA : .DB( | + | DATA : .DB(integer3)=12 |
At level 2: | At level 2: | ||
| − | DATA : .DB( | + | DATA : .DB(integer3)=(null) |
| − | DATA : .DB( | + | DATA : .DB(integer1)=15 |
| − | DATA : .DB( | + | DATA : .DB(integer2)=3 |
| − | DATA : .DB( | + | DATA : .DB(integer3)=12 |
Version actuelle datée du 14 juin 2019 à 07:54
The MAPPING_TRACEDATA parameter recovers changes made to the fields.
MAPPING_TRACEDATA=1 recovers field changes
Format: LIB.FILE(FIELD)=VALUE
Level 1 of DB.MAPPING_TRACEDATA shows us the values of the fields once they are assigned.
Level 2 shows us the values of the fields when they are accessed. This gives more detail in calculations for instance.
Example:
The following calculation would be:
DB.integer3 = $DB.integer1 -$DB.integer2
At level 1: DATA : .DB(integer3)=12
At level 2:
DATA : .DB(integer3)=(null)
DATA : .DB(integer1)=15
DATA : .DB(integer2)=3
DATA : .DB(integer3)=12
