Branch data synchronization detection method, device, computer equipment and storage medium

Abstract

This disclosure relates to the field of computer technology and discloses a method, apparatus, computer equipment, and storage medium for branch data synchronization detection. The method includes: acquiring a table of branch data before modification, a table of branch data after modification, and a table of branch data after merging; determining a common table for branch data synchronization based on the table of branch data before modification, the table of branch data after modification, and the table of branch data after merging; obtaining first branch data, second branch data, and third branch data within the common table of branch data synchronization based on a preset index; comparing the first branch data and the second branch data, and determining the synchronization detection result of the branch data based on the first branch data, the second branch data, and the third branch data if a first difference exists between the first branch data and the second branch data. This disclosure solves the problem of not being able to promptly detect errors in synchronized content when determining whether the content of multiple branch tables is synchronized.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, specifically to a method, apparatus, computer equipment, and storage medium for detecting branch data synchronization. Background Technology

[0002] In game project table configuration, tables are typically configured simultaneously across multiple branches. Staff usually configure one main branch and then manually commit their changes to the other branches. However, due to the large amount of configuration data, it's inevitable that some changes will be missed during synchronization. Sometimes, multiple designers modify the same table, leading to one designer's changes being accidentally overwritten by another, resulting in table content that doesn't match expectations.

[0003] Existing table inspection and comparison tools typically compare two tables to identify differences. However, this method fails to detect content accidentally overwritten by others and is prone to revealing other configurations on a branch, making it difficult to pinpoint the truly unsynchronized content.

[0004] Therefore, when determining whether the content is synchronized between multiple branch tables, the relevant technology has the problem of failing to detect missing content and errors in synchronization in a timely manner. Summary of the Invention

[0005] In view of this, the present disclosure provides a branch data synchronization detection method, apparatus, computer equipment and storage medium to solve the problem that related technologies cannot detect content omissions and synchronization errors in a timely manner when determining whether the content of multiple branch tables is synchronized.

[0006] Firstly, this disclosure provides a branch data synchronization detection method, which includes:

[0007] Get the version table before branch data modification, the version table after branch data modification, and the version table after branch data is merged;

[0008] Based on the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging, determine the common table for branch data synchronization.

[0009] Based on the preset index, the first branch data, the second branch data, and the third branch data in the branch data synchronization public table are obtained. The first branch data is included in the version table before the branch data is modified, the second branch data is included in the version table after the branch data is modified, and the third branch data is included in the version table after the branch data is merged.

[0010] Compare the first branch data and the second branch data. If there is a first difference between the first branch data and the second branch data, determine the synchronization detection result of the branch data based on the first branch data, the second branch data, and the third branch data.

[0011] In this embodiment, a branch data synchronization common table is obtained by acquiring the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging. Based on a preset index and the branch data synchronization common table, the first branch data from the version table before branch data modification, the second branch data from the version table after branch data modification, and the third branch data from the version table after branch data merging are determined. Then, the branch data synchronization detection result is determined based on the first branch data, the second branch data, and the third branch data. By comparing the first branch data, the second branch data, and the third branch data, the parts of the branch data that have not been synchronized to the merged branch after being modified can be found in a timely manner. It can also find the parts of your modifications that have been overwritten by others, avoiding omissions and errors when committing to multiple branches, avoiding online errors caused by configuration problems, and solving the problem that related technologies cannot detect content omissions and synchronization errors in a timely manner when determining whether the content is synchronized between multiple branch tables.

[0012] In one optional implementation, a common table for branch data synchronization is determined based on the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging, including:

[0013] Select common resources among the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging;

[0014] The tables obtained from public resources are synchronized with the public tables as branch data.

[0015] In this embodiment, a common table for branch data synchronization obtained from public resources is obtained using a table of versions before branch data modification, a table of versions after branch data modification, and a table of versions after branch data merging. Using this common table for synchronization detection subsequently narrows the comparison scope and saves network resources. In an optional implementation, based on a preset index, the first branch data, the second branch data, and the third branch data within the common table for branch data synchronization are obtained, including:

[0016] Get the preset row index and preset column index;

[0017] By using preset row indexes and preset column indexes to traverse the branch data and synchronize the common table, the first branch data, the second branch data, and the third branch data can be obtained.

