Entity-Relationship Model Extension for Data Redundancy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database technologies face challenges in sharing information across higher-level models due to fragmented environments, leading to redundant information provision and increased overhead, particularly for developers who are not SQL experts.
Innovation Solution
Extending the relational model and query language to recognize features of tables and higher-level entity-relationship models by implementing an extension language in the data design language that defines custom-defined semantic structures, allowing for the inclusion of all active elements in queries and enabling chaining of extensions for tables and entities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If multiple higher-level models (OData EDM, RDL, JPA, etc.) are used to add semantics to data models, then data comprehension and ease of use are improved, but information fragmentation and redundancy increase
Solution Approach 1:
The patent merges multiple higher-level modeling approaches (OData EDM, RDL, JPA, ABAP) into a unified entity-relationship model framework. By establishing common semantics and a standardized ERM structure that can represent entities, associations, and relationships in a consistent manner across different platforms, the patent eliminates information fragmentation while preserving the semantic enrichment benefits of each approach.
Solution Approach 2:
The patent creates a universal entity-relationship model that serves multiple functions across different application layers and platforms. The standardized ERM can be used by OData services, ABAP applications, Java Persistence, and other higher-level models simultaneously, allowing the same semantic information to be shared and reused across diverse technologies without requiring separate model definitions for each platform.
2Ease of operation
If multiple higher-level models are used to contribute additional semantics, then data model comprehensibility is improved, but overhead and redundancy increase
Solution Approach 1:
The patent combines semantic definitions from multiple higher-level models into a single unified entity-relationship model. By defining entities, associations, and relationships in one standardized ERM framework, the patent eliminates the need to maintain separate semantic definitions in OData EDM, RDL, JPA, and other models, thereby reducing redundant information while preserving comprehensibility.
Solution Approach 2:
The patent enables semantic information to be copied and reused across different application layers through the standardized ERM. Once entities and relationships are defined in the unified model, they can be referenced and consumed by multiple higher-level models without requiring separate definitions, reducing overhead while maintaining data model comprehensibility across different platforms.
3Productivity
If developers use complex SQL programming to interact with databases, then data retrieval capability is improved, but developer accessibility deteriorates
Solution Approach 1:
The patent introduces the entity-relationship model as an intermediary layer between developers and the underlying SQL database. By providing a standardized ERM framework with entities, associations, and relationships that map to database structures, the patent enables developers to work with high-level semantic models rather than writing complex SQL queries directly, thereby improving accessibility while maintaining data retrieval capability through automated query generation.
Data Source
AI summary
Embodiments extend the relational model and query language to recognize features of tables and higher level entity-relationship models (ERMs). Extension language is implemented in the data design language (DDL) to incorporate tables, entities (and views) having custom-defined/semantic structure, rather than being limited to primitive types (e.g. flat tables as in standard SQL). The extension language includes an indication that a query is to include all active elements for each table extension or entity extension that is active. The extension language can be chained to extend a table or entity that has been extended.