Dynamic Database Views for Loosely Typed Schema Querying

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Data repositories using loosely typed schemas face challenges in querying and reporting due to the lack of relational correspondences between data and metadata, making it difficult for users to access domain-specific data using their preferred terminology.

Innovation Solution

The dynamic generation of database views and class objects based on metadata allows users to query domain data using specific terminology by mapping user queries to the corresponding database views and class objects, enabling retrieval of data from repositories with generic structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is stored using a loosely typed schema to facilitate configurability and model evolution, then adaptability is improved, but ease of operation deteriorates because relational tools cannot work on the repository and users cannot query data using domain-specific terminology

Engineering Contradiction:

ImproveconfigurabilityVSAvoidquery capability

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary layer consisting of database views and class objects that mediate between the loosely typed repository schema and the user's domain-specific query needs. The database views are dynamically generated to provide a strongly typed interface, while class objects serve as intermediaries that map domain concepts to repository structures, enabling users to query using domain-specific terminology without changing the underlying loose schema

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the data access interface from the storage structure by creating separate database views for different domain types. Each view is segmented to handle specific domain concepts (e.g., software types, music types, service types), allowing users to interact with data in domain-specific contexts while the underlying repository maintains its flexible loose schema

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If generic repository tables are used to store domain data, then adaptability is improved, but device complexity increases due to the need for dynamic generation of database views and mapping information

Engineering Contradiction:

Improvemodel evolutionVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent employs dynamic generation of database views and class objects based on metadata from the repository. This dynamic approach allows the system to adapt to different domain models and configurations automatically, reducing the need for manual setup and lowering operational complexity despite the flexible schema. The mapping information is generated dynamically to connect domain concepts with repository structures

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system performs self-service by automatically generating database views, class objects, and mapping information from the repository metadata. This automation reduces the complexity burden on users, as the system adapts to domain model changes without requiring manual intervention to create or update access interfaces

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If loosely typed tables are used to store domain data and metadata, then adaptability is improved, but loss of information occurs because there are no relational correspondences among related data and metadata

Engineering Contradiction:

Improveschema flexibilityVSAvoidrelational correspondence

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent uses database views as intermediaries that restore relational correspondences between related data and metadata. The views are generated to explicitly define relationships between domain entities, allowing users to access related data with proper contextual relationships even though the underlying storage uses loose typing without enforced referential integrity

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10509775B2Dynamic generation of database views and class objects for providing access to repository data

Publication Date: 2019.12.17 ORACLE INT CORP

AI summary

Techniques for dynamically generating database views and class objects for allowing access to domain data stored in a repository are provided. A computer-implemented method, a system, and/or a machine-readable medium storing instructions executable by one or more processors may include generating a database view and a class object using metadata included in a domain model, and retrieving domain data from a repository using the database view and the class object. For example, a method may include obtaining a domain model from a repository, the domain model including metadata corresponding to a set of domain data stored in the repository, generating a database view of a subset of the set of domain data using the metadata, generating a class object for the subset using the metadata, generating mapping information, and retrieving the subset of domain data from the repository using the database view, the class object, and the mapping information.