Hierarchical Computations in Relational Database Non-Tree Topologies

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Relational database management systems face challenges in performing hierarchical computations on non-tree-like topologies, which are common in real-world data structures, leading to errors and inefficiencies due to 'corner cases' such as cycles, orphan nodes, and diverse data formats.

Innovation Solution

A method is introduced that transforms non-tree-like topologies into well-formed trees by using a traversal stack to modify attributes and generate a normalized tabular indexed data structure, allowing navigation functions to traverse and compute hierarchical attributes, thereby handling 'corner cases' and diverse data formats.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If hierarchical computations are performed on non-tree-like topologies, then real-world data structures can be processed, but errors and inefficiencies occur due to corner cases

Engineering Contradiction:
Improveability to handle diverse data formatsVSAvoidcomputation accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by detecting non-tree-like topologies before hierarchical computations are executed. It identifies corner cases such as cycles, orphans, and multiple parents in advance, then transforms the data structure into a valid tree topology through attribute modification, ensuring reliable computations without errors

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary transformation layer that converts non-tree-like topologies into tree-like structures. This intermediary step modifies attributes of nodes and relationships to eliminate invalid topological patterns, serving as a mediator between raw diverse data and hierarchical computation requirements

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If non-tree-like topologies are transformed into tree-like structures, then hierarchical computations become reliable, but data structure complexity increases

Engineering Contradiction:
Improvecomputation accuracyVSAvoiddata structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system changes parameters of the data structure by modifying attributes of nodes and relationships. It alters topological properties such as parent-child relationships, hierarchy levels, and node identifiers to transform non-tree topologies into valid trees, maintaining reliability while managing structural complexity through controlled parameter modifications

Inventive Principle:
Principle #35Parameter changes

3Reliability

If traversal stacks and attribute modifications are applied, then corner cases are handled, but processing time increases

Engineering Contradiction:
Improvehandling of corner casesVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary detection and transformation of corner cases before main hierarchical computations. By identifying and resolving non-tree topologies in advance using traversal stacks and attribute modifications, the system prevents time-consuming error handling during computation, optimizing overall processing time

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10671581B2Hierarchical computations of nodes having non-tree topologies in relational database management systems
Publication Date: 2020.06.02 SAP SE
  • US10671581B2 patent drawing
  • US10671581B2 patent drawing
  • US10671581B2 patent drawing

AI summary

Performing hierarchical computations in relational database management systems, where the hierarchical computations are based on tabular input data that builds non-tree topologies by modifying the tabular input data to form tree topologies. One or more nodes, in a hierarchy of nodes, generated from tabular data, can have a non-tree-like topology. One or more attributes of entries in the tabular indexed data structure associated with the one or more nodes having the non-tree-like topology can be modified. The modified attributes can cause the tabular indexed data to form a tree-like topology. The modifying can be based on a type of non-tree-like topology of the one or more nodes having the non-tree-like topology. A navigation function can be selected and applied to the modified tabular indexed data structure to determine a navigation result for traversing the hierarchy of nodes. The navigation result can be provided and the hierarchy traversed.