Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

UNION#(Telitab_1$, UnfoldPar_1$, Telitab_2$, UnfoldPar_2$, Mode%)

or

UNION#(Mode%, Telitab_1$, Telitab_2$, ...)

...

  • Telitab_1$ is a string expression containing/returning the first Telitab set.
  • UnfoldPar_1$ is a name of parameter for which to unfold the first Telitab set.
  • Telitab_2$ is a string expression containing/returning the second Telitab set.
  • UnfoldPar_2$ is a name of parameter for which to unfold the second Telitab set.
  • Mode% determines Mode% determines the way to union:
    • Mode% Mode% = 0, Sparse union, i.e. tables are simply attached and not available values are indicated by -999999 (the standard code for PENDING).
    • Mode% Mode% = 1, Union combining parameters of cases with one or more corresponding parameter(s) + value(s).

...

Please note that the union simply contains the sum of two Telitab sets and contains the combined parameters and cases of both sets (Mode%=0). Cases 4-8 have empty object values for PROJECTS.

...

If the union should combine the parameter values of the cases with the same value of the overlapping parameters Mode%=1 should be used:

UNION#(Telitab_1$, "LPP", Telitab_2$, "NullString", 1)

...

Case 1 and 2 of the result are cases 3 and 4 from the unfolded object MODELS in Telitab_1$. 
Case 3 is a combination of of the cases 1 of both input sets. 
Case 4 corresponds with case 2 from Telitab_2$. 
Case 5 is again a combination of respectively the cases 2 and 3. 
Case 6 corresponds with Case 4 from Telitab_2$.

The UNION# function with Mode%=1 can be used as a database manipulation function. The union of two Telitab sets as produced by this functiun completes a set of data by combining data from two source sets in a single table (see also SECTION#() ).

...