Project

General

Profile

Bug #3495

invalid date initial value in schema causes a broken DMO constructor

Added by Greg Shah about 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Greg Shah
Target version:
-
Start date:
Due date:
% Done:

100%

billable:
No
vendor_id:
GCD
case_num:

schema.g_3489a_rev_11231.patch Magnifier (2.32 KB) Greg Shah, 03/07/2018 06:29 PM

History

#1 Updated by Greg Shah about 6 years ago

The use of an invalid INITIAL clause for a date field will cause the generated DMO constructor to be broken:

ADD FIELD "sec-pay-date" OF "bocip-surchrg-dtl" AS date 
  DESCRIPTION "second payment end date" 
  FORMAT "99/99/9999" 
  INITIAL "Second pay end date"    <----- THIS IS AN INVALID DATE
  LABEL "Second pay end date" 
  POSITION 8
  MAX-WIDTH 4
  COLUMN-LABEL "Second pay end date" 
  ORDER 70

This was seen in customer code. Presumably, OpenEdge tolerates this. Please confirm this hypothesis and check to see what the initial value is actually set to in the 4GL. I suspect it is ? (unknown value).

The FWD conversion of this construct should be fixed.

#2 Updated by Greg Shah about 6 years ago

The fix for this issue is in task branch 3489a revision 11231 (and also attached here as a patch file).

Eric: Please review.

#3 Updated by Greg Shah about 6 years ago

  • % Done changed from 0 to 100
  • Assignee set to Greg Shah
  • Status changed from New to Closed

This fix was included in branch 3489a which was merged to trunk as revision 11245. It will be available for download when FWD v3.2 is released.

Also available in: Atom PDF