Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

> ## Naming conventions

> The Progress-to-ORACLE utility generates names for the columns it adds to an ORACLE table. These names follow the conventions described in Table 7–6.

> Table 7–6: Progress-to-ORACLE naming conventions
> OpenEdge field | ORACLE column name
> --- | ---
> Record ID. | `PROGRESS_RECID`
> Array with three elements (for example, `MONTH`). | `field`##1, `field`##2, `field`##3 (`MONTH##1`, `MONTH##2`, `MONTH##3`)

> For example, if your source OpenEdge table includes a field extent named `MONTH` with 12 elements, the Progress-to-ORACLE utility creates 12 columns of the same data type named `MONTH##1`, `MONTH##2`, `MONTH##3`, etc. A Progress 4GL reference to `MONTH[3]` translates into a reference to the ORACLE column `MONTH##3`.

> In addition, the Progress-to-ORACLE utility modifies the names of OpenEdge objects to non-ORACLE keywords in the ORACLE schema. For example, `ORDER` is a reserved word in ORACLE, so the utility changes the `order` field of the OpenEdge demo database to the `order_` column in an ORACLE database. It also modifies names that might conflict with unrolled field extents and that contain characters unacceptable to ORACLE. The OpenEdge field name `order-line` changes to `order_line` to account for the fact that the hyphen (-) is an unacceptable character in ORACLE object names. Be aware that if you have objects in your OpenEdge database with names that are very similar, and conflict with ORACLE reserved words and restricted characters, they can be modified multiple times to produce a valid name.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095