[0018] In this embodiment of the disclosure, the branch data synchronization public table is traversed using preset row index and preset column index. Since the branch data synchronization public table is public, the synchronization status of the branch data can be determined based on the obtained first branch data, second branch data and third branch data.

[0019] In one optional implementation, when there is a first difference between the first branch data and the second branch data, determining the synchronization detection result of the branch data based on the first branch data, the second branch data, and the third branch data includes:

[0020] Compare the first discrepancy data with the third branch data to determine whether a second discrepancy data exists;

[0021] In the absence of second difference data, the detection result of the branch data is determined as the synchronization is complete;

[0022] In the presence of a second discrepancy, the detection result for the branch data is determined to be that synchronization has not been completed.

[0023] In this embodiment of the disclosure, when there is first difference data in the first branch data and the second branch data, the first difference data and the third branch data are compared to determine the final synchronization status of the branch data. If there is no second difference data, it is determined that the modified content has been merged. If there is second difference data, it is detected that the modification has not been merged, thereby avoiding configuration problems that are difficult to find through manual testing.

[0024] In one optional implementation, the first difference data includes a first difference row and a first difference column, and the second difference data includes a second difference row and a second difference column. After determining that the detection result of the branch data is that synchronization is incomplete, the method further includes:

[0025] Based on the first difference row and first difference column of the first difference data, and the second difference row and second difference column of the second difference data, determine the common rows and common columns that have common differences;

[0026] Determine the cell content based on common rows, common columns, preset row indexes, and preset column indexes.

[0027] In this embodiment of the disclosure, based on the determined common rows and common columns, the cell content can be quickly and accurately located, and then the current branch data synchronization status can be determined based on the cell content.

[0028] In one alternative implementation, after determining the cell content, the method further includes:

[0029] The second difference data and cell content are integrated to obtain the integrated difference structure table;

[0030] Upload the difference structure table to cloud storage.

[0031] In this embodiment of the disclosure, user reading convenience is improved by integrating and uploading to the cloud.

[0032] In one alternative implementation, after uploading the difference structure table to cloud storage, the method further includes:

[0033] Retrieve the link identifier generated from the difference structure table;

[0034] Visualization is achieved through link identifiers.

[0035] In this embodiment of the disclosure, a table displaying all missing results is presented in a visual manner, making it convenient for users to view and improving user convenience.

[0036] Secondly, this disclosure provides a branch data synchronization detection device, which includes:

[0037] The acquisition module is used to acquire the version table before the branch data is modified, the version table after the branch data is modified, and the version table after the branch data is merged.

[0038] The first determination module is used to determine the common table for branch data synchronization based on the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging.

[0039] The module is used to obtain the first branch data, the second branch data, and the third branch data in the branch data synchronization public table according to the preset index. The first branch data is included in the version table before the branch data is modified, the second branch data is included in the version table after the branch data is modified, and the third branch data is included in the version table after the branch data is merged.

[0040] The second determining module is used to compare the first branch data and the second branch data, and in the case where there is a first difference data between the first branch data and the second branch data, determine the synchronization detection result of the branch data based on the first branch data, the second branch data and the third branch data.

[0041] Thirdly, this disclosure provides a computer device, including: a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to perform the branch data synchronization detection method of the first aspect or any corresponding embodiment described above.

[0042] Fourthly, this disclosure provides a computer-readable storage medium storing computer instructions for causing a computer to execute the branch data synchronization detection method of the first aspect or any corresponding embodiment described above. Attached Figure Description

[0043] To more clearly illustrate the technical solutions in the specific embodiments of this disclosure or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0044] Figure 1 This is a flowchart illustrating the branch data synchronization detection method according to an embodiment of the present disclosure;

[0045] Figure 2 This is an example diagram illustrating the selection of preset index rows and preset index columns according to embodiments of this disclosure;

[0046] Figure 3 This is a schematic diagram of the overall process of the branch data synchronization detection method according to an embodiment of the present disclosure;

[0047] Figure 4 This is a structural block diagram of a branch data synchronization detection device according to an embodiment of the present disclosure;

