Kbase P39774: What are the impacts of manually removing PROGRESS_RECID col
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/8/2003 |
|
Status: Verified
GOAL:
What are the impacts of manually removing PROGRESS_RECID column created by Pro-to-Ora tool?
GOAL:
What are the impacts of manually removing PROGRESS_RECID column?
FACT(s) (Environment):
Oracle DataServer
FIX:
In order to maintain consistent application behavior between Progress database and Oracle database, Pro-to-Ora creates an indexed NUMBER column, called PROGRESS_RECID, with unique values for each row to support RECID 4GL function.
The PROGRESS_RECID is used when FIND PREV or FIND LAST statements are issued. The DataServer repositions only cursors used by FIND NEXT/PREV/CURRENT statements. Cursors are never repositioned with a FOR EACH statement and/or by new queries. To support these statements, an ORACLE table must include either a PROGRESS_RECID column or an indexed NUMBER column with unique values.
The impact of deleting PROGRESS_RECID column is application related. If the application does not use RECID function (use ROWID instead) and has indexed NUMBER column with unique values to support FIND PREV or FIND LAST, the impact is minimal.
If the application does use either RECID/ROWID functions and does not have an integer NUMBER column other than the PROGRESS_RECID, then you will be greatly affected if this column is removed.