Dynamic Schema Graphs for Natural Language to SQL Parsing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional Graph Neural Networks (GNNs) for natural language to SQL conversion face challenges due to static graph structures, over-smoothing, and inadequate semantic richness, making them less adaptable to diverse and complex queries, and the process of learning SQL is time-consuming and difficult for users.

Innovation Solution

A system that dynamically tailors the graph structure of GNNs based on input queries, using pre-trained language models to enhance semantic understanding, and employs a hybrid initialization strategy combining traditional methods for improved adaptability and accuracy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional static graph structures are used in GNNs for natural language to SQL conversion, then the model structure is simple and easy to implement, but the adaptability to diverse and complex queries is insufficient

Engineering Contradiction:
Improveadaptability to diverse queriesVSAvoidgraph structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic graph structures that adapt to different natural language queries. The graph structure is no longer static but dynamically constructed based on the semantic content of each query, allowing the model to adjust its processing architecture to match the complexity and requirements of diverse SQL conversion tasks.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent applies different processing strategies to different parts of the graph structure based on local requirements. Different node types and edge relationships in the graph receive specialized handling, allowing the model to optimize processing for specific query patterns while maintaining overall flexibility.

Inventive Principle:
Principle #3Local quality

2Loss of information

If deep GNN layers are used to enhance semantic understanding, then the semantic richness improves, but over-smoothing occurs which degrades node representation quality

Engineering Contradiction:
Improvesemantic richnessVSAvoidnode representation quality
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent dynamically adjusts the depth and structure of GNN layers based on the specific query being processed. Rather than using a fixed deep architecture that causes over-smoothing, the model adapts the number of layers and aggregation strategies to preserve node-specific information while still capturing sufficient semantic context.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments the graph processing into multiple specialized layers with different functions. Instead of a uniform deep architecture, the model divides processing into distinct stages that handle different aspects of semantic understanding, preventing information loss while maintaining representation quality.

Inventive Principle:
Principle #1Segmentation

3Loss of information

If random initialization is used for GNN nodes, then the implementation is simple, but the semantic richness required for nuanced parsing is insufficient

Engineering Contradiction:
Improvesemantic richnessVSAvoidinitialization complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent performs preliminary initialization of GNN nodes using pre-trained language model embeddings before the main processing begins. This preliminary action embeds rich semantic information into the node representations from the start, eliminating the need for complex initialization procedures during training while maintaining high semantic quality throughout processing.

Inventive Principle:
Principle #10Preliminary action

4Measurement precision

If the GNN processes the entire database schema, then comprehensive coverage is achieved, but the processing efficiency decreases due to focusing on irrelevant parts

Engineering Contradiction:
Improvequery accuracyVSAvoidquery processing efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent extracts and processes only the relevant portions of the database schema that are necessary for answering each specific natural language query. Rather than processing the entire schema, the model identifies and isolates the pertinent tables, columns, and relationships, significantly improving processing efficiency while maintaining query accuracy.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the database schema processing into relevant and irrelevant portions, processing only the segmented relevant parts for each query. This segmentation approach maintains comprehensive coverage of necessary information while eliminating waste from processing irrelevant schema elements.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12487998B1Contextual graph dynamics for natural language to SQL conversion
Publication Date: 2025.12.02 DELL PROD LP
  • US12487998B1 patent drawing
  • US12487998B1 patent drawing
  • US12487998B1 patent drawing

AI summary

A method for training a model to generate a structured query language (SQL) output using a natural language input includes receiving a training data set that includes natural language queries, corresponding SQL statements, and a corresponding database. The method also includes extracting query-specific schema from the corresponding database. Further, the method includes embedding the natural language queries and the query-specific schema to generate initialized embeddings, where each initialized embedding corresponds to a natural language query of the natural language queries, and where the corresponding SQL statement is one of the corresponding SQL statements; generating subgraphs based on the initialized embeddings and the natural language queries; training a graph neural network (GNN) using the subgraphs as inputs; generating, using the GNN, refined outputs based on the subgraphs; and training a transformer model using the refined outputs and the natural language queries to obtain a trained model.