[0048] Figure 5 This is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present disclosure. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0050] Current data modification synchronization check schemes typically compare two tables to identify differences. For example, a related technology proposes an intelligent comparison and automatic matching method for data columns, involving the technical field of data processing. This method includes the following steps: browsing the baseline and comparison table files; extracting column names from the tables and displaying them on the interface; selecting one of the mutually exclusive options, choosing the entire table, and graying out the start and end row input boxes; selecting the start and end rows to compare; selecting a column from the opened table as the basis for the comparison; opening the baseline table file: launching an Excel spreadsheet and viewing the table data; synchronizing the selected data from the baseline table file to the comparison table file; loading the table data according to the set information and displaying it on the preview interface. At this point, the baseline and comparison table files are simultaneously open on the left and right sides of the same page; comparing the results; and exporting the task result report. However, this method cannot detect content accidentally overwritten by others, and it is easy for other configuration content in a branch to be compared, making it difficult to find the truly unsynchronized content.

[0051] To address the aforementioned problems, according to an embodiment of this disclosure, a branch data synchronization detection method embodiment is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0052] This embodiment provides a branch data synchronization detection method. Figure 1 This is a flowchart of a branch data synchronization detection method according to an embodiment of the present disclosure, such as... Figure 1 As shown, this method can be applied to the server side, and the method may include the following steps:

[0053] Step S101: Obtain the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging.

[0054] Optionally, the SVN (subversion, version control system) repository contains information about various branches and versions. In this implementation, the TortoiseSVN tool can be used to pull different branches and versions from SVN and then place them in different folders on the local machine.

[0055] This embodiment of the disclosure can set up three folders: a "Pre-Modification Version" folder to store the branch data version table before modification; a "Post-Modification Version" folder to store the branch data version table after modification; and a "Post-Merge Version" folder to store the branch data version table after merging. When the server receives a confirmation branch data synchronization detection instruction, it retrieves the branch data version tables before modification, after modification, and after merging from the aforementioned three folders, respectively.

[0056] This embodiment of the disclosure determines the branch data synchronization status by comparing the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging. The version table before branch data modification can be represented by A0, which represents the original version table before any modifications were made to the branch data; the version table after branch data modification can be represented by A1, which represents the version table after the branch data was modified; the version table after branch data merging can be represented by B, which represents the final version table after merging the modified branch data into other branches.

[0057] Step S102: Determine the common table for branch data synchronization based on the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging.

[0058] Optionally, after reading the version table before the branch data was modified, the version table after the branch data was modified, and the version table after the branch data was merged, the common table for branch data synchronization can be obtained from these existing version tables. It is understood that the common table for branch data synchronization comes from the three version tables mentioned above.

[0059] Step S103: According to the preset index, obtain the first branch data, the second branch data, and the third branch data in the branch data synchronization public table. The first branch data is included in the version table before the branch data is modified, the second branch data is included in the version table after the branch data is modified, and the third branch data is included in the version table after the branch data is merged.

[0060] Optionally, a preset index for traversing the branch data synchronization public table is obtained, and the first branch data, second branch data, and third branch data within the branch data synchronization public table are obtained based on this preset index. It is important to understand that the first branch data is obtained from the version table before the branch data was modified, the second branch data is obtained from the version table after the branch data was modified, and the third branch data is obtained from the version table after the branch data was merged, based on the preset index.

[0061] Step S104: Compare the first branch data and the second branch data. If there is a first difference between the first branch data and the second branch data, determine the synchronization detection result of the branch data based on the first branch data, the second branch data, and the third branch data.

[0062] Optionally, this embodiment of the disclosure needs to compare whether there is any difference data (i.e., first difference data) between the traversed first branch data and second branch data. Since the first branch data comes from the version table before the branch data was modified, and the second branch data comes from the version table after the branch data was modified, if the first branch data and the second branch data are consistent and no difference data appears, it means that the branch data has not been modified. In this case, regardless of whether the second branch data and the third branch data are consistent, the current branch data is considered to be synchronized, and no further branch data synchronization detection is performed. Only when there is first difference data between the first branch data and the second branch data, then the synchronization detection result of the branch data is determined based on the first branch data, the second branch data, and the third branch data.

