Foreign Key Constraint Resolution via Entity Relationship Graph Ordering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems face delays and resource-intensive computations when executing queries due to the need to resolve foreign key constraints, which can lead to inefficient query execution in relational databases.

Innovation Solution

The method involves generating an entity relationship model to determine relationships between database tables, creating a graph to represent these relationships, assigning ordering numbers to database elements, and executing queries based on these ordering numbers to optimize query processing and resolve foreign key constraints efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional systems execute queries by resolving foreign key constraints in a specific order, then data integrity is maintained, but query execution time increases and computational resources are consumed

Engineering Contradiction:
Improvedata integrityVSAvoidquery execution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary analysis of foreign key constraints and pre-determines an optimized execution order for query statements before actual query execution. By analyzing the dependency relationships between tables and pre-calculating the optimal statement sequence, the system prepares execution plans in advance that maintain data integrity while minimizing execution time during actual query processing

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables queries to self-resolve foreign key constraints by automatically determining the execution order based on pre-analyzed dependency relationships. The query execution mechanism itself performs the constraint resolution without requiring external intervention or manual ordering, making the system self-sufficient while optimizing performance

Inventive Principle:
Principle #25Self-service

2Reliability

If conventional systems resolve multiple foreign key constraints independently, then each constraint is properly enforced, but the number of computations increases and processing efficiency decreases

Engineering Contradiction:
Improveconstraint enforcementVSAvoidprocessing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system merges the resolution of multiple foreign key constraints into a unified execution plan by analyzing all constraint relationships simultaneously. Instead of processing each constraint independently, the system combines them into a single optimized statement execution sequence that satisfies all constraints while reducing the total number of computational operations required

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system creates a universal execution framework that handles multiple types of foreign key constraints (one-to-one, one-to-many, many-to-many relationships) through a single optimized process. This multi-functional approach allows the same execution mechanism to efficiently resolve various constraint types without requiring separate processing logic for each constraint type

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS8010521B2Systems and methods for managing foreign key constraints
Publication Date: 2011.08.30 SAP SE
  • US8010521B2 patent drawing
  • US8010521B2 patent drawing
  • US8010521B2 patent drawing

AI summary

Systems and methods consistent with the invention may include generating, via a processor, an entity relationship model to indicate a plurality of types of relationships between the entities, determining relationships between the database tables corresponding to the entities by using the entity relationship model, wherein the database tables are stored in a computer memory device, generating a graph based on the entity relationship model, generating sets of database elements representing the entities and corresponding data objects stored in the database tables, wherein the element sets are generated based on the generated graph, assigning ordering numbers to the database element sets and database elements included in the database element sets and executing the query transaction by using the data objects in an order based on the ordering numbers.