CN102999532B - Method and device for configuring data by users - Google Patents

Abstract

The invention discloses a method and a device for user configuration data. The method includes: according to the user's operation on the configuration data, storing the operating user name and operation type under the corresponding configuration data entry in the editing table, and processing the conflicting data in the editing table when there is a conflict in the data in the editing table , when there is no conflict in the data in the editing table, save the table name of the editing table and the corresponding operation user name in the preset increment table; when the user submits the configuration data, according to the user's operation user name and increment The scale obtains the corresponding editing table, and submits the configuration data modified by the user recorded in the editing table to the online table, wherein the online table is used to save the effective configuration data.

Description

Method and device for user configuration data

technical field

The invention relates to the field of mobile communication, in particular to a method and device for user configuration data.

Background technique

At present, in the data configuration management system, each set of logically complete data is defined as a data set. The traditional data configuration process adopts the method of locking the entire data set to ensure the mutual exclusion of data operations among multiple users. , so it does not support multiple users operating the same data set at the same time, and cannot distinguish between multiple users modifying the same table. In the existing technology, the modification of each user is not cached, resulting in the data modified by each user being intertwined. If the data set is not locked, when a user's data configuration is submitted, all user modifications will be submitted. take effect.

With the continuous increase of data to be configured in the data configuration system, in practical applications, the data of a data set is usually configured through the cooperation of multiple people. The single-user configuration method will affect the efficiency of data configuration during the initial configuration, and the configurations between users will affect each other during subsequent operation and maintenance, which may cause the data that the current user does not want to submit to take effect to be submitted by another user. At the same time, the existing data system only checks the data for conflicts when the data is submitted, and the data modified by multiple users in turn will make it impossible to determine exactly which party's data in the conflict should prevail.

At present, the solution for multiple users to configure data at the same time is mainly implemented by data partitioning. Users edit different database tables and check for data conflicts with other users' modifications when the data submission takes effect. However, through the above technical solution, when multiple users configure data at the same time, multiple users cannot configure the same data set at the same time. In addition, real-time conflict checking cannot be performed during data editing, and independent Data commit and independent data rollback.

Contents of the invention

The present invention provides a method and device for user configuration data to solve the problem that in the prior art, when users configure data, multiple users cannot configure the same data set at the same time, and cannot perform real-time conflict checking when editing data, and cannot The problem of independent data submission in units of designated users.

The present invention provides a method for user configuration data, including:

According to the user's operation on the configuration data, save the operating user name and operation type under the corresponding configuration data entry in the editing table. If there is a conflict in the data in the editing table, process the conflicting data in the editing table. If there is no conflict in the data in , save the table name of the editing table and the corresponding operating user name in the pre-set incremental table;

When a user submits configuration data, obtain the corresponding editing table according to the user's operating user name and the increment table, and submit the user's modified configuration data recorded in the editing table to the online table, wherein the online table is used for Save the effective configuration data.

The present invention also provides a device for user configuration data, including:

The first saving module is used to save the operating user name and operation type under the corresponding configuration data entry in the edit table according to the user's operation on the configuration data;

The data conflict module is used to process the conflicting data in the editing table when the data in the editing table is in conflict;

The second saving module is used to save the table name of the editing table and the corresponding operating user name in the preset incremental table under the condition that the data in the editing table has no conflict;

The data submission module is used to obtain the corresponding editing table according to the user's operating user name and the increment table when the user submits the configuration data, and submit the modified configuration data of the user recorded in the editing table to the online table, Among them, the online table is used to save effective configuration data.

The beneficial effects of the present invention are as follows:

By designing the database configuration table into two sets of online table and editing table, the online table is completely consistent with the existing data configuration table, and the table structure of the editing table is completely modified based on the table structure of the existing data configuration table According to the information recorded in the online table, edit table and incremental table, the user-by-user validation and user-by-user rollback process of multi-user configuration data is controlled, which solves the problem that multiple users cannot simultaneously configure the same For data collection, real-time conflict checking cannot be performed during data editing, and independent data submission cannot be performed in units of specified users. Real-time data conflict checking can be performed when multiple users configure data. At the same time, due to the recorded The operation information of each user can support the independent validation of data by user and the independent rollback of data by user, and can play the function of real-time automatic data backup.

Description of drawings

Fig. 1 is the flowchart of the method for the user configuration data of the embodiment of the present invention;

Fig. 2 is a schematic diagram of the relationship between the online table editing table increment table of the embodiment of the present invention;

Fig. 3 is a detailed processing flowchart of a method for configuring data by a user according to an embodiment of the present invention;

Fig. 4 is the flowchart of the data conflict checking of the embodiment of the present invention;

Fig. 5 is a schematic structural diagram of an apparatus for user configuration data according to an embodiment of the present invention.

detailed description