[0063] In this embodiment, a branch data synchronization common table is obtained by acquiring the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging. Based on a preset index and the branch data synchronization common table, the first branch data from the version table before branch data modification, the second branch data from the version table after branch data modification, and the third branch data from the version table after branch data merging are determined. Then, the branch data synchronization detection result is determined based on the first branch data, the second branch data, and the third branch data. By comparing the first branch data, the second branch data, and the third branch data, the parts of the branch data that have not been synchronized to the merged branch after being modified can be found in a timely manner. It can also find the parts of your modifications that have been overwritten by others, avoiding omissions and errors when committing to multiple branches, avoiding online errors caused by configuration problems, and solving the problem that related technologies cannot detect content omissions and synchronization errors in a timely manner when determining whether the content is synchronized between multiple branch tables.

[0064] In some optional implementations, a common table for branch data synchronization is determined based on the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging, including:

[0065] Select common resources among the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging;

[0066] The tables obtained from public resources are synchronized with the public tables as branch data.

[0067] Optionally, in this embodiment of the disclosure, the intersection of the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging, such as the table obtained from the public resources corresponding to A0∩A1∩B, is used as the branch data synchronization public table.

[0068] Furthermore, the table before the branch data was modified contains 1.csv, 2.csv, and 3.csv; the table after the branch data was modified contains 1.csv, 2.csv, and 4.csv; and the table after the branch data was merged contains 1.csv, 2.csv, and 5.csv. Therefore, the common table for branch data synchronization is 1.csv and 2.csv. It can be understood that there can be one or more common tables for branch data synchronization.

[0069] In this embodiment, a common table for branch data synchronization obtained from public resources is obtained by using the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging. Subsequently, using the common table for branch data synchronization as the synchronization detection object can narrow the comparison range and save network resources.

[0070] In some optional implementations, based on a preset index, the first branch data, the second branch data, and the third branch data within the branch data synchronization public table are obtained, including:

[0071] Get the preset row index and preset column index;

[0072] By using preset row indexes and preset column indexes to traverse the branch data and synchronize the common table, the first branch data, the second branch data, and the third branch data can be obtained.

[0073] Optionally, the data synchronization public table for each branch is traversed, processed, and the first column is used as a preset row index, and the first row is used as a preset column index, and stored in a DataFrame (a tabular data structure). For example... Figure 2 ,exist Figure 2 In the table, the first three rows are the header information. The first row is the Chinese column index, the second row is the English name index, and the third row identifies the column type. Either the first or second row can be used as the column index; to avoid encoding issues, the English names in the second row are used as the default column index. The first column starting from the fourth row is set as the default row index. Figure 2 The first column selected in the text consists of ID serial numbers.

[0074] Then, using the preset row index and preset column index, the branch data synchronization public table is traversed to obtain the first branch data contained in the version table before the branch data was modified, the second branch data contained in the version table after the branch data was modified, and the third branch data contained in the version table after the branch data was merged.

[0075] Additionally, the first branch is the version before the modification, the second branch is the version after the modification, and the third branch is the branch after the modified data is merged. The first and second branches can also be the pre-modification and post-modification branches of any modified branch.

[0076] In this embodiment of the disclosure, the branch data synchronization public table is traversed using preset row index and preset column index. Since the branch data synchronization public table is public, the synchronization status of the branch data can be determined based on the obtained first branch data, second branch data and third branch data.

[0077] In some optional implementations, when there is a first difference between the first branch data and the second branch data, the synchronization detection result of the branch data is determined based on the first branch data, the second branch data, and the third branch data, including:

[0078] Compare the first discrepancy data with the third branch data to determine whether a second discrepancy data exists;

[0079] In the absence of second difference data, the detection result of the branch data is determined as the synchronization is complete;

[0080] In the presence of a second discrepancy, the detection result for the branch data is determined to be that synchronization has not been completed.

[0081] Optionally, the data in the first branch and the data in the second branch are compared to obtain the first difference data, such as newly added rows, deleted rows, newly added columns, and deleted columns. Then, based on the first difference data, it is compared with the data in the third branch to determine whether there is second difference data (i.e., missing newly added rows, missing deleted rows, missing newly added columns, missing deleted columns, and missing modified cells, where missing modified cells refer to the parts of the content in the second branch that differ from those in the third branch). If there is no second difference data, it means that the second branch has synchronized the modified branch data to the third branch, achieving branch data modification synchronization; if there is second difference data, it means that the second branch has not synchronized the modified branch data to the third branch, failing to achieve branch data modification synchronization.

