|
SMACS | |||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
See:
Description
| Interface Summary | |
| DbTargetSimpleNode | methods of target definition stage. |
| DbTargetValue | (ignore). |
| DbTargetValueList | DbTarget ValueList operations. |
| DbTargetValueStore | DbTarget ValueList holder. |
| Class Summary | |
| DbTargetInsert | Header for a target. |
| DbTargetListShow | (ignore) |
| DbTargetScanMappingList | algorithm base. |
| DbTargetScriptNode | base node for target definition. |
| DbTargetSource | define source for a target. |
| DbTargetValueListNode | DbTarget ValueList operations. |
the target insert clauses are chained - detect relations
One part is the detection of source references in the outer cursor which is not so much important unless for usage in muliple rule optimization steps - where a number of insert rules would be combined under the set of a single multi-insert rule.
The chaining of outputs is more important in here, we need to detect references of an insert clause on to the insert record of a prior target clause. Such an insert record would need to be cached or reestablished, and it might be the result of an exist clause. Such an exist clause might be implicitly created by means of an old/new on unique columns.
Remember that this is the analyze stage, we just check possible relations of the clauses in a rule. The real instantion is decided later, here we just store everything not matter whether it is used for real then.
|
SMACS | |||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||