Custom Tag Definition in Relational Database Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Generating custom tags in large database tables is resource-intensive and often fails due to insufficient computing resources, requiring significant processing and memory to add new columns.
Innovation Solution
A method that reserves empty columns in database tables for custom tags, using a parser to translate between custom tag names and column names through a column mapping stored outside the database, allowing users to define and query custom tags without altering existing table structures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If new columns are added to large database tables to accommodate custom tags, then the database can store custom tag information, but the process becomes resource-intensive and may fail due to insufficient computing resources
Solution Approach 1:
The patent extracts the custom tag mapping functionality from the database table structure itself and places it in a separate mapping table or external storage. This allows custom tags to be stored without physically adding columns to the main data tables, thereby avoiding the resource-intensive column addition process while maintaining the ability to store and retrieve custom tag information.
Solution Approach 2:
The patent introduces a mapping table or mapping mechanism as an intermediary between the custom tag names and the actual column names in the database. This intermediary layer allows users to define custom tags without directly modifying the database schema, reducing the computational resources required while maintaining full functionality for custom tag storage and retrieval.
2Adaptability or versatility
If new columns are added to large database tables to accommodate custom tags, then the database can store custom tag information, but the process is slow and may not complete due to resource constraints
Solution Approach 1:
By extracting the custom tag definition and mapping from the main database table structure to a separate mapping mechanism, the patent enables rapid creation of custom tags without the slow process of adding columns to large tables. This extraction allows custom tags to be defined quickly in the mapping table while the main data tables remain unchanged.
Solution Approach 2:
The patent performs preliminary setup by creating reserved columns or mapping entries in advance, so that when custom tags need to be added, the infrastructure is already in place. This preliminary action eliminates the need for resource-intensive column addition operations at the time of custom tag creation, significantly improving productivity.
3Adaptability or versatility
If column names in database tables are changed to accommodate custom tags, then the database structure reflects custom tags, but the complexity of managing table structures increases
Solution Approach 1:
The patent extracts the custom tag naming and mapping logic from the database table structures and places it in a separate mapping table or external configuration. This separation allows custom tags to be integrated into the database system without actually changing the column names in the data tables, thereby reducing the complexity of table structure management while maintaining custom tag functionality.
Solution Approach 2:
By introducing a mapping table as an intermediary layer between custom tag names and actual column names, the patent simplifies table structure management. The mapping table handles all the complexity of custom tag name mapping, while the main data tables retain their original simple structures, making the system easier to manage.
4Adaptability or versatility
If multiple custom tags are added to large database tables by adding columns, then the database can store multiple custom tags, but the resource requirements increase significantly
Solution Approach 1:
The patent creates a universal mapping table or mapping mechanism that can handle multiple custom tags simultaneously. Instead of adding separate columns for each custom tag to the main data tables (which would require significant computing resources), the system uses a single mapping infrastructure that supports unlimited custom tags, thereby reducing computing resource requirements while maintaining multi-tag capability.
Solution Approach 2:
By extracting the multi-tag storage mechanism from the main data tables to a separate mapping table, the patent enables the storage of multiple custom tags without proportionally increasing the resource requirements of the main tables. The mapping table handles all custom tag mappings efficiently, allowing multiple tags to be managed with minimal additional resources.
Data Source
AI summary
A method includes generating a table in a relational database, the table comprising an empty column reserved for a custom tag. The column has a default column name. The method also includes, in response to an instruction to create the custom tag, generating a column mapping that maps a name of the custom tag to the column name. The column mapping is stored outside the relational database and is used by a parser to translate between the name of the custom tag and the column name.