[0082] It should be noted that "missing new rows" refers to the row indexes in a table that were added in the second branch but not in the third branch;

[0083] Missed submission of newly added columns refers to a column index that was added to a table in the second branch but is not present in the third branch;

[0084] Missed commit for deleted rows refers to rows in a table that were deleted in the second branch but still exist in the third branch.

[0085] Missed submission for deleted columns refers to a column index in a table that was deleted in the second branch but still exists in the third branch.

[0086] Here's a specific example: as shown in Tables 1 to 3, Table 1 represents the data for the first branch, Table 2 represents the data for the second branch, and Table 3 represents the data for the third branch.

[0087] Table 1

[0088] <![CDATA[col0]]> <![CDATA[col1]]> <![CDATA[col3]]> <![CDATA[row0]]> 1 2 3 <![CDATA[row1]]> 1 2 3 <![CDATA[row3]]> 1 2 3

[0089] Table 2

[0090] <![CDATA[col0]]> <![CDATA[col2]]> <![CDATA[col3]]> <![CDATA[row0]]> 1 2 2 <![CDATA[row2]]> 1 2 3 <![CDATA[row3]]> 3 2 3

[0091] Table 3

[0092] <![CDATA[col0]]> <![CDATA[col3]]> <![CDATA[col4]]> <![CDATA[row0]]> 1 1 2 <![CDATA[row1]]> 1 1 2 <![CDATA[row2]]> 1 1 2

[0093] Missed commit for new row: In the example, a new row {row2} was added in the second branch and also exists in the third branch. In this case, there is no missing commit for the new row in the third branch.

[0094] Missing a newly added column: In the example, a column {col2} was added in the second branch but not in the third branch. In this case, the newly added column {col2} was missed in the third branch.

[0095] Missed commit for deleted row: In the example, the row {row1} was deleted in the second branch but still exists in the third branch. In this case, the third branch missed committing the deletion of row {row1}.

[0096] Missing commit for deleted column: In the example, the column {col1} was deleted in the second branch but not in the third branch. In this case, there is no missing commit for deleted row in the third branch.

[0097] In this embodiment of the disclosure, when there is first difference data in the first branch data and the second branch data, the first difference data and the third branch data are compared to determine the final synchronization status of the branch data. If there is no second difference data, it is determined that the modified content has been merged. If there is second difference data, it is detected that the modification has not been merged, thereby avoiding configuration problems that are difficult to find through manual testing.

[0098] In some optional implementations, the first difference data includes a first difference row and a first difference column, and the second difference data includes a second difference row and a second difference column. After determining that the detection result of the branch data is that synchronization is incomplete, the method further includes:

[0099] Based on the first difference row and first difference column of the first difference data, and the second difference row and second difference column of the second difference data, determine the common rows and common columns that have common differences;

[0100] Determine the cell content based on common rows, common columns, preset row indexes, and preset column indexes.

[0101] Optionally, since the traversal of the branch data synchronization common table is implemented using preset row and column indexes, the first difference data should include both row and column data. In this case, the row data is called the first difference row, and the column data is called the first difference column. Similarly, the second difference data includes the second difference row and the second difference column. Then, to determine the missing submission content (i.e., cell content), it is necessary to obtain the common rows and columns with shared differences from the first difference row and column, the second difference row, and the second difference column.

[0102] Specifically, the first and second difference rows are compared to find the common row, the first and second difference columns are compared to find the common column, and then the cell contents corresponding to the common row and common column of each branch data are traversed based on the preset row index and preset column index. The specific cell is compared to determine the cell content.

[0103] Let the cell content on the first branch be a0 (corresponding to the initial value before modification), the cell content on the second branch be a1 (corresponding to the modified value), and the cell content on the third branch be b (corresponding to the merged value).

[0104] Four scenarios can be summarized from the above:

[0105] 1. a0 = a1 and a1 = b

[0106] 2. a0 = a1 and a1 ≠ b