In order to solve the problems in the prior art that multiple users cannot configure the same data set at the same time when users configure data, real-time conflict checking cannot be performed during data editing, and independent data submission cannot be performed in units of designated users, The present invention provides a method and device for user configuration data. According to the table structure of the data configuration table, two sets of tables are generated in the database, one set is an online table for storing real and effective online data (hereinafter represented by O table); One set is an edit table (represented by E table hereinafter) for storing user offline editing process data. Add operation user name (CURRENT_USER) attribute column in each E table to indicate the user currently modifying the record; also increase operation type (OP) attribute column in each E table to indicate that the user has changed the record The operation done, in addition, the technical scheme of the embodiment of the present invention also maintains an incremental table (represented by D table below) to store user operation information, wherein, user operation information includes the table name of operation user (CURRENT_USER) and E table ( TABLENAME). Use the information recorded in O table, E table, and D table to control the user-by-user validation and user-by-user rollback process of multi-user configuration data. The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, not to limit the present invention.

method embodiment

According to the embodiment of the present invention, a kind of method of user's configuration data is provided, below at first the design of database table structure in the embodiment of the present invention is described in detail: for all data configuration tables are designed as two sets of tables in the database: one One set is an online table (O table) that stores real and effective online data. The O table is not provided for users to operate; the other set is an edit table (E table) that stores the user's offline editing process data. Users can only directly operate the E table. data.

The table structure difference between the O table and the E table is that each E table will add two attribute columns to store user operation process information: one column is the operation user name (CURRENT_USER) attribute column, which is used to store the user name for operating the record; The other column is the operation type (OP) attribute column, which is used to store the type of operation the user has performed on the record. For the OP attribute column, there are only three operation types: add (represented by A), modify (represented by M), and delete (represented by D).

In addition to the data configuration table, it is also necessary to maintain an incremental table (D table) to store the operation information that has been edited in the E table but not submitted to take effect, including the operating user name (CURRENT_USER) and the table name of the E table (TABLENAME).

Fig. 1 is the flow chart of the method for the user configuration data of the embodiment of the present invention, as shown in Fig. 1, the method for the user configuration data according to the embodiment of the present invention includes the following processing:

Step 101, according to the user's operation on the configuration data, save the operating user name and operation type under the corresponding configuration data entry in the E table, and in the case of conflicting data in the E table, process the conflicting data in the E table, In the case that the data in the E table has no conflict, the table name of the E table and the corresponding operation user name are stored in the preset D table; preferably, the operation type includes: increase (A), modification (M), and delete (D).

In step 101, processing the conflicting data in the E table specifically includes the following processing:

In the case that the same user performs multiple operations on a configuration data entry, resulting in data conflicts, if the add operation is performed on a configuration data entry first, and then the configuration data entry is modified, the modified attributes will be synchronized to Under the corresponding configuration data entry in the E table, and set its operation type to add; if you perform an add operation on a configuration data entry first, and then delete the configuration data entry, the corresponding configuration data entry in the E table will be directly deleted. Configuration data entry; if modifying a certain configuration data entry one after another, set the operation type under the corresponding configuration data entry in Table E to modify; if modifying a certain configuration data entry first, then To delete a configuration data entry, set the operation type under the corresponding configuration data entry in Table E to delete; if a configuration data entry is deleted first, and then the configuration data entry is added, then compare The deleted configuration data entry is different from the newly added configuration data entry and to modify the configuration data entry, set the operation type under the corresponding configuration data entry in Table E to modify.

In the case that different users perform multiple operations on a configuration data item successively, resulting in a data conflict, the next operating user is prompted that the configuration data item has been edited by other operating users and has not been submitted to take effect;

In the case that different users operate on multiple configuration data entries, resulting in data conflicts, if the configuration data entry referenced by the configuration data entry modified by the user has been deleted by other users, the user will be prompted to fail the operation; The configuration data entry referenced by the configuration data entry is newly added by other users and has not been submitted to take effect, and the user will be prompted that the operation failed; if the user deletes the configuration data entry referenced by other configuration data entries, and the If the operating user name is the user and the operation type is delete, then set the operation type under the configuration data entry in Table E to delete; if the user deletes the configuration data entry referenced by other configuration data entries, and the If the user name of the operation is empty or other users, the user will be prompted that the operation failed.

That is to say, data configuration is divided into three scenarios, no operation conflict, single user operation conflict and multi-user operation conflict.

1. Handling of no-operation conflicts

For user USER A, if a record RECORD 1 in table E is added, the value of the CURRENT_USER column of RECORD 1 is set to USER A, and the value of the OP column is set to A; if a record RECORD 2 of E table is modified, RECORD The value of the CURRENT_USER column of 2 is set to USER A, and the value of the OP column is set to M; if a record RECORD 3 of the E table is deleted, the value of the CURRENT_USER column of RECORD 3 is set to USER A, and the value of the OP column is set to D , while RECORD 3 does not delete.

2. Handling of single-user operation conflicts

For a single user, an operation conflict refers to multiple operations on the same data record in the same E table, including the following scenarios:

First A and then M, modify the attributes of M to this record synchronously, and the OP operator is still A;

