Query Validator for Semantic Error Detection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Programming in query languages like SQL is prone to errors such as typos or improper table names, which may not be detected until execution, leading to costly and time-consuming issues at customer sites due to lack of developer experience with the database schema.

Innovation Solution

A method that analyzes syntax-correct queries for potential issues by applying user-defined validations, including generic and application-specific checks, to provide warnings and suggestions for improving query accuracy, performance, and preventing future errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a query is compiled with basic syntax checking, then syntax errors are detected, but semantic errors and potential issues remain undetected until execution

Engineering Contradiction:

Improvequery correctnessVSAvoidvalidation system complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs query validation during the compilation phase before execution, applying multiple validation rules to detect semantic errors, performance issues, and potential problems in advance. This preliminary action prevents errors from reaching the execution stage, improving reliability without requiring complex runtime validation systems.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The validation system is divided into multiple independent validation rules, each targeting specific aspects of query correctness (syntax, semantics, performance, best practices). This segmentation allows the system to provide comprehensive validation while maintaining modularity and manageability, avoiding the need for a monolithic complex validation system.

Inventive Principle:

Principle #1Segmentation

2Manufacturing precision

If comprehensive validation rules are applied to all queries, then query quality improves, but validation time and processing overhead increase

Engineering Contradiction:

Improvequery accuracyVSAvoidvalidation time

Core Design Contradiction:

Manufacturing precisionVSLoss of time

Solution Approach 1:

The system applies validation rules selectively based on query characteristics and configured validation levels. Not all validation rules are applied to every query - the system determines which rules are relevant and applies only those, providing sufficient validation without the full overhead of comprehensive validation on every query.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

Validation is performed during the compilation phase as a preliminary step before query execution. By catching and reporting validation issues during compilation rather than during execution, the system minimizes the time impact on actual query processing while ensuring query quality.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If developer experience with database schema is increased, then query errors decrease, but training time and cost increase

Engineering Contradiction:

Improvequery error rateVSAvoiddeveloper training time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The validation system provides immediate feedback to developers during query compilation, highlighting semantic errors, potential issues, and suggestions for improvement. This real-time feedback mechanism helps developers learn correct query patterns and database schema relationships without requiring extensive formal training, as errors are corrected through guided feedback rather than memorization.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system empowers developers to self-correct their queries by providing specific validation messages and suggestions that guide them toward correct query formulations. Rather than requiring external training, developers can independently improve their query writing skills by learning from the validation feedback on their own code.

Inventive Principle:

Principle #25Self-service

4Reliability

If errors are detected at customer site during execution, then runtime failures are identified, but fixing costs and time increase significantly

Engineering Contradiction:

Improveruntime error detectionVSAvoiderror fixing difficulty

Core Design Contradiction:

ReliabilityVSEase of repair

Solution Approach 1:

The validation system detects and reports semantic errors, performance issues, and potential problems during the compilation phase at the development site, before queries are deployed to the customer environment. This preliminary detection prevents runtime failures at the customer site, eliminating the need for costly and time-consuming remote debugging and fixes.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system applies validation rules that prevent problematic queries from being compiled or deployed in the first place. By proactively identifying and blocking queries with semantic errors, performance issues, or schema mismatches before they reach the customer site, the system prevents runtime failures rather than merely detecting them during execution.

Inventive Principle:

Principle #9Preliminary anti-action

Data Source

PatentUS8856166B2Query validator

Publication Date: 2014.10.07 SAP SE

AI summary

According to some embodiments, a method and apparatus are provided to receive a syntax correct query, analyze the syntax correct query, and output a message associated with the syntax correct query.