Abstract: As a solution to the problem of distributed knowledge of data object definitions, data object definitions are removed from the source code. A Meta Data Service is created and made available on a network which knows the definitions of all of the objects that are used by applications that are designed to use the Meta Data Service. When an object is created, the Meta Data Service creates and stores a meta definition for the object. Data objects are passed over a network in a “soft” format. Applications within a distributed data processing system are designed in such a manner such that, at any stage of object processing, an application does not assume to understand the definition or structure of an object, nor is an application hard-coded with the object definitions. At each stage, an application queries the Meta Data Service for the meta definition of the object before proceeding with the processing of an object.

Abstract: A persistent object service (POS) that interfaces to a set of one or more relational database management systems. A persistent object is mapped to one or more tables in a relational database based on the object's attribute types and the object's relationships with other objects. If the object inherits from another object, the mapping creates multiple tables, a top level table for base attributes, and a set of one or more child tables that contain extended attributes of the inherited objects. A routine for storing an object converts persistent object operations to a sequence of SQL statements for storing the object in the relational database.

Abstract: A persistent object service (POS) that interfaces to a set of one or more relational database management systems. A persistent object is mapped to one or more tables in a relational database based on the object's attribute types and the object's relationships with other objects. If the object inherits from another object, the mapping creates multiple tables, a top level table for base attributes, and a set of one or more child tables that contain extended attributes of the inherited objects. A routine for storing an object converts persistent object operations to a sequence of SQL statements for storing the object in the relational database.

Abstract: A persistent object service (POS) that interfaces to a set of one or more relational database management systems. A persistent object is mapped to one or more tables in a relational database based on the object's attribute types and the object's relationships with other objects. If the object inherits from another object, the mapping creates multiple tables, a top level table for base attributes, and a set of one or more child tables that contain extended attributes of the inherited objects. A routine for storing an object converts persistent object operations to a sequence of SQL statements for storing the object in the relational database.