Bug #10039
Error 132 is not caught by the defined CATCH block
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
History
#2 Updated by Dănuț Filimon about 1 year ago
From #8912-334:
The 132 error is not caught, the test case to isolate the issue is:
DEFINE TEMP-TABLE ttTABLE
FIELD F1 AS int
FIELD F2 AS CHARACTER
INDEX if1f2 IS PRIMARY UNIQUE F1 F2.
do transaction:
CREATE ttTable.
CREATE ttTable. // ** ttTABLE already exists with "" "".(132)
catch e as Progress.Lang.Error :
message e:GetMessage(1). // not caught in FWD
end catch.
end.
The fix is already in 8912k, but it regresses multiple unit tests.