Native JSON Data Type Validation in RDBMS

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database systems face inefficiencies in validating JSON objects against schemas and executing queries on JSON data, particularly in relational database management systems (RDBMS) that lack effective mechanisms for schema-based validation and efficient query execution.

Innovation Solution

Implementing techniques that enhance JSON schema validation and query execution by using native JSON data types, coincident validation, schema-informed rewrites, and augmented data types, along with caching metadata in volatile memory for quicker access, to improve performance and efficiency in JSON schema validation and query execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If JSON objects are stored in varchar or CLOB columns with SQL/JSON operators, then JSON text storage is supported, but validation efficiency and query performance deteriorate

Engineering Contradiction:
ImproveJSON schema validationVSAvoidvalidation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent creates JSON schema constraints that define validation rules in advance before data is inserted or updated. The database system pre-compiles these schemas into an optimized format, performing validation preparation work beforehand rather than during data operations, thus improving validation efficiency without sacrificing reliability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments JSON validation into distinct phases: schema compilation, constraint creation, and actual validation execution. By separating schema processing from data validation and caching compiled schemas, the system reduces the computational overhead during validation operations, resolving the contradiction between thorough validation and efficiency

Inventive Principle:
Principle #1Segmentation

2Productivity

If native JSON data type is implemented, then query execution efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvequery execution efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a native JSON data type that serves multiple functions: it provides efficient storage, enables optimized query execution with JSON operators, and integrates with the existing relational database architecture. This multi-functional approach allows the system to gain query performance benefits without proportionally increasing complexity, as the JSON type leverages existing database infrastructure

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces JSON operators as intermediary tools that bridge the gap between native JSON data types and SQL query language. These operators provide a standardized interface for querying JSON data, allowing the database system to handle JSON complexity through a layer of abstraction while maintaining efficient native JSON processing underneath

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If schema validation is performed thoroughly, then data quality is improved, but computational resources increase

Engineering Contradiction:
Improvedata qualityVSAvoidcomputational resources
Core Design Contradiction:
Manufacturing precisionVSUse of energy by moving object

Solution Approach 1:

The patent pre-compiles JSON schemas into an optimized internal format during constraint creation, performing the computationally intensive schema processing work beforehand. This preliminary compilation allows the actual validation operations to execute more efficiently with reduced computational resources, maintaining high data quality standards while lowering runtime resource consumption

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent caches compiled JSON schemas in memory, allowing the database system to reuse pre-processed validation rules across multiple validation operations. This continuous caching approach eliminates redundant compilation work and reduces computational resource usage for subsequent validations, maintaining thorough data quality checks with optimized resource consumption

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS20240126726A1Techniques for comprehensively supporting JSON schema in a rdbms
Publication Date: 2024.04.18 ORACLE INT CORP
  • US20240126726A1 patent drawing
  • US20240126726A1 patent drawing
  • US20240126726A1 patent drawing

AI summary

JSON schemas are implemented efficiently within a DBMS. Through these techniques, the power and benefit of schema-based paradigm are realized in a more cost-effective manner in terms of computer system performance. JSON schema-based techniques described herein improve execution efficiency of database statements that access JSON objects and improve software development productivity.