[0107] 3. a0 ≠ a1 and a1 = b

[0108] 4. a0 ≠ a1 and a1 ≠ b

[0109] For cases 1 and 2, since the cell content on the first and second branches has not been changed, no cell content is missed regardless of the value of the cell on the third branch.

[0110] In case 3, the cell content of the first branch is changed from a0 to the cell content of the second branch, a1, and is consistent with the cell content of the third branch, b. This is considered as the modification being synchronized to the third branch.

[0111] In case 4, the cell content of the first branch was changed from a0 to the cell content of the second branch, a1, but it is inconsistent with the cell content of the third branch, b, which is considered as a missed submission of cell content.

[0112] In the above embodiment, the missing new rows and columns can be determined according to Tables 1 to 3. Then, the common rows and common columns of the branch data synchronization common table are traversed according to the preset row index and preset column index to obtain the content of the first branch cell, the content of the second branch cell, and the content of the third branch cell, as shown in Tables 4 to 6 respectively.

[0113] Table 4

[0114] <![CDATA[col1]]> <![CDATA[col3]]> <![CDATA[row1]]> 1 3 <![CDATA[row3]]> 1 3

[0115] Table 5

[0116] <![CDATA[col1]]> <![CDATA[col3]]> <![CDATA[row1]]> 1 2 <![CDATA[row3]]> 3 3

[0117] Table 6

[0118] <![CDATA[col1]]> <![CDATA[col3]]> <![CDATA[row1]]> 1 2 <![CDATA[row3]]> 1 2

[0119] The comparison and inspection of cell contents for common rows and common columns is shown in Table 7:

[0120] Table 7

[0121]

[0122] As can be seen from Table 7, the value corresponding to row3col1 was 1 in the first branch and was later changed to 3, but it was still 1 in the third branch. Therefore, there is a case where the cell content was not submitted.

[0123] The final cell contents are shown in Table 8.

[0124] Table 8

[0125]

[0126] In this embodiment of the disclosure, based on the determined common rows and common columns, the cell content can be quickly and accurately located, and then the current branch data synchronization status can be determined based on the cell content.

[0127] In some alternative implementations, after determining the cell content, the method further includes:

[0128] The second difference data and cell content are integrated to obtain the integrated difference structure table;

[0129] Upload the difference structure table to cloud storage.

[0130] Optionally, after obtaining the second set of discrepancy data, the missing new rows and columns can be identified. The missing submission content can be obtained from the cell contents. These missing new rows, columns, and content can then be combined into a single table to create a discrepancy structure table for easier reading. Alternatively, this discrepancy structure table can be uploaded to the cloud for storage and easy access later.

[0131] In this embodiment of the disclosure, user reading convenience is improved by integrating and uploading to the cloud.

[0132] In some alternative implementations, after uploading the difference structure table to cloud storage, the method further includes:

[0133] Retrieve the link identifier generated from the difference structure table;

[0134] Visualization is achieved through link identifiers.

[0135] Optionally, after uploading the difference structure table to cloud storage, a link identifier, such as a hyperlink, can be generated. Users can then click on the link identifier to obtain a visual table displaying all the missing results.

[0136] In this embodiment of the disclosure, a table displaying all missing results is presented in a visual manner, making it convenient for users to view and improving user convenience.

[0137] In some alternative implementations, such as Figure 3 As shown, Figure 3 This is a schematic diagram of the overall process of the branch data synchronization detection method according to an embodiment of the present disclosure, including the following steps:

[0138] Traverse the pre-modification branch, post-modification branch, and merged branch table folder to find the common table among the three;

[0139] For each common table, read the branch table before modification, the branch table after modification, and the merged branch table;

[0140] Based on the row and column indices, compare the branch table before and after the modification to find the first difference data.

[0141] After finding the first difference data, compare the modified branch table with the merged branch table to find the second difference data;

[0142] Based on the second difference data, find the missing synchronously added rows and columns;

[0143] Based on the first and second difference data, find the common rows and columns of the differences to determine the content of the missing synchronized cells;

[0144] All missing results are uploaded to the cloud and hyperlinked to the final results index table.

[0145] This embodiment also provides a branch data synchronization detection device, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0146] This embodiment provides a branch data synchronization detection device, such as... Figure 4 As shown, it includes:

