Custom Field Registry for Schema-Free Table Queries
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional implementations of custom fields in computer programs incur performance overhead and require additional programming effort when performing operations, and integrating the behavior of multiple programs that use the same custom field is cumbersome.
Innovation Solution
Store pairs of custom field identifiers and values within a native field of a table using a non-relational format like JSON, and maintain custom field definitions in a separate registry, allowing operations to be performed efficiently without modifying the table schema.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If custom fields are implemented in conventional ways, then entities can be extended with custom fields, but performance overhead occurs when performing operations on entities with custom fields
Solution Approach 1:
The system segments custom field data from the main entity storage by using a separate custom field registry table. Custom field definitions and values are stored independently from the core entity tables, allowing operations on entities to proceed without processing custom field data unless specifically requested. This segmentation eliminates the performance overhead of carrying custom field structures through all entity operations.
Solution Approach 2:
The patent extracts custom field metadata (definitions, data types, validation rules) from the entity structure and places it in a separate custom field registry. This extraction allows the entity tables to remain simple and efficient while custom field capabilities are maintained through references to the external registry, rather than embedding custom field structures within each entity.
2Adaptability or versatility
If multiple computer programs use the same custom field, then integration is possible, but additional programming effort is required to integrate their behavior
Solution Approach 1:
The custom field registry serves as a universal interface that multiple computer programs can access through standardized queries. The registry stores custom field definitions in a consistent format that can be queried by any program, eliminating the need for program-specific custom field implementations. This universal access mechanism allows different programs to share and integrate custom field behavior without additional integration programming.
Solution Approach 2:
The patent introduces a custom field registry as an intermediary layer between multiple computer programs and the underlying data storage. This intermediary standardizes access to custom fields through a unified query interface, allowing programs to interact with custom fields consistently regardless of the underlying implementation details, thereby reducing integration effort.
3Adaptability or versatility
If custom fields are added to tables, then entities can be extended, but the table schema must be modified
Solution Approach 1:
The patent moves custom field storage from the horizontal dimension (table schema columns) to a vertical dimension (external registry with key-value pairs). Instead of adding columns to entity tables for each custom field, the system uses a separate registry where custom fields are stored as records with field identifiers and values. This dimensional change allows entity tables to remain unchanged while still supporting arbitrary custom fields.
Data Source
AI summary
A method may include obtaining a table including a table schema including definitions of native fields, adding a value of a custom field to the table by inserting, in a native field, a native field value including (i) an identifier (ID) of the custom field and (ii) the value of the custom field, and storing a definition of the custom field in a custom field registry external to the table. The custom field may be undefined by the table schema. The method may further include receiving a request to perform an operation on the table, generating, from the request, a query on a subset of the native fields and the custom field, executing the query to obtain query results, and transmitting, in response to the request, the query results.