Database Part Table Junctioning via Schema Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database software applications do not allow users to define relationships between database template tables and existing database tables, limiting the ability to merge or join them effectively.
Innovation Solution
A schema-based approach is implemented in database applications to merge database part tables with source tables by receiving metadata in markup language files, specifying join types, and using a protocol for communication with database web services to define and utilize join relationships between tables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If database applications allow template tables to be joined with existing database tables, then data integration capability is improved, but system complexity increases due to requiring schema definitions and metadata management
Solution Approach 1:
The patent introduces a schema as an intermediary component that defines the join relationship between template tables and existing database tables. The schema contains metadata including source table identifiers, target table identifiers, and join type specifications, serving as a mediator that enables data integration without directly implementing the complex joining logic in the application layer.
Solution Approach 2:
The patent implements preliminary action by requiring that join relationships be pre-defined in schema files before data operations are performed. The metadata describing source tables, target tables, and join types is prepared in advance in markup language files, allowing the database application to efficiently execute pre-planned data integration operations without complex runtime decision-making.
2Adaptability or versatility
If a schema-based approach with markup language files is used to define join relationships, then flexibility in defining relationships is improved, but ease of operation deteriorates due to requiring metadata configuration
Solution Approach 1:
The patent implements self-service by enabling the schema and metadata files to automatically define their own structure and content according to predefined markup language specifications. The system self-configures the join relationships by reading the metadata in the markup language files, which contain all necessary information about source tables, target tables, and join types, eliminating the need for manual configuration interfaces.
3Manufacturing precision
If metadata is received and processed to merge tables, then data integration accuracy is improved, but processing time increases due to metadata parsing and interpretation
Solution Approach 1:
The patent applies preliminary action by pre-defining all join relationship metadata in structured markup language files before data integration operations. The source table identifiers, target table identifiers, and join types are specified in advance in the schema, allowing the database application to quickly parse and execute pre-planned operations without complex runtime analysis, thus reducing processing time while maintaining accuracy.
Data Source
AI summary
Embodiments are provided to define relationships for merging template or database part tables with one or more database tables in a computer system. A database application may utilize a schema to receive metadata associated with a target database part table in one or more markup language elements. The database application may then receive metadata associated with a source database table to be joined with the target table in the schema elements. The database application may then receive join type metadata in the schema elements. The join type metadata may specify whether fields from the source table are to be merged into the target table or whether fields from the target table are to be merged into the source table. In response to receiving the target table metadata and the source table metadata, the database application may then merge the target and source tables utilizing the join type metadata.