Web Database Concurrent Editing Conflict Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web database systems lack convenience in concurrent editing operations, as users are not notified of editing by others until an error message appears, leading to loss of input data and increased user burden.
Innovation Solution
A web database system that determines if a record has been or is being edited through one interface and executes processing on another interface to reflect these changes, displaying notifications to users to prevent data loss and enhance user experience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If error message is displayed only when editing conflict occurs, then system complexity is reduced, but user convenience deteriorates as users are not notified of ongoing edits
Solution Approach 1:
The system performs preliminary detection of editing status before a conflict actually occurs. When user B attempts to edit a record, the system proactively checks whether user A is already editing or has recently edited that record, and displays a notification to user B before any conflict arises. This prevents the need for complex post-conflict resolution mechanisms.
Solution Approach 2:
The system implements continuous feedback by monitoring editing status in real-time and providing notifications to users about ongoing edits. This feedback loop allows users to be aware of concurrent editing activities and take appropriate actions, simplifying the overall system by making conflict prevention transparent to users.
2Reliability
If page refresh is required after editing conflict, then data consistency is ensured, but loss of input data occurs and user burden increases
Solution Approach 1:
The system provides preliminary notification to users about ongoing edits before they attempt to save their changes. This early warning allows users to preserve their work or coordinate with other editors, preventing the need for page refreshes that would cause data loss.
Solution Approach 2:
The system takes preliminary anti-action by preventing the editing operation before a conflict occurs. When a user is notified that another user is editing the same record, the system blocks the potentially conflicting operation, thereby preventing the need for corrective actions like page refreshes that would result in data loss.
3Ease of operation
If concurrent editing is allowed without notification, then ease of operation is improved, but reliability deteriorates as users cannot notice editing by others
Solution Approach 1:
The system implements feedback by continuously monitoring editing status and providing real-time notifications to users about ongoing edits on records they are viewing or editing. This maintains ease of concurrent editing while ensuring users are aware of other users' activities through the notification mechanism.
Data Source
AI summary
Provided is a web database system, which allows concurrent editing operations of a web database through a plurality of interfaces, the web database system including at least one processor configured to: determine one of whether the web database has been edited through a first interface among the plurality of interfaces or whether the web database is being edited through the first interface; and execute predetermined processing relating to the web database for a second interface among the plurality of interfaces in one of a case in which it has been determined that the web database has been edited through the first interface or a case in which it has been determined that the web database is being edited through the first interface.