Project

General

Profile

Bug #3117

test and fix VALIDATION() expressions in a DELETE statement

Added by Greg Shah almost 8 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version:

History

#1 Updated by Greg Shah almost 8 years ago

Please see the TODO comments in BufferImpl.deleteRecord(Supplier<logical> valexp, Supplier<character> valmsg) and in BufferImpl.validate(Supplier<logical> valexp, Supplier<character> valmsg). Testcases should be created to explore the issues highlighted there and then the implementation should be modified to be fully compatible (to the extent it is not already compatible).

#2 Updated by Greg Shah almost 8 years ago

In regard to the END condition processing, Eric reports this:

This behavior came from a developer making a "correction" at some point, but the end condition stuff especially looks suspect. He probably was working with some test case where this might have happened in a FOR EACH, and assumed the end condition should happen on any validation.

The bottom line is that testcases will be needed to check the current implementation's behavior.

Also available in: Atom PDF