Database Query Parser Optimizing UDT Method Execution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional parsers face inefficiencies when processing queries with nested user-defined data type (UDT) methods, leading to redundant instantiations and invocations that increase processing time and degrade database performance.

Innovation Solution

A parser technique that transforms database queries with UDT methods into a specified format, removing redundant instantiations and invocations by grouping, ordering, and combining mutated set clauses, thereby optimizing query execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional parsers process queries with nested UDT methods, then the queries can be executed, but redundant instantiations and invocations increase processing time and degrade performance

Engineering Contradiction:

Improvequery processing efficiencyVSAvoidprocessing time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The parser performs preliminary analysis of nested UDT method invocations during the parsing phase, identifying and marking redundant instantiations before query execution. This preliminary action allows the system to prepare an optimized execution plan that eliminates unnecessary method calls, thereby reducing processing time during actual query execution while maintaining correct query processing

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The invention changes the parameter representation of UDT instantiations by tracking and comparing method invocation contexts. When the parser detects that a UDT method is being invoked with identical parameters and context as a previous invocation, it modifies the execution parameters to reuse the existing instantiation rather than creating a new one, thereby eliminating redundant processing and reducing overall query execution time

Inventive Principle:

Principle #35Parameter changes

2Ease of operation

If conventional parsers resolve nested UDT methods by re-writing queries, then method nesting is handled, but redundant instantiations and invocations are created

Engineering Contradiction:

Improvequery parsing capabilityVSAvoidquery structure complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The parser extracts the essential information from nested UDT method invocations by analyzing the method call stack and identifying the effective instantiation requirements. Instead of blindly re-writing the entire query structure, the system extracts only the necessary method invocations and their parameters, eliminating redundant nested calls while preserving the essential query logic and maintaining operational simplicity

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

During the parsing phase, the system performs preliminary analysis to determine the minimal set of UDT instantiations required for query execution. By pre-computing which method invocations are necessary and which are redundant, the parser can generate a simplified query representation that maintains ease of operation while reducing structural complexity and eliminating unnecessary nesting

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS10025588B1Parsing of database queries containing clauses specifying methods of user-defined data types

Publication Date: 2018.07.17 TERADATA US INC

AI summary

A database system includes a parser that is capable of parsing database queries containing user-defined data type (UDT) methods. The database query is transformed by the parser into a statement according to a specified format. In performing the transformation, redundant instantiations of UDTs and invocations of methods are removed. In one implementation, the redundant instantiations and invocations are removed by grouping and combining clauses containing UDT methods.