[0147] Module 401 is used to obtain the version table before the branch data is modified, the version table after the branch data is modified, and the version table after the branch data is merged.

[0148] The first determining module 402 is used to determine the branch data synchronization common table based on the version table before the branch data is modified, the version table after the branch data is modified, and the version table after the branch data is merged.

[0149] The module 403 is used to obtain the first branch data, the second branch data, and the third branch data in the branch data synchronization public table according to the preset index. The first branch data is included in the version table before the branch data is modified, the second branch data is included in the version table after the branch data is modified, and the third branch data is included in the version table after the branch data is merged.

[0150] The second determining module 404 is used to compare the first branch data and the second branch data, and in the case where there is a first difference data between the first branch data and the second branch data, determine the synchronization detection result of the branch data based on the first branch data, the second branch data and the third branch data.

[0151] In this embodiment, a branch data synchronization common table is obtained by acquiring the version table before branch data modification, the version table after branch data modification, and the version table after branch data merging. Based on a preset index and the branch data synchronization common table, the first branch data from the version table before branch data modification, the second branch data from the version table after branch data modification, and the third branch data from the version table after branch data merging are determined. Then, the branch data synchronization detection result is determined based on the first branch data, the second branch data, and the third branch data. By comparing the first branch data, the second branch data, and the third branch data, the parts of the branch data that have not been synchronized to the merged branch after being modified can be found in a timely manner. It can also find the parts of your modifications that have been overwritten by others, avoiding omissions and errors when committing to multiple branches, avoiding online errors caused by configuration problems, and solving the problem that related technologies cannot detect content omissions and synchronization errors in a timely manner when determining whether the content is synchronized between multiple branch tables.

[0152] In some alternative implementations, the first determining module 402 includes:

[0153] The selection unit is used to select common resources among the version table before the branch data was modified, the version table after the branch data was modified, and the version table after the branch data was merged.

[0154] The configuration unit is used to synchronize tables obtained from public resources as branch data to public tables.

[0155] In some alternative implementations, module 403 includes:

[0156] The first acquisition unit is used to acquire the preset row index and the preset column index;

[0157] The obtained unit is used to traverse the branch data and synchronize the public table using preset row indexes and preset column indexes to obtain the first branch data, the second branch data, and the third branch data.

[0158] In some alternative implementations, the second determining module 404 includes:

[0159] The comparison unit is used to compare the first difference data and the third branch data to determine whether there is a second difference data.

[0160] The first determining unit is used to determine the detection result of the branch data as complete synchronization in the absence of second difference data;

[0161] The second determining unit is used to determine that the detection result of the branch data is not synchronized when there is second difference data.

[0162] In some optional embodiments, the first difference data includes a first difference row and a first difference column, and the second difference data includes a second difference row and a second difference column. The apparatus further includes:

[0163] The third determining unit is used to determine, after determining that the detection result of the branch data is not synchronized, the common rows and common columns that have common differences based on the first difference row and the first difference column of the first difference data, and the second difference row and the second difference column of the second difference data.

[0164] The fourth determination unit is used to determine the cell content based on the common row, common column, preset row index, and preset column index.

[0165] In some alternative embodiments, the device further includes:

[0166] The integration unit is used to integrate the second difference data and the cell content after the cell content is determined, so as to obtain the integrated difference structure table.

[0167] The upload unit is used to upload the difference structure table to cloud storage.

[0168] In some alternative embodiments, the device further includes:

[0169] The second acquisition unit is used to acquire the link identifier generated by the difference structure table after the difference structure table is uploaded to the cloud storage.

[0170] Visual units are used for visual presentation via links.

[0171] In this embodiment, the branch data synchronization detection device is presented in the form of a functional unit. Here, a unit refers to an ASIC circuit, a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0172] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0173] This disclosure also provides a computer device having the above-described features. Figure 4 The branch data synchronization detection device shown.

[0174] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of this disclosure, such as... Figure 5As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 5 Take a processor 10 as an example.

[0175] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0176] The memory 20 stores instructions executable by at least one processor 10 to cause at least one processor 10 to perform the method shown in the above embodiments.

