Latent Data Type Annotations for DBMS Format Support

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Database management systems (DBMS) face challenges in supporting new data formats without creating dedicated data types, as adding new data types is costly and restricts flexibility, and existing methods require extensive code changes and client modifications.

Innovation Solution

The technique involves using latent data types, where values are stored as recognized data types but annotated with latent data type information, allowing DBMS to process them accordingly through operand flags and annotations like 'TREAT AS' in database statements, enabling support for new data formats without dedicated types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a dedicated data type is added to support a new data format, then the DBMS can perform operations on data in that format, but the implementation cost and complexity increase significantly

Engineering Contradiction:

Improvedata format support capabilityVSAvoidDBMS implementation complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary mechanism (type annotation system with TREAT AS clauses and operand flags) that bridges the gap between existing recognized data types and new latent data formats. This allows the DBMS to handle new data formats without creating dedicated data types, as the annotation system mediates between the stored recognized type and the intended latent type for operation selection.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent makes existing recognized data types multi-functional by allowing them to represent multiple latent data formats through annotations. A single recognized data type can serve as the storage vehicle for various latent data formats (XML, JSON, etc.), eliminating the need for separate dedicated data types for each format and reducing overall system complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If a new dedicated data type is created for each data format, then data format specific operations can be performed, but standards adoption time increases

Engineering Contradiction:

Improvedata format operation capabilityVSAvoidstandards adoption time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent establishes a preliminary framework (annotation system with TREAT AS clauses) that prepares the DBMS to handle new data formats immediately upon introduction, without waiting for formal standards adoption. The system can annotate existing recognized data types with latent data type information, enabling operations on new formats before dedicated data types are formally created through standards processes.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If existing DBMS functionalities are updated to support new data types, then client operability improves, but code changes and testing requirements increase

Engineering Contradiction:

Improveclient operability with new data formatsVSAvoidcode changes and testing effort

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent uses copying by creating virtual representations of data types through annotations rather than creating physical new data type structures. The TREAT AS clauses and operand flags create a logical copy or overlay on existing recognized data types, allowing new format operations without modifying the underlying data type implementations or client code.

Inventive Principle:

Principle #26Copying

4Adaptability or versatility

If data is converted to recognized data types for storage, then DBMS compatibility is maintained, but processing performance decreases

Engineering Contradiction:

ImproveDBMS compatibilityVSAvoiddata processing performance

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent maintains continuity of useful action by preserving the original data format characteristics through latent data type annotations while storing data in recognized types. The annotation system continuously tracks the latent data type information through query processing, enabling format-specific operations without actual data conversion, thus maintaining both compatibility and performance.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS11409741B2Enabling data format specific database functionalities over existing data types by marking operand values

Publication Date: 2022.08.09 ORACLE INT CORP

AI summary

Functionalities of new data types are enabled for data stored using native data types (“recognized data types”) supported by DBMSs. Values having a latent data type may be stored using a recognized data type of a DBMS. That is, a value stored in a database table may be recognized by a DBMS as having a recognized data type (e.g., character string) but the value may also include information that indicates the value conforms to a particular latent data type. DBMSs compile database statements. The database statement can contain multiple expressions that may specify a latent data type or that may have a recognized data type but that also imply latent data types. By determining that various expressions have latent data types, operations that rely on the expressions as having a latent data type may be validated in a query and executed accordingly.