Flexible Schema Table Schematization for Database Query Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Relational databases face challenges in loading new data due to the need for administrators to define fixed schemas, which can be a barrier when users lack knowledge about the data, and flexible schema tables introduce inconsistencies and complexity during querying.

Innovation Solution

A method and system for schematizing flexible schema tables to create a view with a fixed schema appearance, by identifying keys and data types, selecting view columns based on conditions, and generating a view that includes these columns and types, allowing database tools to operate without schema changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a fixed schema is used in relational databases, then data organization is consistent and querying is efficient, but loading new data types requires administrator intervention and schema definition

Engineering Contradiction:
Improveease of loading new dataVSAvoidschema management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system automatically discovers data types and generates schema definitions without requiring administrator intervention. The database management system performs self-service by analyzing incoming data streams, identifying patterns, and creating appropriate schema structures autonomously.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary schema generation by analyzing data samples before full data loading occurs. This preliminary action includes discovering data types, determining field structures, and preparing schema definitions in advance to facilitate smooth data ingestion.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If a flexible schema table is used, then loading new data is simplified, but querying becomes inconsistent and complex

Engineering Contradiction:
Improveflexibility in data loadingVSAvoidquery consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments the flexible schema into multiple standardized views, each representing a consistent data structure. By dividing the heterogeneous data into organized segments with defined schemas, the system maintains query consistency while preserving the ability to handle diverse data types.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary layer that translates between flexible data inputs and standardized schema representations. This mediator component ensures that diverse data sources are converted into consistent formats suitable for reliable querying and analysis.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Stability of the object's composition

If administrators manually define schemas, then data structure consistency is ensured, but the process is time-consuming and requires specialized knowledge

Engineering Contradiction:
Improveschema consistencyVSAvoidtime for schema definition
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The system replaces the manual mechanical process of schema definition with an automated discovery mechanism. Instead of administrators manually analyzing and defining schemas, the system uses automated data analysis algorithms to infer and generate schema definitions, significantly reducing time and expertise requirements.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system implements feedback loops where data sampling results are continuously analyzed and used to refine schema definitions. This iterative feedback process ensures schema consistency while automatically adapting to data patterns, eliminating the need for time-consuming manual schema design.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11042516B2Flexible schema table
Publication Date: 2021.06.22 MICRO FOCUS LLC
  • US11042516B2 patent drawing
  • US11042516B2 patent drawing
  • US11042516B2 patent drawing

AI summary

In an example, a flexible schema table may be schematized. Records from the flexible schema table may be queried and, for keys in the records, a data type is estimated for each key. View columns may then be selected from the keys based on a predetermined condition. A view of the flexible schema table may be created from the selected view columns, wherein the view includes the view columns and the data types for the view columns.