First A and then D, directly delete the record from E table;

First M and then M, the OP operator is still M;

M first and then D, the OP operator is D;

First D and then A, compare the difference between the deleted record and the newly added record, make the attribute of the newly created record effective as M, and modify the OP to M.

3. Handling of multi-user operation conflicts

For multiple users, operation conflicts include operation conflicts of a single record and operation conflicts of multiple records. Among them, the operation conflict of a single record means that USER A and USER B successively edit the same record of the same E table. For the editing application of the latter data record, an error should be prompted. That is, if it is found that the CURRENT_USER in the record in the E table is not empty, it will prompt the operating user who wants to apply to edit this record that other users have edited the data record and have not yet submitted it to take effect, and can only wait for the user to submit After it takes effect, the data can be edited, and other data can continue to be edited. The operation conflict of multiple records refers to the change of the reference relationship between records when different users add or delete records. Including the following scenarios:

USERA adds or modifies a record RECORD 1, which refers to RECORD 2, but RECORD 2 has been deleted by USER B. Therefore, in addition to checking whether RECORD 2 exists, a condition needs to be added during the data constraint check, which is to find RECORD 2 Whether the CURRENT_USER is empty, if it is not empty and the OP column is D, then the user will be prompted that the referenced record has been deleted by USER B, and the modification of RECORD 1 failed.

USERA adds or modifies a record RECORD 1, which references RECORD 2, but RECORD 2 is added by USER B and has not been submitted to take effect. Therefore, in addition to finding whether RECORD 2 exists during data constraint checking, it is necessary to add a The condition is to check whether the CURRENT_USER of RECORD2 is empty. If it is not empty and the OP column is A, then the user is prompted that the referenced record was added by USER B and has not been submitted to take effect, and the modification of RECORD 1 fails.

USER A deletes a record RECORD 1, but RECORD 1 is referenced by RECORD 2. If the CURRENT_USER of RECORD 2 is USER A and OP is D, the deletion is allowed; if CURRENT_USER is empty or USERB is not allowed to delete, RECORD 1 is deleted fail.

Step 102, when the user submits the configuration data, obtain the corresponding E table according to the user's operating user name and the D table, and submit the modified configuration data of the user recorded in the E table to the O table, wherein the O table Used to save effective configuration data.

Specifically, step 102 includes the following processing: 1. When the user submits the configuration data, obtain the user's operating user name who initiates the data submission request; 2. Search the E table corresponding to the operating user name in the D table according to the operating user name 3. Obtain the corresponding E table according to the table name of the E table, obtain the configuration data entry of the operating user named the user in the E table, and obtain the configuration of the operating user named other users according to the records in the O table Data entry; 4. Merge the obtained configuration data entries according to the operation indicated by the operation type in the E table, and submit the merged configuration data to the O table.

That is to say, when submitting data, first obtain the operating user USER A who initiates the data submission request, and look up the list of E tables involved in D table according to the user name. Then look for the database record whose CURRENT_USER is USERA in each E table of these changes. For the records whose CURRENT_USER is not USERA, take those records in the corresponding O table, and merge them according to the operation indicated by the OP. The processing logic of merging is that for adding operations, it is directly adding; for modifying operations, it is directly modifying; for deleting operations, the corresponding records in the O table are deleted. The merged data will be submitted to Form O to take effect.

In step 102, after submitting the modified configuration data of the user recorded in the E table to the O table, the following processing needs to be performed: clear the record of the user whose name is the operating user in the D table, and delete the corresponding operation in the E table. The user name is the record of the user and the operation type is delete, and the operation user name and operation type under the configuration data entry of the operation user name in the E table are cleared.

That is to say, if the operation data of USER A is successfully submitted, clear the records in table D where CURRENT_USER is USER A, delete the corresponding records in table E where CURRENT_USER is USER A and the OP column is the deletion mark, and then clear the records in the corresponding table E CURRENT_USER is the attribute column of USER A. If the operation data submission of USER A fails, the failure reason will be prompted to the user.

Preferably, before step 102, the following operations can also be performed. When the user rolls back the configuration data, the corresponding E table is obtained according to the user's operating user name and the D table, and the corresponding E table is obtained according to the records in the O table. The configuration data entry is rolled back, and the O table is used to save the effective configuration data;

It specifically includes the following processing: 1. When the user rolls back the configuration data, obtain the operation user name of the user who initiates the data rollback request; 2. According to the operation user name in the D table, search for the E table corresponding to the operation user name Table name; 3. Obtain the corresponding E table according to the table name of the E table, obtain the configuration data entry whose operating user name is the user in the E table, and obtain the operation indicated by the operation type under the obtained configuration data entry and the O table In the record, roll back the corresponding configuration data entry in the E table.

That is to say, before the user submits the data, the user's operation can be rolled back to the state before editing. Firstly, according to the selected operating user name for data rollback, go to the D table to obtain the corresponding E table list, and find all the modification records of the user in these E tables. According to the value of the OP column of these records, process respectively: for A operation, delete the record; for M operation, copy the corresponding record of O table to E table; for D operation, clear the attribute values of CURRENT USER and OP column.

