edmiCreateNestedTypedAggrByIndex

SdaiAggr edmiCreateNestedTypedAggrByIndex(SdaiAggr    parentAggr,
                                           SdaiInteger index, 
                                           SdaiSelect  pSel); 

Creates a typed aggregate instance and sets the created aggregate as an element in an already existing aggregate instance, i.e., a nested aggregate is the result of this operation. The already existing aggregate will be the parent aggregate of the new created aggregate and the new created typed aggregate will be a child aggregate of the already existing aggregate. All EDMinterface access operation defined for untyped aggregates is applicable on typed aggregates. Nested typed aggregates must be used when the data type specification of the elements of the parent aggregate is not uniquely defined in the appropriate Express schema. This can only occur when the actual element specification is of type SELECT. A struct of type SdaiSelect containing the aggregate typing should be supplied. This operation is legal for all parent aggregates of ARRAY and LIST aggregate types with the following effect:

1. For ARRAY : The new created typed aggregate will be inserted at the element specified by the <index> argument. If an element already exists in this position, the old element will be replaced by the new one.
2. For LIST: If 0 <= index < elements in list: The new created typed aggregate will be inserted at the element specified by the <index> argument. If an element already exists in this position, the old element will be replaced by the new one. Else the new created typed aggregate will be appended to the parent list aggregate.

A numeric aggregateID that uniquely identifies the new created aggregate instance in the EDMdatabase will be the returned function value. This aggregateID should be used to identify this particular aggregate instance in subsequent EDMinterface operations. An aggregateID is persistent and fixed, i.e. it is constant throughout the lifetime of the actual aggregate instance. An aggregateID can never be used as a data value in any of the EDMinterface put operations, it can only be returned as data value in EDMinterface get operations. This operation is only applicable to aggregates owned by application instances. The model that will hold the new created aggregate must be open for write access .

Arguments

Return Value

Options

Example

/* EXPRESS
 SCHEMA Example;
 . . . 
 TYPE anAggr = SELECT (anArray, aList); END_TYPE; 
 TYPE anArray = ARRAY[1:100] of Person; END_TYPE; 
 TYPE aList = LIST of Child; END_TYPE; 
 . . . 
 ENTITY anEntity; 
 attr1 : SET of anAggr; 
 attr2 : ARRAY[1:10] of anAggr; 
 . . . 
 END_ENTITY; 
 . . . 
 END_SCHEMA;
 */
 SdaiModel modelId;
 SdaiAggr myAggr, parentAggr;
 SdaiAppInstance anInst;
 tSdaiSelect mySelect;
 ...
 anInst = sdaiCreateInstanceBN(modelId, "anEntity");
 parentAggr = sdaiCreateAggrBN(anInst, "attr2");
 mySelect.typeList = (SdaiInstance *) malloc(1 * sizeof(SdaiInstance));
 mySelect.typeList[0]= edmiGetDefinedTypeBN("Example", "aList");
 mySelect.nTypes = 1;
 myAggr = edmiCreateNestedTypedAggrByIndex (parentAggr, 1, &mySelect);
 if (! myAggr) {
 /* Error in operation */ 
 printf("\nError in edmiCreateNestedTypedAggrByIndex: %s\n", 
 edmiGetErrorText(sdaiErrorQuery())); 
 goto error; 
 }
 ...

See also