OPALE - 10.0 - Utilisation - MAPPING TRACEDATA/en

Différence entre versions

De MappingDoc
 
(13 révisions intermédiaires par le même utilisateur non affichées)
Ligne 1 : Ligne 1 :
 +
<languages/>
 
The MAPPING_TRACEDATA parameter recovers changes made to the fields.
 
The MAPPING_TRACEDATA parameter recovers changes made to the fields.
  
Ligne 7 : Ligne 8 :
 
Level 1 of DB.MAPPING_TRACEDATA shows us the values of the fields once they are assigned.
 
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 allows you to have more detailed calculations for instance.
+
Level 2 shows us the values of the fields when they are accessed. This gives more detail in calculations for instance.
  
 
Example:
 
Example:
  
The following calculation gives us:
+
The following calculation would be:
  
     DB.entier3 = $DB.entier1 -$DB.entier2
+
     DB.integer3 = $DB.integer1 -$DB.integer2
  
 
At level 1:
 
At level 1:
DATA  : .DB(whole3)=12
+
DATA  : .DB(integer3)=12
  
 
At level 2:
 
At level 2:
  
DATA  : .DB(entier3)=(null)
+
DATA  : .DB(integer3)=(null)
  
DATA  : .DB(entier1)=15
+
DATA  : .DB(integer1)=15
  
DATA  : .DB(entier2)=3
+
DATA  : .DB(integer2)=3
  
DATA  : .DB(entier3)=12
+
DATA  : .DB(integer3)=12

Version actuelle datée du 14 juin 2019 à 07:54

Autres langues :
English • ‎français

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