Fig. 2 is the schematic diagram of the relation of the online table editing table incremental table of the embodiment of the present invention, as shown in Fig. 2, comprise record 1 and record 2 in the O table, the value of the attribute 1 of record 1 is A2, the attribute 1 of record 2 The value is B1, USER A operates on E table 1, among which, record 1 and record 2 are respectively modified and deleted by USER A, record 3 is added by USER B, and table D records the operation of USER A The user name and its modified table name of E table 1, and the operating user name of USER B and its modified table name of E table 1. USER A submits data. First, obtain the E table 1 operated by USERA according to the records in D table, and merge the operations of record 1 and record 2 according to the records of USER A in E table 1, and submit them to O table to take effect, and finally , O table 1 includes the modified record 1. After the submission takes effect, clear the CURRENT_USER column and OP column of record 1 in E table 1, delete record 2, and delete the USERA record in D table.

The technical solutions of the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings.

Fig. 3 is a detailed processing flowchart of the method for user configuration data in an embodiment of the present invention, as shown in Fig. 3 , including the following processing:

Step 301, user operation E table record, save the operating user and operation type;

Step 302, data conflict check, if the check is passed, go to step 303; if the check is not passed, go to step 301;

Step 303, saving the changed E-list and operating user information in the D-list;

Step 304, the user selects data submission to enter step 306, and the user selects data rollback to enter step 305;

Step 305, roll back the corresponding record of E table according to O table, enter step 301;

Step 306, according to the changed E table records submitted to O table to take effect;

Step 307, if the data submission is successful, go to step 308, if the data submission fails, go to step 310;

Step 308, clear the operation user and operation type for the data records added and modified in the E table, delete the deleted data records, and enter step 309;

Step 309, clean up the operation information of the current operating user in table D, and end this configuration process;

Step 310, prompting the user of the reason for the failure of data submission, and ending the configuration process.

Fig. 4 is the flow chart of the data conflict check of the embodiment of the present invention, as shown in Fig. 4, comprises following processing:

Step 401, USER A edits data;

Step 402, determine the value of the CURRENT_USER column of the target record column, if the CURRENT_USER column is empty, then perform step 405, if the CURRENT_USER column is USERA, then perform step 403, if the CURRENT_USER column is USERB, then perform step 404;

Step 403, merge according to the algorithm according to the sequence operator, and execute step 405;

Step 404, check the reference relationship of the data record, if the check is passed, then execute step 405, otherwise, execute step 406;

Step 405, submit the modification to Form E;

In step 406, the user is prompted about the reason for the operation failure.

In the embodiment of the present invention, the database configuration table is designed as two sets of tables, the online table and the editing table, wherein the online table is completely consistent with the existing data configuration table, and the table structure of the editing table is completely based on the table structure of the existing data configuration table Based on the transformation, according to the information recorded in the online table, edit table and incremental table to control the user-by-user and user-by-user rollback process of multi-user configuration data, it solves the inability of multi-users to configure data in the prior art. Configure the same data set at the same time. Real-time conflict checking cannot be performed during data editing, and independent data submission and independent data rollback cannot be performed in units of specified users. At the same time, since the operation information of each user is recorded, it can support independent validation of data by user and independent rollback of data by user, and can play the function of real-time automatic data backup.

Device embodiment

According to the embodiment of the present invention, a kind of device of user configuration data is provided, below at first the design of the database table structure in the embodiment of the present invention is described in detail: for all data configuration tables are designed as two sets of tables in the database: one One set is an online table (O table) that stores real and effective online data. The O table is not provided for users to operate; the other set is an edit table (E table) that stores the user's offline editing process data. Users can only directly operate the E table. data.

The table structure difference between the O table and the E table is that each E table will add two attribute columns to store user operation process information: one column is the operation user name (CURRENT_USER) attribute column, which is used to store the user name for operating the record; The other column is the operation type (OP) attribute column, which is used to store the type of operation the user has performed on the record. For the OP attribute column, there are only three operation types: add (represented by A), modify (represented by M), and delete (represented by D).

In addition to the data configuration table, it is also necessary to maintain an incremental table (D table) to store the operation information that has been edited in the E table but not submitted to take effect, including the operating user name (CURRENT_USER) and the table name of the E table (TABLENAME).

Fig. 5 is a schematic structural diagram of a device for user configuration data according to an embodiment of the present invention. As shown in Fig. 5, the device for user configuration data according to an embodiment of the present invention includes: a first storage module 50, a data conflict module 52, a second storage module The module 54 and the data submitting module 56, each module of the embodiment of the present invention will be described in detail below.

Specifically, the first saving module 50 is used to save the operating user name and operation type under the corresponding configuration data entry in the E table according to the user's operation on the configuration data; wherein, the operation type includes: adding, modifying, and deleting;

