Kbase P127420: EMPTY-DATASET and EMPTY-TEMP-TABLE reset ORIGIN-HANDLE
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  11/01/2008 |
|
Status: Unverified
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
SYMPTOM(s):
EMPTY-DATASET and EMPTY-TEMP-TABLE reset ORIGIN-HANDLE
ORIGIN-HANDLE attribute of a TEMP-TABLE object is reset to the unknown value (?)
Using EMPTY-DATASET on changes dataset resets ORIGIN-HANDLE attribute
Using EMPTY-TEMP-TABLE on temp-table in changes dataset resets ORIGIN-HANDLE attribute
CAUSE:
This is expected behavior.
When executing the GET-CHANGES method on a buffer or proDataSet handle to populate the target table/dataset with changes from the original table/dataset, the ORIGIN-HANDLE attribute is set to the handle of the originating table for each temp-table with changes in the changes dataset.
This is used internally by the AVM when executing MERGE-CHANGES to merge change data back into the original dataset. This is also a useful tool for developers to use to track where the data came from.
When using EMPTY-DATASET on a changes dataset or EMPTY-TEMP-TABLE on a temp-table in a changes dataset the ORIGIN-HANDLE attribute is no longer meaningful and is reset to the unknown value (?).
FIX:
Documentation has been changed to reflect this.