This option specifies whether or not the X_UPID and X_RRNO columns should be added to the table when the table is built. If Create RRNO Column is selected, any existing identity column will be used instead of X_RRNO, as a second identity column cannot be added to the table. (Refer to Identity columns.)
If you import a table that does not have a primary key, and do not select Create RRNO Column, functionality will be limited. For further details, refer to Create RRNO Column in the LANSA Technical Reference Guide. To minimize functionality limitations, add a primary key or unique index and reimport the table. Alternatively, select the Create RRNO Column option in the Table Attributes for the table.
The X_RRNO value will be automatically incremented using a database-specific method.
You must be connected to the database with appropriate permissions on the table to allow the column(s) to be added.
Once the column(s) have been added to the table, they can only be removed manually.
Note that adding the RRNO column affects existing SQL syntax which does not explicitly specify column names. For example the INSERT statement:
INSERT TO MYTABLE VALUES('A', 'B', 2)
only works if a value is specified for all columns. After you add the RRNO column this syntax will not work anymore.
It is better programming practice to specify the names of the columns. In this way adding new columns to the table will not affect your code:
INSERT TO MYTABLE(COL1, COL2, COL3) VALUES('A', 'B', 2)
Also See
LANSA Tables loaded as Imported tables
Building a Table with Create RRNO Column selected (Oracle-specific)
Removing X_UPID and X_RRNO Columns (Oracle-specific)
