SQL Visualizer Diagrams for Code Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The current textual representation of database SQL statements and procedures is difficult to understand due to its declarative nature and awkward syntax, making code analysis time-consuming and error-prone, especially with long statements containing hundreds or thousands of lines of code.

Innovation Solution

A SQL Visualizer tool that converts textual SQL statements and procedures into graphical diagrams, allowing for easier manipulation and understanding by transforming them into Aptitude SQL Rules and Procedures, enabling users to switch between textual and graphical representations and automatically synchronizing changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If SQL statements are represented in textual form, then the code can be written and executed, but the logical structure becomes difficult to understand and analyze

Engineering Contradiction:
Improveease of understandingVSAvoidlogical structure clarity
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent transforms SQL statements from one-dimensional textual representation to two-dimensional graphical diagrams. This dimensional change allows the logical structure, data flow, and relationships to be visualized spatially, making it easier to understand complex SQL logic that would be obscured in linear text format.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The patent segments SQL statements into distinct graphical components representing different logical operations (SELECT, INSERT, UPDATE, DELETE, JOINs, etc.). Each component is visually separated and labeled, allowing developers to analyze the logical structure piece by piece rather than parsing through continuous text.

Inventive Principle:
Principle #1Segmentation

2Reliability

If SQL statements are written in traditional declarative syntax, then the code can be executed by the database, but the syntax becomes awkward and hard to read

Engineering Contradiction:
Improvedatabase execution compatibilityVSAvoidreadability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a graphical diagram as an intermediary representation between the developer's intent and the database's execution. The diagram serves as a visual mediator that preserves the full executable SQL syntax while presenting it in a more readable graphical format, allowing developers to work with both representations simultaneously.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If SQL procedures contain hundreds or thousands of lines of code, then the functionality can be implemented, but code analysis becomes very difficult and time consuming

Engineering Contradiction:
Improvefunctional capabilityVSAvoidcode analysis time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent converts lengthy linear SQL procedures into compact graphical diagrams where the entire procedure's logical structure can be viewed at a glance. This dimensional transformation compresses what would require scrolling through thousands of lines of text into a single visual page, dramatically reducing analysis time.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The patent merges multiple SQL statements and operations into unified graphical components. Related operations are grouped together visually, allowing developers to understand the overall procedure flow without analyzing each individual line of code separately.

Inventive Principle:
Principle #5Merging (Combining)

4Ease of manufacture

If SQL statements place the end result at the beginning (traditional syntax), then the code follows conventional structure, but the logical flow becomes less transparent

Engineering Contradiction:
Improveconventional code structureVSAvoidlogical flow transparency
Core Design Contradiction:
Ease of manufactureVSEase of operation

Solution Approach 1:

The patent inverts the traditional SQL syntax structure by placing the end result (INSERT, UPDATE, DELETE operations) at the end of the graphical diagram rather than the beginning. This inversion mirrors natural logical flow where inputs and processing steps lead to outputs, making the logical flow more transparent while maintaining the ability to generate conventional SQL.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS9880815B2SQL visualizer
Publication Date: 2018.01.30 APTITUDE SOFTWARE
  • US9880815B2 patent drawing
  • US9880815B2 patent drawing
  • US9880815B2 patent drawing

AI summary

A SQL Visualizer including means for transforming a textual SQL statement into a graphical diagram which represents the textual SQL statement.