Graph Workspace Object for Unified SQL Graph Queries
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Relational databases face challenges in efficiently querying and processing graph data, as they store relationships implicitly, whereas graph databases store them explicitly, leading to difficulties in combining and retrieving graph and relational data in a unified query result.
Innovation Solution
A computer-implemented method that identifies a graph workspace object and executes declarative language queries on a relational database to access and process graph data, allowing for the combination of graph and relational data in a single query result by using a structured query language (SQL) interface, enabling the use of graph algorithms and data manipulation within a relational database framework.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If graph data is stored in a relational database with implicit relationships, then the database can maintain relational data structures, but querying and processing graph data becomes inefficient and difficult
Solution Approach 1:
The patent introduces a graph workspace object as an intermediary layer between the relational database and graph data. This object provides graph-specific data structures and operations while interfacing with the underlying relational database, allowing efficient graph queries without changing the core relational storage mechanism. The graph workspace translates graph operations into relational database operations, resolving the contradiction between maintaining relational structure and enabling efficient graph processing.
2Productivity
If graph data is stored with explicit relationships in a graph database, then graph querying becomes efficient, but combining graph data with relational data in a unified query becomes difficult
Solution Approach 1:
The graph workspace object is designed to perform multiple functions: it can execute graph-specific queries efficiently on graph data while also integrating with the relational database system to allow combined queries. The workspace provides a universal interface that supports both graph operations (traversals, paths, connections) and relational operations (joins, filters, aggregations), enabling unified queries that combine both data types without sacrificing either efficiency or adaptability.
3Ease of operation
If a relational database is used to store graph data, then the database schema can be maintained, but the interface for querying graph data becomes limited
Solution Approach 1:
The patent segments the query interface into two distinct layers: a graph-specific query language layer for expressing graph operations (traversals, paths, relationships) and a standard SQL layer for relational operations. The graph workspace object acts as a translator between these layers, allowing users to write graph queries in a specialized language while the system handles the translation to relational database operations. This segmentation provides an ease-of-use specialized interface without overwhelming complexity, as each layer focuses on its specific data type.
Data Source
AI summary
A method, a system, and a computer program product for querying graph data. A graph workspace object is identified. One or more parameters for executing a declarative language query are identified. Using the identified parameters, the declarative language query is executed on the identified graph workspace object. Based on the executed declarative language query, one or more tables responsive to a request to access graph data stored in a relational database are processed.