About: Object-relational database is a research topic. Over the lifetime, 259 publications have been published within this topic receiving 3390 citations.
TL;DR: In this paper, a system for accessing business data stored in one or more databases by a user is presented, which includes a means for presenting a user with a plurality of components with each component representing a discrete element of the business model.
Abstract: The invention provides a system for accessing business data stored in one or more databases by a user. The system includes a means for presenting a user with a plurality of components with each component representing a discrete element of the business model, having a defined relationship with each other component, and including a plurality of information objects. Each information object represents an instance of the component business element and can be defined by a set of attributes and behaviors. The system further provides means for user selection of a first one of the plurality of components, for user selection of a first one of the plurality of information objects from the first component, and for instantiating the first information object. The user can then manipulate the first information object to cause the object to interact with any of the other components. The system then generates a report showing information objects of the other component which represent instances of the other component that are related to the first information object.
TL;DR: In this paper, a federated coordinator coupled to the client interface for translating client commands into object server commands, an object server coupled with a processor and a data storage device for storing the object data, a virtual processor instance, invoked on the processor for performing the data function on the data identified by the data surrogate to produce processed data, and a virtual disk instance invoked in the data storage devices and logically associated with the virtual processor instances for storing object data.
Abstract: A method and apparatus for processing object data. The apparatus comprises a client interface for receiving client commands comprising a data surrogate identifying the object data and an object data function, and for transmitting processed object data to a client, a federated coordinator coupled to the client interface for translating client commands into object server commands, an object server coupled to the federated coordinator comprising a processor and a data storage device for storing the object data, a virtual processor instance, invoked on the processor for performing the object data function on the object data identified by the data surrogate to produce processed data, a virtual disk instance, invoked in the data storage device and logically associated with the virtual processor instance for storing the object data identified by the data surrogate, and means for moving the object data function to the virtual processor instance logically associated with the virtual disk instance storing the object data.
TL;DR: This paper discusses how XML data can be stored, managed and queried in the Oracle8i database, and presents Oracle's XML-enabling database technology.
Abstract: XML is here as the Internet standard for information exchange among e-businesses and applications. With its dramatic adoption and its ability to model structured, unstructured and semi-structured data, XML has the potential of becoming the data model for Internet data. In recent years, Oracle has evolved its DBMS to support complex, structured, and un-structured data. Oracle has now extended that technology to enable the storage and querying of XML data by evolving its DBMS to an XML enabled DBMS, Oracle8i. We present Oracle's XML-enabling database technology. In particular, we discuss how XML data can be stored, managed and queried in the Oracle8i database.
TL;DR: In this paper, a computer system for transferring data from an object relational database to another such database is presented, where the data in the source database having a table type hierarchy of data tables is transformed to a flat file format data transfer file using a defined tree traversal order.
Abstract: A computer system for transferring data from an object relational database to another such database. The data in the source database having a table type hierarchy of data tables. The system transforming data from the source database to a flat file format data transfer file using a defined tree traversal order. The columns and subcolumns of the data transfer file corresponding to types and attributes from the source database type hierarchy; The data transfer file having a type identifier column corresponding to a type in the table type hierarchy. The system permitting the inputting of the data from the data transfer file to a target database having a table type hierarchy corresponding to the table type hierarchy of the source database.
TL;DR: An overview of the semantic integrity support in the most recent SQL-standard SQL:1999 is given, and it is shown to what extent the different concepts and language constructs proposed in this standard can be found in major commercial (object-)relational database management systems.
Abstract: The correctness of the data managed by database systems is vital to any application that utilizes data for business, research, and decision-making purposes. To guard databases against erroneous data not reflecting real-world data or business rules, semantic integrity constraints can be specified during database design. Current commercial database management systems provide various means to implement mechanisms to enforce semantic integrity constraints at database run-time.In this paper, we give an overview of the semantic integrity support in the most recent SQL-standard SQL:1999, and we show to what extent the different concepts and language constructs proposed in this standard can be found in major commercial (object-)relational database management systems. In addition, we discuss general design guidelines that point out how the semantic integrity features provided by these systems should be utilized in order to implement an effective integrity enforcing subsystem for a database.