Project

General

Profile

Feature #1734

improve temp/work table naming

Added by Eric Faulhaber over 11 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
FWD - Converted Code Improvements - Deduplication
Start date:
Due date:
% Done:

100%

Estimated time:
16.00 h
billable:
No
vendor_id:
GCD

History

#1 Updated by Eric Faulhaber over 11 years ago

The current naming convention of TempRecordN, where N is a sequential number, is severely limiting. Any change to a temp/work table requires full reconversion, because an incremental conversion restarts the number sequence and causes naming collisions. The names must be persisted in the conversion database for consistency across subsequent, incremental conversion runs.

Also, we should do away with the sequential naming convention altogether and base the names on those used in the 4GL code. Note we will have to deal with the case where the same table structure is named differently across external procedures.

#2 Updated by Greg Shah over 11 years ago

  • Target version set to Code Improvements

#3 Updated by Eric Faulhaber about 8 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Implemented.

#4 Updated by Greg Shah over 7 years ago

  • Target version changed from Code Improvements to Converted Code Improvements - Deduplication

Also available in: Atom PDF