A data conflict module 52, used for processing the conflicting data in the E table when the data in the E table conflicts;

The data conflict module 52 specifically includes:

The first data conflict sub-module is used to perform multiple operations on a configuration data entry by the same user, resulting in data conflicts. If an add operation is first performed on a certain configuration data entry, and then the configuration data entry is modified operation, the modified attribute is synchronized to the corresponding configuration data entry in the E table, and its operation type is set to increase; if the addition operation is performed on a certain configuration data entry first, then the configuration data entry is deleted , then directly delete the corresponding configuration data entry in the E table; if modifying a certain configuration data entry successively, set the operation type under the corresponding configuration data entry in the E table to modify; If the entry is modified, and then the configuration data entry is deleted, the operation type under the corresponding configuration data entry in Table E is set to delete; if a configuration data entry is deleted first, then the Configure the data entry to increase the operation, then compare the difference between the deleted configuration data entry and the newly added configuration data entry and modify the configuration data entry, and the operation type under the corresponding configuration data entry in the E table is set to modify;

The second data conflict sub-module is used to remind the next operating user that the configuration data item has been edited by other operating users and has not been submitted when different users perform multiple operations on a configuration data item, resulting in data conflicts take effect;

The third data conflict sub-module is used to prompt the user if the configuration data item referenced by the configuration data item modified by the user has been deleted by other users when different users operate on multiple configuration data items resulting in a data conflict. The user operation fails; if the configuration data entry referenced by the configuration data entry modified by the user is newly added by other users and has not been submitted to take effect, the user operation failure will be prompted; if the user deletes the configuration data referenced by other configuration data entries entry, and the operating user name under other configuration data entries is the user, and the operation type is delete, then set the operation type under the configuration data entry in E table to delete, if the user deletes the configuration referenced by other configuration data entries data entry, and the operation user name under other configuration data entries is empty or other users, the user will be prompted that the operation failed.

That is to say, data configuration is divided into three scenarios, no operation conflict, single user operation conflict and multi-user operation conflict.

1. The processing of no-operation conflicts by the data conflict module 52

For user USER A, if a record RECORD 1 in table E is added, the value of the CURRENT_USER column of RECORD 1 is set to USER A, and the value of the OP column is set to A; if a record RECORD 2 of E table is modified, RECORD The value of the CURRENT_USER column of 2 is set to USER A, and the value of the OP column is set to M; if a record RECORD 3 of the E table is deleted, the value of the CURRENT_USER column of RECORD 3 is set to USER A, and the value of the OP column is set to D , while RECORD 3 does not delete.

2. The data conflict module 52 handles single-user operation conflicts

For a single user, an operation conflict refers to multiple operations on the same data record in the same E table, including the following scenarios:

First A and then M, modify the attributes of M to this record synchronously, and the OP operator is still A;

First A and then D, directly delete the record from E table;

First M and then M, the OP operator is still M;

M first and then D, the OP operator is D;

First D and then A, compare the difference between the deleted record and the newly added record, make the attribute of the newly created record effective as M, and modify the OP to M.

3. The data conflict module 52 handles multi-user operation conflicts

For multiple users, operation conflicts include operation conflicts of a single record and operation conflicts of multiple records. Among them, the operation conflict of a single record means that USER A and USER B successively edit the same record of the same E table. For the editing application of the latter data record, an error should be prompted. That is, if it is found that the CURRENT_USER in the record in the E table is not empty, it will prompt the operating user who wants to apply to edit this record that other users have edited the data record and have not yet submitted it to take effect, and can only wait for the user to submit After it takes effect, the data can be edited, and other data can continue to be edited. The operation conflict of multiple records refers to the change of the reference relationship between records when different users add or delete records. Including the following scenarios:

USERA adds or modifies a record RECORD 1, which refers to RECORD 2, but RECORD 2 has been deleted by USER B. Therefore, in addition to checking whether RECORD 2 exists, a condition needs to be added during the data constraint check, which is to find RECORD 2 Whether the CURRENT_USER is empty, if it is not empty and the OP column is D, then the user will be prompted that the referenced record has been deleted by USER B, and the modification of RECORD 1 failed.

USERA adds or modifies a record RECORD 1, which references RECORD 2, but RECORD 2 is added by USER B and has not been submitted to take effect. Therefore, in addition to finding whether RECORD 2 exists during data constraint checking, it is necessary to add a The condition is to check whether the CURRENT_USER of RECORD2 is empty. If it is not empty and the OP column is A, then the user is prompted that the referenced record was added by USER B and has not been submitted to take effect, and the modification of RECORD 1 fails.

USER A deletes a record RECORD 1, but RECORD 1 is referenced by RECORD 2. If the CURRENT_USER of RECORD 2 is USER A and OP is D, the deletion is allowed; if CURRENT_USER is empty or USERB is not allowed to delete, RECORD 1 is deleted fail.

The second saving module 54 is used to save the table name of the E table and the corresponding operation user name in the preset D table under the condition that the data in the E table has no conflict;

