52 results about "Object oriented databases" patented technology

A computer data processing system including a central processing unit configured with a novel integrated computer control software system for the management of data objects including dynamic and automatic organization, linking, finding, cross-referencing, viewing and retrieval of multiple objects regardless of nature or source. The inventive system provides underlying component architecture having an object-oriented database structure and a metadata database structure which is unique in storing only one instance of each object while linking the object to multiple collections and domains by unique metadata links for the grouping into and retrieval from any of the collections. The system employs configurable, extensible attribute / properties of data objects in metadata format, and a truly user-friendly configurable interface that facilitates faster, more unified, comprehensive, useful and meaningful information management. Additional features include a sticky path object hierarchy viewing system, key phrase linking, viewing by reference, and drag-and-drop relationship link creation.

The present invention creates a model that maps object classes in an object-oriented environment to a data source. The model maps the relationship between properties of each object class and data of the data source. The present invention can be used with a data source such as a relational database, user interface, file system, or object-oriented database. An application's object classes and data source schema are designed independent of the other since the model can be used to map one to the other. The model is comprised of entities and attributes. An entity maps to an object class and to at least one table of the DBMS. An entity contains attributes either simple or derived. A simple attribute maps to a DBMS column. A derived attribute is a combination of other attributes and does not directly map to a DBMS column. A relationship creates a link between entities of the model. A relationship can be used to flatten an attribute or flatten a relationship. A flattened attribute is an attribute of one entity that is added to another entity. A flattened relationship is created by the elimination of intermediate relationships between two entities. Relationships can be either unidirectional or bi-directional. A unidirectional relationship has a single traversal path that has a source entity and a destination. A bi-directional relationship has two traversal paths. A reflexive relationship can be created using a single entity. The model is used to synchronize object properties and the data of the data source.

Techniques for managing data distributed over nodes in a network include receiving, at an original node, content data that describes a physical entity that is not a router in a vicinity of the original node. In response to receiving the content, a beacon data object is generated in an object-oriented database distributed over the network nodes. The beacon holds the content data and holds policy data that indicates how to terminate the beacon. A node that has ownership of the beacon performs the step of terminating the beacon based on the policy data. Ownership of the beacon can be transferred so that the beacon stays associated with the physical entity, such as a room in a building, even as a mobile original node moves away from the physical entity. The content data can indicate conditions that invite responsive action, such as hazardous environmental conditions.

A distributed, object-oriented database engine utilizing independent, intelligent processing nodes as a cooperative, massively parallel system with redundancy and fault tolerance. Instead of using traditional methods of parallelism as found in most distributed databases, the invention utilizes a messaging system and a series of message processing nodes to determine where attributes and data files associated with objects are stored. The architecture is loosely coupled, each node independently determining if it manages or routes storage and retrieval requests.

Implementations of the present invention allow a user to work within a record-based design environment while achieving the advantages provided by an object-oriented database. In particular, the user of components in accordance with the present invention can create designs within a record-based application program, within an object-oriented application program, or within a third application program linked by the object-oriented program, and still have the graphical representation thereof visibly displayed in the record-based application program.