[0177] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the computer device as shown by a landing page for an app. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, which can be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0178] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0179] The computer device also includes a communication interface 30 for communicating with other devices or communication networks.

[0180] This disclosure also provides a computer-readable storage medium in which the methods described in this disclosure can be implemented in hardware or firmware, or implemented as recordable on a storage medium, or implemented as computer code originally stored on a remote storage medium or a non-transitory machine-readable storage medium and subsequently stored on a local storage medium after being downloaded over a network. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium may be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium may also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code that, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.

[0181] Although embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A method for detecting branch data synchronization, characterized in that, The method includes: Get the version table before branch data modification, the version table after branch data modification, and the version table after branch data is merged; Based on the version table before the branch data was modified, the version table after the branch data was modified, and the version table after the branch data was merged, determine the common table for branch data synchronization. According to the preset index, the first branch data, the second branch data, and the third branch data in the branch data synchronization public table are obtained. The first branch data is included in the version table before the branch data is modified, the second branch data is included in the version table after the branch data is modified, and the third branch data is included in the version table after the branch data is merged. Compare the first branch data and the second branch data. If there is a first difference data between the first branch data and the second branch data, compare the first difference data and the third branch data to determine whether there is a second difference data. In the absence of the second difference data, the detection result of the branch data is determined to be a complete synchronization; If the second difference data exists, the detection result of the branch data is determined to be that synchronization has not been completed.

2. The method according to claim 1, characterized in that, The step of determining a common table for branch data synchronization based on the version table before the branch data modification, the version table after the branch data modification, and the version table after the branch data merging includes: Select the common resources among the version table before the branch data was modified, the version table after the branch data was modified, and the version table after the branch data was merged; The table obtained from the public resource will be used as the branch data synchronization public table.

3. The method according to claim 1 or 2, characterized in that, The step of obtaining the first branch data, second branch data, and third branch data in the synchronized public table of the branch data according to the preset index includes: Get the preset row index and preset column index; The branch data synchronization public table is traversed using the preset row index and the preset column index to obtain the first branch data, the second branch data, and the third branch data.

4. The method according to claim 3, characterized in that, The first difference data includes a first difference row and a first difference column, the second difference data includes a second difference row and a second difference column, and after determining that the detection result of the branch data is that synchronization is incomplete, the method further includes: Based on the first difference row and the first difference column of the first difference data, and the second difference row and the second difference column of the second difference data, determine the common rows and columns that have common differences; The cell content is determined based on the common row, the common column, the preset row index, and the preset column index.

5. The method according to claim 4, characterized in that, After determining the cell content, the method further includes: The second difference data and the cell content are integrated to obtain the integrated difference structure table; The difference structure table is uploaded to cloud storage.

6. The method according to claim 5, characterized in that, After uploading the difference structure table to cloud storage, the method further includes: Obtain the link identifier generated from the difference structure table; The links are used for visual display.

7. A branch data synchronization detection device, characterized in that, The device includes: The acquisition module is used to acquire the version table before the branch data is modified, the version table after the branch data is modified, and the version table after the branch data is merged. The first determining module is used to determine a branch data synchronization common table based on the version table before the branch data modification, the version table after the branch data modification, and the version table after the branch data is merged. The module is used to obtain the first branch data, the second branch data, and the third branch data in the branch data synchronization public table according to a preset index. The first branch data is included in the version table before the branch data is modified, the second branch data is included in the version table after the branch data is modified, and the third branch data is included in the version table after the branch data is merged. The second determining module is used to compare the first branch data and the second branch data, and in the case where there is a first difference data between the first branch data and the second branch data, determine the synchronization detection result of the branch data based on the first branch data, the second branch data and the third branch data. The second determining module includes: The comparison unit is used to compare the first difference data and the third branch data to determine whether there is a second difference data. The first determining unit is used to determine the detection result of the branch data as complete synchronization in the absence of second difference data; The second determining unit is used to determine that the detection result of the branch data is not synchronized when there is second difference data.

8. A computer device, characterized in that, include: A memory and a processor are communicatively connected, the memory stores computer instructions, and the processor executes the branch data synchronization detection method according to any one of claims 1 to 6 by executing the computer instructions.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to execute the branch data synchronization detection method according to any one of claims 1 to 6.

Images