Schema-State Data Structures for Querying Unpopulated New Columns

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems face computational errors when accessing new columns in a database table that have not yet been populated with data, leading to incomplete query responses or errors.

Innovation Solution

Implementing a schema-state-based data structure that includes an AS-OF field to identify a specific time associated with the database table, allowing for the addition of missing column headings and providing query responses with null values when necessary, thus preventing errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If new columns are added to a database table without structural revisions, then adaptability is improved, but computational errors occur when accessing unpopulated columns

Engineering Contradiction:
Improveability to access new columnsVSAvoidquery response accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by creating placeholder entries for new columns during schema evolution before actual data is populated. When a column is added to the database table, the system proactively creates placeholder records with null or default values, ensuring the column structure exists in advance. This preliminary structuring prevents computational errors during query execution while maintaining adaptability to new data schemas.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If the database table structure is revised to accommodate new columns, then completeness of data storage is improved, but system complexity increases

Engineering Contradiction:
Improvedata completenessVSAvoidschema evolution complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system implements self-service mechanisms where the database management system automatically handles schema evolution and placeholder creation without requiring complex manual interventions. When new columns are introduced, the system autonomously updates the table structure, creates appropriate placeholder entries, and manages data migration, thereby reducing the operational complexity of schema revisions while ensuring complete data storage capacity.

Inventive Principle:
Principle #25Self-service

3Loss of information

If placeholder entries are created for new columns, then query response completeness is improved, but data storage volume increases

Engineering Contradiction:
Improvequery response completenessVSAvoiddata storage volume
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The system employs disposable placeholder entries that serve their purpose temporarily during schema transitions. These placeholder records are lightweight, minimal-structure entries created solely to enable query execution against new columns. Once actual data is populated into the new columns, the placeholders can be consolidated or removed. This approach ensures complete query responses while minimizing long-term data storage overhead, as the placeholders exist only transiently during the transition period.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentUS20250217365A1Schema-state-based data structure
Publication Date: 2025.07.03 TIGEREYE LABS INC
  • US20250217365A1 patent drawing
  • US20250217365A1 patent drawing
  • US20250217365A1 patent drawing

AI summary

Systems and methods are provided for providing a schema-state-based data structure that enables access to new columns in the database table while preventing computational errors from occurring in accessing the old data. For example, the system may enable multiple queries to be received and query responses/results to be provided. The first query request may comprise a FROM field that identifies a database table and an AS-OF field identifies a second time associated with the database table. Upon confirming that a data cell for a column heading in the fetched record does not have valid data at a first time associated with the AS-OF field and does have valid data at a second time associated with the FETCHED field, adding a null value to the data cell in the fetched record and providing the fetched record for the column heading as a query response to the first query request.