The data submission module 56 is used to obtain the corresponding E table according to the user's operating user name and the D table when the user submits the configuration data, and submit the modified configuration data of the user recorded in the E table to the O table.

The data submission module 56 is specifically used for: when the user submits the configuration data, obtains the operation user name of the user who initiates the data submission request; Searches the table name of the E table corresponding to the operation user name in the D table according to the operation user name; The table name of the E table obtains the corresponding E table, obtains the configuration data entry whose operating user name is the user in the E table, and obtains the configuration data entry whose operating user name is other users according to the records in the O table; The operation indicated by the operation type of , merges the obtained configuration data entries, and submits the merged configuration data to the O table.

That is to say, when submitting data, the data submission module 56 first obtains the operating user USER A who initiates the data submission request, and searches the D table for the related list of the E table according to the user name. Then look for the database record where CURRENT_USER is USER A in each E table of these changes. For the records whose CURRENT_USER is not USER A, take those records in the corresponding O table, and merge them according to the operation indicated by the OP. The processing logic of merging is that for adding operations, it is directly adding; for modifying operations, it is directly modifying; for deleting operations, the corresponding records in the O table are deleted. The merged data will be submitted to Form O to take effect.

Preferably, the above-mentioned device also includes: a data rollback module, used to obtain the corresponding E table according to the user's operating user name and D table when the user rolls back the configuration data, and the E table according to the records in the O table The corresponding configuration data entry is rolled back, and the O table is used to save the effective configuration data;

The data rollback module is specifically used to: when the user rolls back the configuration data, obtain the operation user name of the user who initiates the data rollback request; find the table name of the E table corresponding to the operation user name in the D table according to the operation user name Obtain the corresponding E table according to the table name of the E table, obtain the configuration data entry of the user named the user in the E table, according to the operation indicated by the operation type under the configuration data entry obtained and the record in the O table, Roll back the corresponding configuration data entries in the E table;

That is to say, the data rollback module can roll back the user's operation to the state before editing before the user submits the data. Firstly, according to the selected operating user name for data rollback, go to the D table to obtain the corresponding E table list, and find all the modification records of the user in these E tables. According to the value of the OP column of these records, process respectively: for A operation, delete the record; for M operation, copy the corresponding record of O table to E table; for D operation, clear the attribute values of CURRENT USER and OP column.

Preferably, the above-mentioned device also includes: a data clearing module, which is used to clear the record of the user whose operating user name is the user in the D table, delete the corresponding record in the E table whose operating user name is the user and whose operation type is delete, and clear the record. In Table E, the operating user name is the operating user name and operation type under the user's configuration data entry.

That is to say, if the operation data of USERA is successfully submitted, the data clearing module needs to clear the records in table D where CURRENT_USER is USER A, delete the corresponding records in table E where CURRENT_USER is USERA and the OP column is a deletion mark, and then clear the corresponding table E CURRENT_USER in is the attribute column of USER A. If the operation data submission of USER A fails, the failure reason will be prompted to the user.

Fig. 2 is the schematic diagram of the relation of the online table editing table incremental table of the embodiment of the present invention, as shown in Fig. 2, comprise record 1 and record 2 in the O table, the value of the attribute 1 of record 1 is A2, the attribute 1 of record 2 The value is B1, USER A operates on E table 1, among which, record 1 and record 2 are respectively modified and deleted by USER A, record 3 is added by USER B, and table D records the operation of USER A The user name and its modified table name of E table 1, and the operating user name of USER B and its modified table name of E table 1. USER A submits data. First, obtain the E table 1 operated by USERA according to the records in D table, and merge the operations of record 1 and record 2 according to the records of USER A in E table 1, and submit them to O table to take effect, and finally , O table 1 includes the modified record 1. After the submission takes effect, clear the CURRENT_USER column and OP column of record 1 in E table 1, delete record 2, and delete the USERA record in D table.

The technical solutions of the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings.

Fig. 3 is a detailed processing flowchart of the method for user configuration data in an embodiment of the present invention, as shown in Fig. 3 , including the following processing:

Step 301, user operation E table record, save the operating user and operation type;

Step 302, data conflict check, if the check is passed, go to step 303; if the check is not passed, go to step 301;

Step 303, saving the changed E-list and operating user information in the D-list;

Step 304, the user selects data submission to enter step 306, and the user selects data rollback to enter step 305;

Step 305, roll back the corresponding record of E table according to O table, enter step 301;

Step 306, according to the changed E table records submitted to O table to take effect;

Step 307, if the data submission is successful, go to step 308, if the data submission fails, go to step 310;

Step 308, clear the operation user and operation type for the data records added and modified in the E table, delete the deleted data records, and enter step 309;

Step 309, clean up the operation information of the current operating user in table D, and end this configuration process;

Step 310, prompting the user of the reason for the failure of data submission, and ending the configuration process.

