Database Segmentation for Multi-User Extension Fields
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in efficiently supporting multiple users on a single physical system while maintaining data isolation, as adding extension fields to database tables can be labor-intensive and resource-intensive, leading to high support costs and potential data visibility issues among users.
Innovation Solution
The solution involves separating standard and user-specific extension field values into different database tables, allowing user-specific customizations to be stored and managed independently without altering the column layout of standard database tables, thereby ensuring data isolation and efficient resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If extension fields are added directly to database tables to support user customizations, then customization capability is improved, but data isolation between multiple users deteriorates and maintenance complexity increases
Solution Approach 1:
The patent segments the database table structure into standard fields and extension fields stored in separate tables. The standard data object table contains only standard fields, while extension fields are stored in separate extension field tables with references to the standard data object. This segmentation allows customization without altering the core table structure, maintaining data isolation and reducing maintenance complexity.
Solution Approach 2:
The patent extracts extension fields from the main database table structure and stores them in separate extension field tables. This extraction ensures that user-specific customizations do not affect the standard data object structure, enabling independent maintenance of standard fields while preserving customization capabilities.
2Reliability
If dedicated physical systems are provided for each user to ensure data isolation, then data isolation is improved, but resource utilization deteriorates
Solution Approach 1:
The patent implements a universal database structure where multiple users can share the same physical system through a common standard data object table while maintaining data isolation through separate extension field tables. This multi-functional approach allows a single physical system to serve multiple users without compromising data isolation, improving resource utilization while maintaining reliability.
Solution Approach 2:
The patent uses a nested structure where extension field tables are referenced by the standard data object table. Users can be nested within the same standard data object structure while maintaining their own extension fields, allowing multiple users to coexist on a single physical system with proper data isolation.
3Ease of manufacture
If extension fields are appended to core database tables, then customization is simplified, but data visibility and security between users deteriorates
Solution Approach 1:
The patent segments the storage of standard and extension fields into separate tables, with extension fields containing user-specific data. This segmentation enables simple customization through extension field tables while maintaining strict data visibility control, as each user's extension fields are isolated in their own records.
Solution Approach 2:
The patent introduces extension field tables as intermediary structures between the standard data object and user-specific customizations. These intermediary tables act as mediators that store user-specific data separately, preventing direct visibility of other users' extension fields while maintaining the ability to customize the system.
Data Source
AI summary
Access to a networked application can be provided to multiple users while allowing user-specific extension fields to be created and maintained for exclusive access by the user creating the extension field. A user-customized data object that includes a standard field value of a standard field of a standard data object defined by the networked application and a user-specific extension field value of a user-specific extension field that modifies operation of the networked application for the user and that is not available to other users of the plurality of users can be received from a user for writing to memory. The user-specific extension field value can be separated from the standard field value. The standard field value and the user-specific extension field value can be persisted in a first database table and a second database table, respectively. Related systems, methods, and articles of manufacture are also provided.