CN111241198B - Data synchronization method and device and data processing equipment - Google Patents
Data synchronization method and device and data processing equipment Download PDFInfo
- Publication number
- CN111241198B CN111241198B CN202010013544.7A CN202010013544A CN111241198B CN 111241198 B CN111241198 B CN 111241198B CN 202010013544 A CN202010013544 A CN 202010013544A CN 111241198 B CN111241198 B CN 111241198B
- Authority
- CN
- China
- Prior art keywords
- data
- synchronization
- data table
- data item
- identification
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000012545 processing Methods 0.000 title claims abstract description 17
- 239000003607 modifier Substances 0.000 claims description 25
- 230000004048 modification Effects 0.000 claims description 19
- 238000012986 modification Methods 0.000 claims description 19
- 239000000758 substrate Substances 0.000 claims 1
- 230000001360 synchronised effect Effects 0.000 abstract description 17
- 238000010586 diagram Methods 0.000 description 12
- 230000009471 action Effects 0.000 description 7
- 230000006870 function Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 238000010200 validation analysis Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000002085 persistent effect Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a data synchronization method, a data synchronization device and data processing equipment, wherein the method comprises the following steps: acquiring a data synchronization request, wherein the data synchronization request comprises an identification of a target data table; determining the target data table in a main database according to the identification of the target data table; synchronizing the target data item marked as the non-effective state in the target data table to a slave database, and marking the target data item as the effective state after synchronization is completed. Therefore, the data in the selected range of the user can be synchronized with the master database and the slave database at the time selected by the user, so that the flexibility of data synchronization is improved, and the requirements of different business scenes are met.
Description
Technical Field
The present invention relates to the field of information processing technologies, and in particular, to a data synchronization method, a data synchronization device, and a data processing device.
Background
In some database usage scenarios, in order to control the read-write rights of the database or to avoid the bottleneck of the read-write operation of the database, a master database and a slave database are provided, the master database allowing its data to be written or modified, the data of the slave database being synchronized with the master database, but the slave database allowing only its data to be read out.
In the existing master-slave database synchronization scheme, synchronization of the slave databases is generally performed automatically after data change of the master database, or data is simultaneously persisted to the master database and the slave database according to a user operation log. However, in these synchronization methods, the user cannot control the time or the range of data synchronization, and cannot flexibly perform synchronization actions for some data that does not need immediate synchronization to the slave database.
Disclosure of Invention
To overcome the above-mentioned drawbacks of the prior art, an object of the present application is to provide a data synchronization method, which includes:
acquiring a data synchronization request, wherein the data synchronization request comprises an identification of a target data table;
determining the target data table in a main database according to the identification of the target data table;
synchronizing the target data item marked as the non-effective state in the target data table to a slave database, and marking the target data item as the effective state after synchronization is completed.
In some possible implementations of the present application, the method further includes:
after the data items in the primary database are modified, the modified data item configuration is identified as an inactive state.
In some possible implementations of the present application, the data synchronization request further includes a requester identifier, and the data item stored in the main database records an identifier of the modifier;
a step of synchronizing target data items in the target data table identified as inactive state to a slave database, comprising:
and synchronizing the target data item, which is matched with the requester identifier and is identified as being in an inactive state, to a slave database according to the identifier of the modifier in the target data table.
In some possible implementations of the present application, the method further includes:
after the data item in the master database is modified, the identity of the modifier is recorded in the data item to be modified.
In some possible implementations of the present application, the method further includes:
after the data items in the main database are modified, recording the identification of a data table in which the modified data items are located;
displaying the identification of the modified data table on a display interface;
the step of obtaining the data synchronization request comprises the following steps:
and acquiring a data synchronization request generated by the operation of the user on the display interface, wherein the data synchronization request comprises the identification of a target data table selected by the user from the displayed at least one data table.
In some possible implementations of the present application, after the data item in the primary database is modified, the step of recording the identifier of the data table in which the modified data item is located includes:
after the data item in the main database is modified, recording the identification of the data table in which the modified data item is positioned into a preset modification record table, and recording the identification of a modifier for executing modification on the data table;
a step of displaying an identification of the modified data table on the display interface, comprising;
acquiring a login user identifier of a user logged in on the display interface;
and searching a data table of which the identifier of the modifier is matched with the identifier of the login user in the modification record table.
In some possible implementations of the present application, the method further includes:
detecting a synchronization result of the target data item;
if the synchronization result is that the synchronization is successful, a data update notification is sent to an operation system corresponding to the target data item;
if the synchronization result is that the synchronization fails, the data of the target data item in the slave database is rolled back, and a synchronization failure alarm is generated.
Another object of the present application is to provide a data synchronization device, the device comprising:
the request acquisition module is used for acquiring a data synchronization request, wherein the data synchronization request comprises an identification of a target data table;
the data table determining module is used for determining the target data table in the main database according to the identification of the target data table;
and the data item synchronization module is used for synchronizing the target data item marked as the non-effective state in the target data table to the slave database, and marking the target data item as the effective state after the synchronization is completed.
Another object of the present application is to provide a data processing apparatus comprising a machine-readable storage medium storing machine-executable instructions which, when executed by the processor, implement the data synchronization method provided herein, and a processor.
It is another object of the present application to provide a machine-readable storage medium storing machine-executable instructions which, when executed by a processor, implement the data synchronization method provided herein.
Compared with the prior art, the application has the following beneficial effects:
the application provides a data synchronization method, a data synchronization device and data processing equipment, wherein when a data synchronization request is received, a corresponding target data table in a master database is determined according to the identification of a target data table appointed in the data synchronization request, and then target data items marked as an unactuated state in the target data table are synchronized to a slave database. Therefore, the data in the selected range of the user can be synchronized with the master database and the slave database at the time selected by the user, so that the flexibility of data synchronization is improved, and the requirements of different business scenes are met.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered limiting the scope, and that other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a data system according to an embodiment of the present application;
fig. 2 is a flow chart of a data synchronization method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a data processing apparatus according to an embodiment of the present application;
fig. 4 is a schematic diagram of a functional module of a data synchronization device according to an embodiment of the present application;
fig. 5 is a second schematic diagram of a functional module of the data synchronization device according to the embodiment of the present application.
Icon: 100-a data processing device; 110-a data synchronization device; 111-request acquisition module; 112-a data table determination module; 113-a data item synchronization module; 114-a data item identification module; 115-a data table recording module; 116-a data display module; 117-a synchronization detection module; 120-a machine-readable storage medium; 130-a processor; 10-a service system; 20-a master database; 30-slave database; 40-operating the system.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, which are generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, as provided in the accompanying drawings, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
In the description of the present application, it should also be noted that, unless explicitly specified and limited otherwise, the terms "disposed," "mounted," "connected," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the terms in this application will be understood by those of ordinary skill in the art in a specific context.
In some database usage scenarios, a master database and a slave database may be set in order to control read-write rights of the databases or in order to avoid bottlenecks in read-write operations of the databases. In such a scenario, an administrator typically performs an addition, deletion or modification of data with respect to the master database, and then the data of the master database may be synchronized to the slave data, and the operating system may only acquire the data from the slave database.
In some business scenarios, however, changes to data configured by an administrator in a master database may not require immediate synchronization to a slave database for use by an operating system.
Taking the "live internet" scenario as an example, different administrators may configure different databases according to different business requirements, such as gift configuration data, lottery configuration data, and the like. These data may be pre-configured for the interaction event to be performed at a particular time later and do not need to be immediately synchronized to use from the database to the operating system.
In view of the fact that the existing automatic synchronization mechanism of the master database and the slave database cannot flexibly meet the above-mentioned needs, the present embodiment provides a data synchronization scheme capable of flexibly executing synchronization actions, and the scheme provided by the present embodiment is explained in detail below.
Referring to fig. 1, fig. 1 is a schematic diagram of a data system provided in this embodiment, where the data system may include a service system 10, a master database 20, and at least one slave database 30. The business system 10, the master database 20 and the slave database 30 may be different electronic devices, or may be relatively independent logic components configured on the same electronic device.
A user may perform actions such as adding, deleting, or modifying data from the primary database 20 through the business system 10. The business system 10 may read data from the master database 20 and synchronize to the slave database 30. Other third party operating systems 40 may communicate with the business system 10 or the slave database 30 to obtain data from the slave database 30 through the business system 10 or directly from the slave database 30.
Referring to fig. 2, fig. 2 is a flow chart of a data synchronization method according to the present embodiment, and each step of the method is explained in detail below.
Step S110, a data synchronization request is acquired, where the data synchronization request includes an identification of a target data table.
In this embodiment, the user may access the service system 10 and initiate the data synchronization request on the service system 10 through a specific client or a web page provided by the service system 10 at a time required by the user; or the user may invoke the interface of the service system 10 through other terminals at the time required by himself to send the data synchronization request to the service system 10.
The data synchronization request may include an identifier of a target data table designated by a user and required to perform synchronization.
Step S120, determining the target data table in the main database 20 according to the identification of the target data table.
Step S130, synchronizing the target data item identified as the inactive state in the target data table to the slave database 30, and identifying the target data item as the active state after synchronization is completed.
In this embodiment, a target data table may be determined from the master database 20 by the service system 10, and target data identified as an inactive state in the target data table may be read and then written to the slave database 30.
The master database 20 may also be notified of the determined target data table by the business system 10, and then the slave database 30 may be synchronized by the master database 20 with the data items in the target data table that are identified as inactive.
The secondary database 30 may also be notified of the determined target data table by the business system 10, and then a data query may be initiated by the secondary database 30 to the primary database 20 and data for the queried target data item identified as an inactive state in the target data table may be obtained.
Based on the above design, in the data synchronization scheme provided in this embodiment, the data in the selected range of the user can be synchronized with the master database 30 at the time selected by the user, so that the flexibility of data synchronization of the master database 30 is improved, and the requirements of different service scenarios are satisfied.
Alternatively, in this embodiment, after the data item in the main database 20 is modified, the modified data item configuration may be identified as an inactive state.
For example, each data item in the master database 20 has a preset field assigned a different value that identifies whether the data item has been synchronized to the slave database 30.
When a user performs an addition or modification to a certain data item of the master database 20, the preset field of the data item is configured to be a first preset value to identify that the data item is in an inactive state, i.e. the data item is a new or modified data item and has not yet been synchronized to the slave data.
Then in step S130, after the data item has been synchronized to the slave database 30, the preset field of the data item is configured to a second preset value to identify that the data item is in an validated state, i.e. that the data item has been synchronized to the slave database 30.
It should be noted that, the modification of the data in the main database 20 may be performed by the service system 10 receiving the modification of the user, obtaining a modification log, and persisting the modification content to the main database 20 according to the modification log. Unlike the prior art, however, the act of persisting the modified content to the slave database 30 according to the oplog is not performed in this embodiment.
Alternatively, in some scenarios, different users may modify different data items in the same data table according to different business needs. In this embodiment, after the data item in the main database 20 is modified, when the modified data item configuration is identified as an inactive state, an identifier of a modifier may also be recorded in the data item, where the identifier of the modifier may be an identity of a user performing modification on the data item.
In step S110, the data synchronization request may further include a requester identifier, where the requester identifier is an identity of the user that initiates the data synchronization request.
Then in step S130, the target data item in the target data table, whose identification matches the requester identification and is identified as being in an inactive state, may be synchronized to the slave database 30.
In some examples, "the identification of the modifier matches the requester identification" may mean that the identification of the modifier is the same as the requester identification. I.e. only allowing the user to synchronize his own modified data.
For example, after the user a modifies the data item in the database, the identifier of the modifier in the modified data item is the identifier of the user a.
In step S110, when the user a initiates the data synchronization request, the requester is identified as the identity of the user a. In step S130, only the target data item identified as the identity of user a of the modifier may be looked up for synchronization.
In other examples, "the identification of the modifier matches the identification of the requester" may mean that the identification of the modifier has a corresponding rights matching relationship with the identification of the requester. That is, the user can be allowed to synchronize the data modified by other users according to the corresponding relationship of the user rights.
For example, assuming that the user B has authority to synchronize the data modified by the user a, if in step S110 the user B initiates a data synchronization request, and the requester is identified as the identity of the user B, in step S130, the target data item identified as the user a by searching for the modifier may be allowed to be synchronized according to the authority correspondence between the user B and the user a.
Based on the above design, in the data synchronization method provided in this embodiment, synchronization can be performed on data in a corresponding range according to identity information of a user requesting for synchronization data, so that granularity of a data range needing synchronization is reduced, and flexibility of data synchronization is improved.
Alternatively, in general, the data to be synchronized is modified in the main database 20, so that the user may select the target data table to be synchronized conveniently, and in this embodiment, after the data item in the main database 20 is modified by the service system 10, the identifier of the data table in which the modified data item is located may be recorded.
Then, when the user needs to perform data synchronization, a display interface is provided by the service system 10, and the identification of the modified data table is displayed on the display interface. In this way, the user can intuitively understand from the display interface which data tables have been modified.
The user can select a modified data table to be determined as a target data table through operations such as clicking on the display interface, and initiate a data synchronization request aiming at the target data table.
For example, in some examples, an update validation button may be displayed for each modified data table, and the user initiates a data update request for that data table as the target data table upon clicking on the update validation button. In other examples, the checked frame may be displayed for each modified data table, and the user may click on the checked required data table as the target data table and then click on an update validation button to initiate a data update request for the selected target data table.
Optionally, when recording the identity of the data table in which the modified data item is located, the identity of the modifier performing the modification to the data table may also be recorded by the business system 10.
When the user needs to perform data synchronization, the service system 10 may acquire a login user identifier of the user logged on the display interface, and then search the modification record table for a data table in which the identifier of the modifier matches the login user identifier. Therefore, only the modified data table corresponding to the identity of the user who wants to execute the data synchronization is displayed, the selection operation of the user is facilitated, and the execution authority range of the data synchronization action is effectively controlled.
Optionally, in this embodiment, the service system 10 may also detect a synchronization result of the target data item.
And if the synchronization result is that the synchronization is successful, sending a data update notification to the operation system 40 corresponding to the target data item. In this manner, the operating system 40 may timely acquire data from the slave data and use it.
If the synchronization result is a synchronization failure, the data of the target data item in the slave database 30 is rolled back, and a synchronization failure alarm is generated. In this way, the developer can learn the problem and process the problem in time.
Referring to fig. 3, fig. 3 is a block diagram of a data processing apparatus 100 according to the present embodiment. Wherein the business system 10 shown in fig. 1 may be operated in said data processing device 100.
The data processing apparatus 100 comprises a data synchronization device 110, a machine readable storage medium 120, and a processor 130.
The machine-readable storage medium 120 and the processor 130 are directly or indirectly electrically connected to each other to realize data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The data synchronization means 110 comprise at least one software functional module which may be stored in the machine readable storage medium 120 in the form of software or firmware (firmware) or which is solidified in the Operating System (OS) of the data processing device 100. The processor 130 is configured to execute executable modules stored in the machine-readable storage medium 120, such as software functional modules and computer programs included in the data synchronization device 110.
The machine-readable storage medium 120 may be, but is not limited to, random access Memory (Random Access Memory, RAM), read Only Memory (ROM), programmable Read Only Memory (Programmable Read-Only Memory, PROM), erasable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc. Wherein the machine-readable storage medium 120 is used to store a program, and the processor 130 executes the program after receiving the execution instruction.
The processor 130 may be an integrated circuit chip with signal processing capabilities. The processor 130 may be a general-purpose processor 130, including a central processing unit 130 (Central Processing Unit, CPU for short), a network processor 130 (Network Processor, NP for short), etc.; but may also be a digital signal processor 130 (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. The general purpose processor 130 may be a microprocessor 130 or the processor 130 may be any conventional processor 130 or the like.
Referring to fig. 4, fig. 4 is a schematic diagram of a data synchronization device 110 according to the present embodiment, where the data synchronization device 110 includes at least one functional module that can be stored in a machine-readable storage medium 120 in the form of software. Functionally divided, the data synchronization means 110 may comprise a request acquisition module 111, a data table determination module 112 and a data item synchronization module 113.
The request acquisition module 111 is configured to acquire a data synchronization request, where the data synchronization request includes an identifier of a target data table.
In this embodiment, the request acquiring module 111 may be configured to perform step S110 shown in fig. 2, and a specific description of the request acquiring module 111 may refer to a description of the step S110.
The data table determining module 112 is configured to determine the target data table in the primary database 20 according to the identification of the target data table.
In this embodiment, the data table determining module 112 may be configured to perform step S120 shown in fig. 2, and a specific description of the data table determining module 112 may refer to a description of the step S120.
The data item synchronization module 113 is configured to synchronize a target data item identified as an inactive state in the target data table to the slave database 30, and identify the target data item as an active state after synchronization is completed.
In this embodiment, the data item synchronization module 113 may be used to execute step S130 shown in fig. 2, and a specific description of the data item synchronization module 113 may refer to a description of step S130.
Optionally, referring to fig. 5, in this embodiment, the data synchronization device 110 further includes a data item identification module 114.
The data item identification module 114 is configured to identify, after a data item in the primary database 20 has been modified, the modified data item configuration as an inactive state.
Optionally, in this embodiment, the data synchronization request further includes a requester identifier, and the data item stored in the master database 20 records an identifier of the modifier.
The data item synchronization module 113 is specifically configured to synchronize, to the slave database 30, a target data item in the target data table, where the identifier of the modifier matches the identifier of the requester and is identified as being in an inactive state.
Optionally, in this embodiment, the data synchronization device 110 further includes a data item identification module 114.
The data item identification module 114 is configured to record, after the data item in the main database 20 is modified, an identification of a modifier in the modified data item.
Optionally, in this embodiment, the data synchronization device 110 further includes a data table recording module 115 and a data display module 116.
The data table recording module 115 is configured to record, after the data item in the primary database 20 is modified, an identification of a data table in which the modified data item is located.
The data display module 116 is configured to display the identification of the modified data table on a display interface.
The request obtaining module 111 is specifically configured to obtain a data synchronization request generated by a user performing an operation on the display interface, where the data synchronization request includes an identification of a target data table selected by the user from the displayed at least one data table.
Optionally, in this embodiment, the data table recording module 115 is specifically configured to record, after the data item in the main database 20 is modified, an identifier of a data table in which the modified data item is located into a preset modification record table, and record an identifier of a modifier that performs modification on the data table.
The data display module 116 is specifically configured to obtain a login user identifier of a user logged in on the display interface; and searching a data table of which the identifier of the modifier is matched with the identifier of the login user in the modification record table.
Optionally, in this embodiment, the data synchronization device 110 further includes a synchronization detection module 117.
The synchronization detection module 117 is configured to detect a synchronization result of the target data item; if the synchronization result is that the synchronization is successful, sending a data update notification to the operation system 40 corresponding to the target data item; if the synchronization result is a synchronization failure, the data of the target data item in the slave database 30 is rolled back, and a synchronization failure alarm is generated.
In summary, the present application provides a data synchronization method, apparatus, and data processing device, which determine, when a data synchronization request is received, a corresponding target data table in a master database according to an identifier of a target data table specified in the data synchronization request, and then synchronize a target data item identified as an inactive state in the target data table to a slave database. Therefore, the data in the selected range of the user can be synchronized with the master database and the slave database at the time selected by the user, so that the flexibility of data synchronization is improved, and the requirements of different business scenes are met.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners as well. The apparatus embodiments described above are merely illustrative, for example, flow diagrams and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, the functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing is merely various embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (6)
1. A method of data synchronization, the method comprising:
after the data item in the main database is modified by an administrator, the modified data item configuration is marked as an unactuated state, the mark of a modifier is recorded in the data item to be modified, and the mark of a data table in which the modified data item is positioned is recorded;
displaying the identification of the modified data table on a display interface;
acquiring a data synchronization request generated by a user operating on the display interface, wherein the data synchronization request comprises an identification of a target data table selected by the user from at least one displayed data table and a requester identification;
determining the target data table in a main database according to the identification of the target data table;
synchronizing the target data item which is matched with the requester identifier and is identified as the non-effective state in the target data table, wherein the target data item is used for an operation system from a database, and the identifier of the target data item is identified as the effective state after the synchronization is completed.
2. The method of claim 1, wherein the step of determining the position of the substrate comprises,
after the data item in the main database is modified by an administrator, the step of recording the identification of the data table in which the modified data item is located includes:
after the data item in the main database is modified by an administrator, recording the identification of the data table in which the modified data item is positioned into a preset modification record table, and recording the identification of a modifier for executing modification on the data table;
a step of displaying the identification of the modified data table on a display interface, comprising;
acquiring a login user identifier of a user logged in on the display interface;
and searching a data table of which the identifier of the modifier is matched with the identifier of the login user in the modification record table.
3. The method according to claim 1, wherein the method further comprises:
detecting a synchronization result of the target data item;
if the synchronization result is that the synchronization is successful, a data update notification is sent to an operation system corresponding to the target data item;
if the synchronization result is that the synchronization fails, the data of the target data item in the slave database is rolled back, and a synchronization failure alarm is generated.
4. A data synchronization device, the device comprising:
the data item identification module is used for identifying the modified data item configuration as an unactuated state after the data item in the main database is modified by an administrator and recording the identification of a modifier in the data item to be modified;
the data table recording module is used for recording the identification of the data table where the modified data item is located;
the data display module is used for displaying the identification of the modified data table on a display interface;
the request acquisition module is used for acquiring a data synchronization request generated by the operation of a user on the display interface, wherein the data synchronization request comprises the identification of a target data table selected by the user from at least one displayed data table and the identification of a requester;
the data table determining module is used for determining the target data table in the main database according to the identification of the target data table;
and the data item synchronization module is used for synchronizing the target data item which is matched with the identifier of the requester and is identified as the non-effective state in the target data table to the operation system from the database, and after the synchronization is completed, the identifier of the target data item is identified as the effective state.
5. A data processing apparatus comprising a machine-readable storage medium and a processor, the machine-readable storage medium storing machine-executable instructions which, when executed by the processor, implement the method of any one of claims 1-3.
6. A machine-readable storage medium storing machine-executable instructions which, when executed by a processor, implement the method of any one of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010013544.7A CN111241198B (en) | 2020-01-02 | 2020-01-02 | Data synchronization method and device and data processing equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010013544.7A CN111241198B (en) | 2020-01-02 | 2020-01-02 | Data synchronization method and device and data processing equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111241198A CN111241198A (en) | 2020-06-05 |
| CN111241198B true CN111241198B (en) | 2024-02-27 |
Family
ID=70877667
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010013544.7A Active CN111241198B (en) | 2020-01-02 | 2020-01-02 | Data synchronization method and device and data processing equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111241198B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112835936A (en) * | 2021-02-05 | 2021-05-25 | 北京电解智科技有限公司 | Data processing method and device and service cluster |
| CN113672604A (en) * | 2021-08-16 | 2021-11-19 | 浙江大华技术股份有限公司 | User data synchronization method, device and system and electronic equipment |
| CN114185896B (en) * | 2021-12-14 | 2024-07-09 | 中国平安财产保险股份有限公司 | Data processing method, device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101038591A (en) * | 2007-04-11 | 2007-09-19 | 华为技术有限公司 | Method and system for synchronizing data base |
| CN105069059A (en) * | 2015-07-28 | 2015-11-18 | 小米科技有限责任公司 | Database synchronization method and apparatus |
| CN105787077A (en) * | 2016-03-02 | 2016-07-20 | 百度在线网络技术（北京）有限公司 | Data synchronizing method and device |
| CN106709066A (en) * | 2017-01-19 | 2017-05-24 | 杭州数梦工场科技有限公司 | Data synchronization method and device |
| CN108228814A (en) * | 2017-12-29 | 2018-06-29 | 泰康保险集团股份有限公司 | Method of data synchronization and device |
| CN109325037A (en) * | 2018-08-17 | 2019-02-12 | 中国平安人寿保险股份有限公司 | A kind of method of data synchronization, storage medium and server for mass data |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140258234A1 (en) * | 2013-03-11 | 2014-09-11 | AppGlu, Inc. | Synchronization of cms data to mobile device storage |
-
2020
- 2020-01-02 CN CN202010013544.7A patent/CN111241198B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101038591A (en) * | 2007-04-11 | 2007-09-19 | 华为技术有限公司 | Method and system for synchronizing data base |
| CN105069059A (en) * | 2015-07-28 | 2015-11-18 | 小米科技有限责任公司 | Database synchronization method and apparatus |
| CN105787077A (en) * | 2016-03-02 | 2016-07-20 | 百度在线网络技术（北京）有限公司 | Data synchronizing method and device |
| CN106709066A (en) * | 2017-01-19 | 2017-05-24 | 杭州数梦工场科技有限公司 | Data synchronization method and device |
| CN108228814A (en) * | 2017-12-29 | 2018-06-29 | 泰康保险集团股份有限公司 | Method of data synchronization and device |
| CN109325037A (en) * | 2018-08-17 | 2019-02-12 | 中国平安人寿保险股份有限公司 | A kind of method of data synchronization, storage medium and server for mass data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111241198A (en) | 2020-06-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11698885B2 (en) | System and method for content synchronization | |
| JP6793766B2 (en) | Displaying presence in applications that access shared and synchronized content | |
| CN111241198B (en) | Data synchronization method and device and data processing equipment | |
| JP6980062B2 (en) | Managing presence across devices that access shared and synchronized content | |
| US10637896B2 (en) | User notification for interaction information | |
| US9268655B2 (en) | Interface for resolving synchronization conflicts of application states | |
| US10725802B2 (en) | Methods and apparatus for using tags to control and manage assets | |
| US9864736B2 (en) | Information processing apparatus, control method, and recording medium | |
| US20200125660A1 (en) | Quick identification and retrieval of changed data rows in a data table of a database | |
| US10949401B2 (en) | Data replication in site recovery environment | |
| CN109885786B (en) | Data caching processing method and device, electronic equipment and readable storage medium | |
| WO2015100307A1 (en) | Providing access to a cloud based content management system on a mobile device | |
| JP6447258B2 (en) | Management program, management method, and management apparatus | |
| US9514176B2 (en) | Database update notification method | |
| CN110619226A (en) | Platform-based data processing method, system, equipment and storage medium | |
| US11048668B2 (en) | Sensitive data management | |
| CN112115203A (en) | Asset management method, device, equipment and storage medium of cloud platform | |
| CN112948884B (en) | Method and system for implementing big data access control on application level user | |
| CN110928945A (en) | Data processing method and device for database and data processing system | |
| JP2014021754A (en) | Virtual machine management system, virtual machine management method, and program | |
| US9467452B2 (en) | Transferring services in a networked environment | |
| CN111913980A (en) | Equipment management method and device | |
| US10778514B1 (en) | Universal configurations | |
| CN109639509B (en) | Network equipment configuration method and device | |
| US12107901B2 (en) | Device management system, device management method, and recording medium having device management program recorded thereon |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |