Kbase P135209: TEMP-TABLE and DATASET method documentation doesn't mention effects to buffer state
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
01/02/2010 |
|
Status: Verified
SYMPTOM(s):
TEMP-TABLE and DATASET method documentation doesn't mention effects to buffer state
** No <file-name> record is available. (91)
WRITE-XML method causes default buffer to become unavailable
READ-XML method loses buffer state
FILL method forces buffer out of scope
CAUSE:
Bug# OE00174889
CAUSE:
When executing one of the below methods on a temp-table or proDataSet, and the default buffer of one of the contained temp-tables is available, there is no guarantee as to the state of that buffer after the method has finished executing.
WRITE-XML
READ-XML
FILL
SAVE
Any Reject/Accept type activity
This is simply a documentation bug. The loss of the buffer state after these methods are used is expected.
The default buffer is needed for read/create/write operations and its momentary contents are not guaranteed after the operation is completed. In the case of the WRITE-XML method the table should have the same content after the method completes but since the default buffer was used to handle the write its position and state are not guaranteed.
FIX:
For WRITE-XML use a named buffer if there is any expectation of buffer availability after the method completes. For the other methods there is no guarantee that the temp-table is going to contain the same data afterward so no such expectation is even considered reasonable.