Kbase P60918: During Pro-to-Ora, what is the naming convention for fields
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/31/2003 |
|
Status: Unverified
GOAL:
During Pro-to-Ora, what is the naming convention for fields that have multiple extents
GOAL:
During Pro-to-Ora, what is the algorithm for naming fields that have multiple extents
GOAL:
During Pro-to-Ora, what is the naming convention for array fields
GOAL:
During Pro-to-Ora, what is the algorithm for array fields
FIX:
During Pro-to-Ora, the algorithm that determines field names when a field has multiple extents (an array) versus the algorithm that calculates field names when a field has no extents is different.
Essentially the Oracle DataServer limits table and field names to be 26 characters. However if the field has extents, then the algorithm is a bit different. Thus, the DataServer adds the following "##<number of extents>" to the field-name; i.e., field-name##3
The rule to calculate the field name with extents is;
If the field has 1-9 extents- Progress will subtract 3 characters from the base name, allowing for the addition of ##<1-digit>
If the field has 10-99 extents- Progress will subtract 4 characters from the base name, allowing for the addition of ##<2-digits>
If the field has 99-999 extents- Progress will subtract 5 characters from the base name, allowing for the addition of ##<3-digits>
Example 1:
-Progress field name = Helper-Setup-Hours-Override
-Field name has 27 characters with 5 extents.
-Since we're limited to 26 characters, Pro-to-Ora truncates the field name to the translation name, "Helper_Setup_Hours_Over##5".
-Field name in schema holder = Helper-Setup-Hours-Override
-Field names in Oracle;
Helper_Setup_Hours_Over##1
Helper_Setup_Hours_Over##2
Helper_Setup_Hours_Over##3
Helper_Setup_Hours_Over##4
Helper_Setup_Hours_Over##5
Example 2:
-Progress field name = Measure-Per-Unit-Override
-Field has 25 characters with 5 extents.
-Since we're limited to 26 characters, Pro-to-Ora truncates the field name to the translation name, Measure_Per_Unit_Overri##5.
-Field name in schema holder = Measure-Per-Unit-Override
-Field names in Oracle
Measure_Per_Unit_Overri##1
Measure_Per_Unit_Overri##2
Measure_Per_Unit_Overri##3
Measure_Per_Unit_Overri##4
Measure_Per_Unit_Overri##5
Example 3
-Progress field name = Measure-Per-Unit-Override
-Field has 25 characters with 20 extents.
-Since we're limited to 26 characters, Pro-to-Ora truncates the field name to the translation name, Measure_Per_Unit_Overr##20.
-Field name in schema holder = Measure-Per-Unit-Override
-Field names in Oracle
Measure_Per_Unit_Overr##1
Measure_Per_Unit_Overr##2
Measure_Per_Unit_Overr##3
Measure_Per_Unit_Overr##4
Measure_Per_Unit_Overr##5
...
...
Measure_Per_Unit_Overr##20