Database Catalog Metadata Extensions for Schema Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing database management systems face challenges in managing differences between the data schema of stored database objects and the schema required by user applications, leading to a tedious and error-prone mapping process.
Innovation Solution
A database system that includes a database catalog with additional metadata describing properties, attributes, or characteristics of database objects, which is compiled using a database compiler and stored in the catalog, allowing for dynamic attachment, alteration, or removal of metadata, and includes views with metadata that can be propagated or aggregated.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If database objects are accessed using fixed database schema and metadata in database catalog, then data access is standardized and organized, but mapping to application-specific data schema formats becomes tedious and error-prone
Solution Approach 1:
The patent introduces additional metadata as an intermediary layer between the fixed database schema and application-specific data schema formats. This additional metadata contains application-specific information (such as UI labels, display formats, and validation rules) that mediates the mapping between the database structure and application requirements, eliminating the need for manual mapping processes.
Solution Approach 2:
The patent segments the metadata into two distinct parts: standard metadata (stored in the database catalog) that describes database objects, and additional metadata (stored separately) that describes application-specific requirements. This segmentation allows each layer to be independently managed and updated without affecting the other, simplifying the overall system complexity.
2Reliability
If manual mapping process is used to synchronize database objects with application data schema, then schema differences can be addressed, but the process is tedious and error-prone
Solution Approach 1:
The system performs self-service by automatically generating and maintaining the additional metadata based on the database object definitions. The database compiler automatically creates the additional metadata when database objects are created or modified, eliminating the need for manual mapping operations and reducing errors associated with manual processes.
Solution Approach 2:
The additional metadata is generated in advance during database object creation or modification, before the data needs to be accessed by applications. This preliminary action ensures that all necessary mapping information is already prepared and available, eliminating time-consuming manual mapping operations later.
3Adaptability or versatility
If database structure changes occur, then database can adapt to new requirements, but client application scripts require modifications to accommodate schema changes
Solution Approach 1:
The patent introduces dynamic additional metadata that can be automatically updated when database structures change. The additional metadata acts as a dynamic layer that adapts to database changes without requiring application script modifications, allowing the system to maintain flexibility while keeping application code stable.
Solution Approach 2:
The system implements feedback mechanisms where changes to database objects automatically trigger updates to the additional metadata. This feedback loop ensures that the additional metadata always reflects the current database structure, eliminating the need for manual updates to application scripts when database changes occur.
Data Source
AI summary
A computer-implemented method for managing the differences in the schema of data stored in a database and the schema of data as consumed by a client application. The method involves creating additional metadata related to a property, attribute, or characteristic of a database object stored in the database, storing this additional metadata in a database catalog, and making the additional metadata available for access or retrieval by a query received from the client application for the database object stored in the database.