Nested Relational Entity Provider for ORM Mapping

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing object-relational mapping (ORM) technologies are not natively compatible with nested relational and hierarchical databases, as they require Structured Query Language (SQL) support and normalization to First Normal Form, which is not applicable to these data models.

Innovation Solution

A method and system for mapping objects and object relationships in an object-oriented programming language to nested relational databases without normalizing the data, using industry-standard ORM technologies like JPA and .NET Entity Framework, and employing native APIs for efficient data access, allowing for the creation of nested relational entity providers that recognize and manage one-to-many relationships within the database's native structure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional ORM technologies are used with nested relational databases, then SQL support and normalization to First Normal Form are required, but this increases complexity and reduces efficiency for nested relational data models

Engineering Contradiction:

Improvecompatibility with nested relational databasesVSAvoidnormalization requirement

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a nested relational entity provider as an intermediary layer between the ORM framework and nested relational databases. This provider translates ORM operations into native nested relational database operations, eliminating the need for SQL and normalization while maintaining compatibility with standard ORM technologies like JPA and .NET Entity Framework.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The invention changes the fundamental parameters of database interaction by switching from SQL-based access to native nested relational API access. This parameter change allows direct manipulation of nested relational structures without requiring normalization to First Normal Form, thereby reducing complexity while improving adaptability.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If SQL and normalization are used for nested relational databases, then standard ORM compatibility is achieved, but performance and efficiency are reduced

Engineering Contradiction:

ImproveORM standard complianceVSAvoiddata access efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The nested relational entity provider serves as a mediator that maintains ORM standard compliance while enabling efficient native access. It intercepts standard ORM operations and translates them into optimized native nested relational database operations, achieving both standard compliance and high performance.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The solution segments the data access layer into a specialized nested relational entity provider that handles nested relational databases separately from the general ORM framework. This segmentation allows optimized native API access for nested relational data while maintaining compatibility with standard ORM operations through the provider interface.

Inventive Principle:

Principle #1Segmentation

3Productivity

If native nested relational APIs are used instead of SQL, then performance improves, but compatibility with existing ORM technologies is lost

Engineering Contradiction:

Improvedata access performanceVSAvoidORM framework compatibility

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The nested relational entity provider implements a universal interface that works with both standard ORM frameworks and native nested relational databases. It provides multi-functionality by supporting standard ORM operations (create, read, update, delete) while utilizing efficient native APIs underneath, thereby achieving both compatibility and performance.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The entity provider acts as an intermediary that translates standard ORM operations into native nested relational API calls. This mediation layer preserves ORM framework compatibility while enabling the performance benefits of native APIs, as it maps high-level ORM operations to low-level efficient database operations.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8260824B2Object-relational based data access for nested relational and hierarchical databases

Publication Date: 2012.09.04 ROCKET SOFTWARE

AI summary

Mechanisms are provided for mapping objects and object-relationships in an object-oriented programming language to a nested relational database. Entity metadata constructs for an object relational mapping framework are obtained, the entity metadata constructs mapping fields in entities of an object model to fields in a data table of the nested relational database and identifying relationships between entities in the object model. A nested relational data model of the nested relational database is obtained, the nested relational data model specifying tables and sub-tables of the nested relational database. Tables and sub-tables of the nested relational database are mapped to a plurality of separate entities of the object model. Data in the nested relational database is accessed using the plurality of separate entities. The mapping is performed without normalizing the data of the tables and sub-tables of the nested relational database to a non-nested representation.