OPM insert, delete, or update queries can be processed using insert, delete, or update methods, respectively. Object insertions, deletions, and updates refer to individual OPM class instances and therefore involve their Oid's. Since Oid's cannot be accessed directly by users, OPM class instances are identified in queries using conditions involving regular attributes. The mapping between the values of these attributes and internal Oid values can be achieved using retrieval queries (e.g., via one of the approaches mentioned above).
Object insert, delete, or update queries can be also translated directly into SQL transactions. For this translation, Oid values do not have to be known ahead of time.