pr_other table

The pr_other table is the default destination for saved instances that belong to a class that is not mapped to any other table. To access the pr_other table, the system uses the catalog and schema specified for the pr4_base table as identified in the databases/baseTable/catalog and databases/baseTable/schema entries in the prconfig.xml file or dynamic system settings.

Each time an object is saved to the pr_other table, the system adds a PEGA0041 alert to the alert log.

CAUTION:

This table is convenient during development, as changes to the class structure do not require changes to the database schema. However, use this facility with caution. Because the pr_other table has only a few columns, most properties are stored in the Storage Stream column of this table. Accordingly, accesses to this table — reads, updates, or deletes — are often slower than accesses to the same instance when stored as a row in a "purpose built" table.

Using pr_other to store data for an application under development does not by itself indicate an error in the database design or operations. However, using the pr_other table is undesirable if your application frequently searches rows of this table. In this case, define a new table in the Pega Platform database to hold instances of the class, and add a database table instance to map instances to the new table map saved instances to an existing table.