Database Conflict Resolution via Local Version Merging

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Central databases face conflicts and data loss when multiple computing devices simultaneously attempt to update the same file, leading to overwrites of different versions, resulting in loss of data and difficulties in determining the current, most up-to-date information.

Innovation Solution

A method is implemented where each computing device generates a local version of the central database file, merges it with the current version upon detecting changes, and replaces the current version with the merged version, resolving conflicts and ensuring data integrity by incorporating changes from both versions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple computing devices simultaneously update the central database file, then the system allows concurrent access and modifications, but data loss occurs when versions overwrite each other

Engineering Contradiction:

Improveconcurrent access capabilityVSAvoiddata integrity

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by generating local versions of the central database file before updates occur. Each computing device creates a local copy that can be modified independently, preventing direct conflicts on the central file. This preliminary versioning allows concurrent access while maintaining data integrity through controlled merging later.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The local version acts as an intermediary between the computing device and the central database file. Instead of multiple devices directly modifying the central file (causing conflicts), each device modifies its own local version, and the system mediates the merging of these local versions back to the central file, preventing data loss.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If the system merges local and current versions of the database file, then data integrity is maintained, but additional processing steps and computational resources are required

Engineering Contradiction:

Improvedata integrityVSAvoidmerging process complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The database file is segmented into local versions and current versions, allowing independent processing of each segment. The merging process handles only the differences between segments rather than the entire file, reducing complexity. Each computing device works with its own local version segment, and conflicts are resolved at the segment level during merging.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of directly modifying the central database file, the system creates copies (local versions) that can be modified independently. This copying mechanism simplifies the merging process because the system only needs to compare and integrate changes from copies rather than managing multiple direct modifications to the original file.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If local versions are generated and stored for each computing device, then concurrent modifications are enabled, but storage space is consumed for maintaining multiple versions

Engineering Contradiction:

Improveconcurrent modification capabilityVSAvoidstorage space

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

Local versions are nested within the overall database structure, with each local version containing only the specific modifications needed by its computing device. Rather than storing complete duplicate copies of the entire database, the system stores nested version information that can be merged back into the central file, optimizing storage efficiency while enabling concurrent modifications.

Inventive Principle:

Principle #7Nested doll (Nesting)

Data Source

PatentEP4485223A1Device, system and method for obviating conflicts in database updates

Publication Date: 2025.01.01 AMADEUS SAS

Figure 1
Figure 2
Figure 3

AI summary

A device, system and method for obviating conflicts in database updates is provided. A computing device generates a local version of a central database file stored at a central database accessible by a plurality of computing devices, including the computing device, the central database file changeable by any of the plurality of computing devices, the local version comprising a copy of the central database file. After generating the local version, and in response to determining that a change has occurred to the central database file, as stored at the central database, the computing device: merges the local version and a current version of the central database file to generate a merged version of the central database file; and replaces, at the central database, the current version of the central database file with the merged version of the central database file.