About: Single Table Inheritance is a research topic. Over the lifetime, 83 publications have been published within this topic receiving 3513 citations.
TL;DR: A translator for translating objects defined in Abstract Syntax Notation (ASN) such as ASN.1 to a relational database schema as mentioned in this paper allows persistent storage of object instances as records in relational database.
Abstract: A translator for translating objects defined in Abstract Syntax Notation such as ASN.1 to a relational database schema permits persistent storage of object instances as records in a relational database. Object classes are mapped to entity tables with object instances represented by entity records. Simple attributes are mapped to primitive typed attribute columns and package or group attributes are mapped to separate dependent entity tables. Derived attributes are represented by joins of the parent and child entity records.
TL;DR: In this article, the authors present an approach to derive OLAP dimensions from the normalized relational table and the results of the OLAP measures derivation by an automated method according to the present invention.
Abstract: A Relational Database Management System (RDBMS) having any arbitrary structure is translated into a multi-dimensional data model suitable for performing OLAP operations upon. If a relational table defining the relational model includes any tables with cardinality of 1,1 or 0,1, the tables are merged into a single table. If the relational table is not normalized, then normalization is performed and a relationship between the original table and the normalized table is created. If the relational table is normalized, but not by dependence between columns, such as in the dimension table in a snowflake schema, the normalization process is performed using the foreign key in order to generate the normalized table. Once the normalized table is generated, OLAP measures are derived from the normalized relational table by an automated method. In addition, OLAP dimensions are derived from the normalized relational table and the results of the OLAP measures derivation by an automated method according to the present invention. According to an aspect, it is possible to associate a member of a dimension to another member of the same or another dimension. According to another aspect, it is possible to create a new dimension of analysis, the members of which are all the different values that a scalar expression can take on. According to yet another aspect, it is possible to access the various instances of a Reporting Object as members in an OLAP dimension. According to the yet another aspect, it is possible to apply opaque filters or a combination of them to the data that underlies analysis.
TL;DR: In this paper, the authors propose a relational extender for a computer-based relational database, which includes at least one column, in a first, business, table containing a user defined application database, dedicated to object handles for defining the complex data type of an object.
Abstract: This invention is directed to relational extenders for a computer-based relational database. Each relational extender includes at least one column, in a first, business, table containing a user defined application database, dedicated to object handles for defining the complex data type of an object; a second, attribute, table containing at least one column defining a unique characteristic associated with the one object and one column dedicated to containing the object handle; and a third, metadata, table containing at least one column defining a common characteristic associated with all objects defined within the business table and one column dedicated to containing the object handle and at least one column dedicated to containing a reference to object data associated with the object. The relational extender further includes a fourth table containing a reference to each object handle column defined in the first table, and a fifth table containing the names of the second and third tables for each object defined in the first table.
TL;DR: In this article, a method, apparatus, and article of manufacture for using a relational database management system to support on-line analytical processing (OLAP) systems is described, where a relational schema is defined from a multi-dimensional database definition.
Abstract: A method, apparatus, and article of manufacture for using a relational database management system to support on-line analytical processing (OLAP) systems. A relational schema is defined from a multi-dimensional database definition. The multi-dimensional database definition has one or more dimensions having one or more members. The relational schema includes a fact table and related dimension tables. The fact table has a dimension column for all but one of the dimensions of the multi-dimensional database and a value column for each member of the remaining dimension. The fact table has one or more rows that contain values corresponding to the intersection of the members identified by the dimension columns and the members associated with the value columns. Each dimension table has a row for each member of a dimension. Each row of each dimension table includes a multi-dimensional member identifier and a relational member identifier. A relational database is created based on the defined relational schema. Rows are accessed from the relational database using the multi-dimensional member identifiers by joining the dimension tables to the fact table through the relational member identifiers.
TL;DR: In this paper, a method, apparatus, and article of manufacture for using a relational database management system to support on-line analytical processing (OLAP) systems is described. But the method is not suitable for use in the ODP environment.
Abstract: A method, apparatus, and article of manufacture for using a relational database management system to support on-line analytical processing (OLAP) systems. A multi-dimensional database is represented as a relational schema in the relational database. The multi-dimensional database has one or more dimensions having one or more members. Each value in the multi-dimensional database is identified by the intersection of one member from each dimension. The relational schema includes a fact table and related dimension tables. The fact table has a dimension column for all but one of the dimensions of the multi-dimensional database and a value column for each member of the remaining dimension. The fact table has at least one row that contains the values corresponding to the intersection of the members identified by the dimension columns and the members associated with the value columns. Each dimension table has a row for each member of a dimension. At least one dimension table has one or more attribute columns for holding attribute values for members defined by the dimension table.