OID Columns
Every target table includes a mandatory column with the name oid that contains the OID of the object corresponding to the table row.
Jade supports the following RPS object identifier (oid) length mapping options.
-
Map to String (7.1 format), which is a length 28‑character fixed‑length string of the "ccccccc.nnnnnnnnnnnnnnnnnnnn" format, with leading zeros in both the class and instance fields. The ccccccc value is the 7‑character class number, 1 character is for the separator, and nnnnnnnnnnnnnnnnnnnn is the 20‑character instance id.
This is the recommended oid mapping option, as any oid can be represented in this way.
-
Int/Int, which maps oids and references into two integer columns of _clsno (type int) and _instid (type int).
This mapping option cannot accommodate instance ids larger than 2,147,483,647.
-
Int/BigInt, which maps oids and references into two integer columns of _clsno (type int) and _instid (type bigint), to accommodate 64‑bit instance ids.
This mapping option cannot accommodate instance ids larger than 9,223,372,036,854,775,807.
In historical tables only, null references for deleted transactions are populated with NULL. Null references on non‑deleted transactions are as the expected; that is, "0000000.00000000000000000000".
For details about setting up RPS mapping, see "
