Bug #2387
improve compatibility of NO-UNDO temp-tables
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
History
#1 Updated by Eric Faulhaber almost 10 years ago
The validation of no-undo temp-tables in P2J does not quite match the behavior in Progress. See testcases uast/flush/no-undo-invalid*.p
.
Once a record fails validation in Progress, it continues to validate and report errors as enclosing scopes are exited/iterated/retried, but the errors do not necessarily disrupt control flow. For instance, an invalid record in a repeat block will cause errors to be reported during both the retry and iterate phases of the block, but the block does not exit as a result.
With bzr rev 10610, we added partial support, but we don't have this behavior quite right, and it requires further investigation to determine exactly what is happening here.