Project

General

Profile

Bug #11904

INITIAL in a schema .df file follows 'mdy' format

Added by Constantin Asofiei 22 days ago. Updated 14 days ago.

Status:
WIP
Priority:
Normal
Assignee:
Ovidiu Maxiniuc
Target version:
-
Start date:
Due date:
% Done:

90%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
Constantin Asofiei
production:
No
env_name:
topics:

History

#2 Updated by Constantin Asofiei 22 days ago

In #11871 project, the .df file uses 'mdy' format, INITIAL "7/27/2026", for a datetime field.

The database is ran with 'dmy' format in 4GL.

We need to confirm via tests that:
  • either this was a TODAY format which was exported wrong
  • the schema INITIAL date format always follows 'mdy', regardless on how you run the 4GL database

#3 Updated by Ovidiu Maxiniuc 21 days ago

  • Assignee set to Ovidiu Maxiniuc
  • Status changed from New to WIP
  • reviewer Constantin Asofiei added

According to Progress Documentation, "The date constants entered in procedures, or as initial values in the Data Dictionary, are always specified in month/day/year format." It is not affected by SESSION:DATE-FORMAT attribute or by Date Format (-d) command-line parameter.

I also manually tested by starting the process with different date formats and exporting the database schema. In all cases the resulting .df file was identical.

I am looking at FWD implementation of data-related fields based on initial value, next.

#4 Updated by Ovidiu Maxiniuc 14 days ago

  • % Done changed from 0 to 90

Created branch 11904a from trunk 16773.

Initial values of date* fields are always in MDY format. Currently testing different combinations of fields and date-formats.

Committed revision 16774.

Also available in: Atom PDF