Database Table Comparison via Partner Row Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for comparing two data tables in a database context often result in lengthy and complex outputs, making it difficult for users to identify meaningful differences between the tables.
Innovation Solution
The proposed solution involves sorting the data tables by common key and comparison fields, creating a matches table for partner rows, and using a duplicate-aware row matching technique to compare and populate a results table, thereby isolating meaningful changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If existing row-by-row comparison methods are used, then all differences between tables are identified, but the results become unnecessarily long and difficult to understand
Solution Approach 1:
The patent segments the comparison process into distinct phases: identifying partner rows based on key fields, comparing only those partner rows, and separately handling unpartnered rows. This segmentation allows the system to focus computational effort on meaningful comparisons while filtering out irrelevant differences, thus maintaining measurement precision without information overload.
Solution Approach 2:
The patent extracts and isolates the essential comparison elements (partner rows with matching key fields) from the entire dataset. By taking out only the relevant rows for comparison and excluding unpartnered rows from the detailed comparison process, the system delivers precise difference identification without presenting unnecessary information to users.
2Reliability
If all rows are compared sequentially, then complete comparison coverage is achieved, but the complexity of the comparison process increases
Solution Approach 1:
The comparison process is segmented into distinct operational phases: generating partner row identifiers, matching partner rows between tables, comparing only matched rows, and handling unpartnered rows separately. This segmentation maintains complete comparison coverage while reducing process complexity by organizing operations into manageable, logically-separated steps.
Solution Approach 2:
The patent performs preliminary actions by first identifying and organizing partner rows based on key fields before conducting the actual data comparison. This preliminary organization step simplifies the subsequent comparison process by pre-grouping relevant rows, thereby maintaining reliability without increasing overall process complexity.
3Measurement precision
If row order differences are treated as substantive differences, then all variations are captured, but meaningful differences become difficult to identify
Solution Approach 1:
The patent extracts and isolates the key field values that define partner row relationships, separating these structural identifiers from the actual data comparison. By taking out the key field matching logic as a distinct preliminary step, the system accurately detects substantive differences while filtering out irrelevant variations such as row order differences, thereby improving result interpretability.
Solution Approach 2:
The patent applies different comparison criteria to different parts of the data structure: key fields are used for identifying partner relationships, while comparison fields are used for detecting substantive differences. This local quality approach ensures that row order differences (a structural property) do not confuse the detection of meaningful data differences, enhancing both precision and ease of operation.
Data Source
AI summary
Rows of first and second tables that share common values for one or more designated key fields can be considered partner rows to facilitate computer-based comparison of the tables. Responsive to a user request to compare the first and second tables, which designates field(s) common to both data tables as key fields and field(s) common to both data tables as comparison fields, a matches table is generated which includes the key field(s), comparison field(s), and a source field whose value indicates the originating table of the data in the row. For each set of partner rows, the matches table is populated with data from the partner rows. The data in the matches table is handled, and a results table is populated with the results of the handling of the data in the matches table and with data from any unpartnered rows in the first and second tables.