Fig. 4 is the flow chart of the data conflict check of the embodiment of the present invention, as shown in Fig. 4, comprises following processing:

Step 401, USER A edits data;

Step 402, determine the value of the CURRENT_USER column of the target record column, if the CURRENT_USER column is empty, then perform step 405, if the CURRENT_USER column is USERA, then perform step 403, if the CURRENT_USER column is USERB, then perform step 404;

Step 403, merge according to the algorithm according to the sequence operator, and execute step 405;

Step 404, check the reference relationship of the data record, if the check is passed, then execute step 405, otherwise, execute step 406;

Step 405, submitting the modification to Form E;

In step 406, the user is prompted about the reason for the operation failure.

In the embodiment of the present invention, the database configuration table is designed as two sets of tables, the online table and the editing table, wherein the online table is completely consistent with the existing data configuration table, and the table structure of the editing table is completely based on the table structure of the existing data configuration table Based on the transformation, according to the information recorded in the online table, edit table and incremental table to control the user-by-user and user-by-user rollback process of multi-user configuration data, it solves the inability of multi-users to configure data in the prior art. Configure the same data set at the same time. Real-time conflict checking cannot be performed during data editing, and independent data submission and independent data rollback cannot be performed in units of specified users. At the same time, since the operation information of each user is recorded, it can support independent validation of data by user and independent rollback of data by user, and can play the function of real-time automatic data backup.

Although preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, and therefore, the scope of the present invention should not be limited to the above-described embodiments.

Claims (9)

