Abstract Column Type Inference for Database Table Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data platforms require manual identification and conversion of column data types during table creation or migration, which is time-consuming and resource-intensive, especially for large datasets.

Innovation Solution

Automatically determining and updating column data types in a database by processing data records, allowing for the use of abstract default types and selective conversion to standard types based on compatible data types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual data type identification is performed, then data type accuracy is ensured, but time consumption and resource usage increase significantly

Engineering Contradiction:
Improvedata type identification accuracyVSAvoidtime for table creation and migration
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system automatically infers data types by analyzing sample data records without requiring manual user input. The database engine autonomously determines column data types based on the actual data values inserted, eliminating the need for users to manually specify data types while maintaining accuracy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs data type inference in advance during table creation or migration operations by analyzing sample data records before finalizing the table schema. This preliminary analysis allows the system to pre-determine appropriate data types, avoiding time-consuming manual checks later.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If explicit column data types are provided, then data integrity is maintained, but the complexity of table creation and migration processes increases

Engineering Contradiction:
Improvedata integrityVSAvoidtable creation and migration process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The database system automatically determines and assigns appropriate data types to columns based on analyzed sample data, eliminating the need for users to manually specify data types. This self-service approach maintains data integrity through automated type inference while significantly reducing the complexity of table creation and migration processes.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If data type conversion is performed for platform migration, then compatibility between different platforms is achieved, but processing time and computational resources increase

Engineering Contradiction:
Improveplatform compatibilityVSAvoidmigration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs data type analysis and conversion determination in advance during the migration process by examining sample data records. This preliminary action allows the system to pre-identify required conversions and optimize the migration process, reducing overall migration time while maintaining platform compatibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The migration system automatically determines and executes data type conversions based on analyzed sample data without requiring manual intervention. The system self-determines the appropriate conversion paths between different platform data types, achieving compatibility while minimizing processing time and resource consumption.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10545984B2Abstract default column type in tables
Publication Date: 2020.01.28 SAP SE
  • US10545984B2 patent drawing
  • US10545984B2 patent drawing
  • US10545984B2 patent drawing

AI summary

Methods, systems, and computer-readable storage media for providing a table in a database system, the table including a column having a column data type set to an abstract data type, receiving a first data record to be added to the table, the first data record including a first data value to be included in the column, determining a first data type corresponding to a data type of the first data value, changing the column data type from the abstract data type to the first data type, receiving a second data record to be added to the table, the second data record including a second data value to be including in the column, determining a second data type corresponding to the data type of the second data value, and selectively changing the column data type to the second data type.