Table Alias Metadata for Simplified Query Syntax

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In relational databases, users face complexity in managing data due to the need for on-demand alias creation and processing in Data Manipulation Language (DML) statements, which complicates foreign key relationships and query syntax.

Innovation Solution

Implementing table aliases as metadata within the database management system, allowing users to define Common Table Expressions (CTEs) during table creation, which are then stored and automatically applied in query statements, reducing the need for repetitive alias definitions in DML queries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users include alias creation statements in DML statements for on-demand alias creation, then foreign key relationships can be represented, but DML statements become complicated and data management becomes more difficult

Engineering Contradiction:
Improveforeign key relationship representationVSAvoidDML statement complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary action by automatically creating table aliases in the metadata repository before DML statements are executed. When a table is accessed, the database management system automatically generates and stores the alias, so users don't need to manually include alias creation statements in their DML queries. This resolves the contradiction by maintaining foreign key relationship representation while eliminating DML statement complexity.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If table aliases are created on-demand in DML statements, then foreign key relationships are maintained, but query syntax becomes more complex

Engineering Contradiction:
Improveforeign key relationship maintenanceVSAvoidquery syntax complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The database management system performs self-service by automatically managing table aliases without requiring user intervention in DML statements. The system monitors table access patterns, automatically creates appropriate aliases in the metadata repository, and maintains foreign key relationships autonomously. This resolves the contradiction by maintaining relationship integrity while simplifying query syntax to its natural form.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If automatic table alias implementation is added to the database management system, then query syntax is simplified and readability is enhanced, but system complexity increases

Engineering Contradiction:
Improvequery syntax simplicityVSAvoiddatabase management system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The metadata repository serves as an intermediary layer between the database management system and users. Automatic table alias creation and storage in the metadata repository handles the complexity internally, while users benefit from simplified query syntax. The intermediary absorbs the system complexity without exposing it to users, resolving the contradiction between ease of operation and device complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9946781B2System and method of implementing table aliases
Publication Date: 2018.04.17 SAP SE
  • US9946781B2 patent drawing
  • US9946781B2 patent drawing
  • US9946781B2 patent drawing

AI summary

In some example embodiments, a first alias creation statement is received. The first alias creation statement comprises a first table identifier of a first table, a second table identifier of a second table, a first alias identifier, and a first common table expression, and the first common table expression comprises the first table identifier. A first alias for the second table is generated based on the first alias creation statement, with the first alias comprising the first alias identifier and the first common table expression. The first alias is stored as metadata of the second table. A first query statement is received, with the first query statement comprising the second table identifier and the first alias identifier, and the first query statement is rewritten using the first common table expression based on the first alias identifier to generate a first rewritten query statement.