1. A method for user configuration data, comprising: According to the user's operation on the configuration data, save the operating user name and operation type under the corresponding configuration data entry in the editing table, and process the conflicting data in the editing table when there is a conflict in the data in the editing table , in the case that the data in the edit table has no conflict, save the table name of the edit table and the corresponding operation user name in the preset increment table; The operation types include: adding, modifying and deleting; When the data in the editing table conflicts, processing the conflicting data in the editing table specifically includes: In the case that the same user performs multiple operations on a configuration data entry, resulting in data conflicts, if the add operation is performed on a configuration data entry first, and then the configuration data entry is modified, the modified attributes will be synchronized to Under the corresponding configuration data entry in the edit table, and set its operation type to add; if an add operation is performed on a certain configuration data entry first, and then a delete operation is performed on the configuration data entry, the edit will be directly deleted The corresponding configuration data entry in the table; if modifying a certain configuration data entry successively, set the operation type under the corresponding configuration data entry in the editing table to modify; if modifying a certain configuration data entry first operation, and then delete the configuration data entry, set the operation type under the corresponding configuration data entry in the edit table to delete; When the data entry is added, compare the difference between the deleted configuration data entry and the newly added configuration data entry and modify the configuration data entry, and set the operation type under the corresponding configuration data entry in the editing table to modify; In the case that different users perform multiple operations on a configuration data entry, resulting in data conflicts, the next operating user is prompted that the configuration data entry has been edited by other operating users and has not been submitted to take effect; In the case that different users operate on multiple configuration data entries, resulting in data conflicts, if the configuration data entry referenced by the configuration data entry modified by the user has been deleted by other users, the user will be prompted to fail the operation; The configuration data entry referenced by the configuration data entry is newly added by other users and has not been submitted to take effect, the user will be prompted that the operation failed; if the user deletes the configuration data entry referenced by other configuration data entries, and the other configuration data entries The operation user name under the user is the user, and the operation type is delete, then set the operation type under the configuration data entry in the edit table to delete, if the user deletes the configuration data entry referenced by other configuration data entries, and the If the operation user name under other configuration data items mentioned above is empty or other users, the user will be prompted that the operation failed; When the user submits the configuration data, obtain the corresponding editing table according to the user's operating user name and the increment table, and submit the modified configuration data of the user recorded in the editing table to the online table, wherein the The online table is used to save the effective configuration data. 2. The method according to claim 1, wherein, before the user submits the configuration data, the method further comprises: When the user rolls back the configuration data, the corresponding editing table is obtained according to the operating user name of the user and the increment table, and the corresponding configuration data entry in the editing table is rolled back according to the records in the online table. 3. The method according to claim 2, wherein, when the user rolls back configuration data, obtain the corresponding editing table according to the user's operating username and the incremental table, and according to the record in the online table, the Editing the corresponding configuration data entry in the table for rollback includes: When the user rolls back the configuration data, obtain the operating username of the user who initiated the data rollback request; Searching the incremental table for the table name of the editing table corresponding to the operating user name according to the operating user name; Obtain the corresponding edit table according to the table name of the edit table, obtain the configuration data entry whose operating user name is the user in the edit table, and obtain the operation indicated by the operation type under the obtained configuration data entry and the Records in the above-mentioned online table, and roll back the corresponding configuration data entry in the edit table. 4. The method according to claim 1, wherein, when the user submits the configuration data, the corresponding editing table is obtained according to the user's operation user name and the increment table, and the data recorded in the editing table is The modified configuration data submitted by the user to the online form specifically includes: When the user submits the configuration data, obtain the operation user name of the user who initiates the data submission request; Searching the incremental table for the table name of the editing table corresponding to the operating user name according to the operating user name; Obtain the corresponding edit table according to the table name of the edit table, obtain the configuration data entry whose operation user name is the user in the edit table, and obtain the configuration data entry of the operation user name other users according to the records in the online table data entry; According to the operation indicated by the operation type in the editing table, merge the obtained configuration data entries, and submit the merged configuration data to the online table. 5. The method according to claim 1 or 2, wherein, after submitting the modified configuration data of the user recorded in the editing table to the online table, the method further comprises: Clear the records in the incremental table with the user name as the user, delete the records in the corresponding editing table with the user name as the user and the operation type as delete, and clear the configuration in the edit table with the user name as the user Operation username and operation type under the data entry. 6. A device for configuring user data, comprising: The first saving module is used to save the operating user name and operation type under the corresponding configuration data entry in the edit table according to the user's operation on the configuration data; A data conflict module, configured to process the conflicting data in the editing table when there is a conflict in the data in the editing table; The second saving module is used to save the table name of the editing table and the corresponding operating user name in the preset increment table when the data in the editing table has no conflict; The data submission module is used to obtain the corresponding editing table according to the user's operating user name and the incremental table when the user submits the configuration data, and submit the modified configuration data of the user recorded in the editing table to the online table, wherein the online table is used to save effective configuration data; The operation types include: add, modify, and delete; The data conflict module specifically includes: The first data conflict sub-module is used to perform multiple operations on a configuration data entry by the same user, resulting in data conflicts. If an add operation is first performed on a certain configuration data entry, and then the configuration data entry is modified operation, the modified attribute is synchronized to the corresponding configuration data entry in the edit table, and its operation type is set to increase; if the addition operation is performed on a certain configuration data entry first, then the configuration data entry is executed Delete operation, then directly delete the corresponding configuration data entry in the edit table; if a modification operation is performed on a certain configuration data entry successively, the operation type under the corresponding configuration data entry in the edit table is set to modify; if First perform a modification operation on a certain configuration data entry, and then perform a delete operation on the configuration data entry, then set the operation type under the corresponding configuration data entry in the edit table to delete; if a certain configuration data entry is first Execute the delete operation, then add the configuration data entry to the configuration data entry, then compare the difference between the deleted configuration data entry and the newly added configuration data entry and modify the configuration data entry, and add the corresponding configuration data in the edit table The operation type under the entry is set to Modify; The second data conflict sub-module is used to remind the next operating user that the configuration data item has been edited by other operating users and has not been submitted when different users perform multiple operations on a configuration data item, resulting in data conflicts take effect; The third data conflict sub-module is used to prompt the user if the configuration data item referenced by the configuration data item modified by the user has been deleted by other users when different users operate on multiple configuration data items resulting in a data conflict. The user operation fails; if the configuration data entry referenced by the configuration data entry modified by the user is newly added by other users and has not been submitted to take effect, the user operation failure will be prompted; if the user deletes the configuration data referenced by other configuration data entries entry, and the operating user name under the other configuration data entry is the user, and the operation type is delete, then set the operation type under the configuration data entry in the edit table to delete, if the user deletes it by other configuration data entries The referenced configuration data entry, and the operation user name under the other configuration data entry is empty or other users, prompting that the operation failed for the user. 7. The device of claim 6, further comprising: The data rollback module is used to obtain the corresponding editing table according to the user's operating user name and the incremental table when the user rolls back the configuration data, and the corresponding configuration data entry in the editing table according to the records in the online table Do a rollback. 8. The apparatus of claim 7, wherein The data rollback module is specifically used for: when the user rolls back the configuration data, obtain the operating user name of the user who initiates the data rollback request; search the incremental table according to the operating user name and the operating user The table name of the editing table corresponding to the first name; according to the table name of the editing table, obtain the corresponding editing table, and obtain the configuration data entry of the user named the user in the editing table, according to the obtained configuration data entry The operation indicated by the operation type under and the records in the online table are rolled back to the corresponding configuration data entry in the edit table; The data submission module is specifically used for: when the user submits the configuration data, obtain the operation user name of the user who initiates the data submission request; according to the operation user name, search in the incremental table for the user name corresponding to the operation user name. The table name of the editing table; obtain the corresponding editing table according to the table name of the editing table, obtain the configuration data entry whose operating user name is the user in the editing table, and obtain the operation according to the record in the online table The user name is the configuration data entry of other users; according to the operation indicated by the operation type in the editing table, merge the obtained configuration data entries, and submit the merged configuration data to the online table . 9. The device according to claim 6 or 7, wherein the device further comprises: The data clearing module is used to clear the records in the incremental table whose operating user name is the user, delete the records in the corresponding editing table whose operating user name is the user and whose operation type is delete, and clear the operating user in the editing table The action user name and action type under the configuration data entry named for this user.