CN110209534B - System and method for automatically backing up mysql database - Google Patents
System and method for automatically backing up mysql database Download PDFInfo
- Publication number
- CN110209534B CN110209534B CN201910516092.1A CN201910516092A CN110209534B CN 110209534 B CN110209534 B CN 110209534B CN 201910516092 A CN201910516092 A CN 201910516092A CN 110209534 B CN110209534 B CN 110209534B
- Authority
- CN
- China
- Prior art keywords
- database
- data
- formal
- backup
- micro
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/80—Database-specific techniques
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a backup technology of a mysql database, and discloses a system and a method for automatically backing up the mysql database, which solve the problem that the work efficiency is low because a large amount of time is occupied because data is firstly exported from the mysql database and then imported into a local database when the data needs to be checked in the traditional technology. The system of the invention comprises: the system comprises a formal database, a backup database, a formal database micro-service module, a backup database micro-service module and a java scheduler; the system comprises a formal database micro-service module, a backup database micro-service module and a java scheduler, wherein the formal database micro-service module, the backup database micro-service module and the java scheduler are deployed in the same server; the java scheduler is started at fixed time, the formal database is accessed by calling the formal database micro-service module, the backup database is accessed by calling the backup database micro-service module, changed data are searched in the formal database based on comparison of fields in tables in the backup database and the formal database, and the changed data are updated to the backup database.
Description
Technical Field
The invention relates to a backup technology of a mysql database, in particular to a system and a method for automatically backing up the mysql database.
Background
A regular project production environment often only has the DBA (database administrator) read and write rights to the mysql database, while developers generally only have read-only rights. When the operator and the financial staff need to check the data, the DBA needs to lead out all the data in the mysql database, and then the developer leads the data into the local database, so that the target data is inquired out through the sql statement and the excel table is exported to be provided for the operator and the financial staff.
However, as the amount of traffic increases, the amount of data also increases sharply, and when data needs to be checked, the operation of importing the data and importing the data into the local database takes a lot of time, resulting in low work efficiency.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the system and the method for automatically backing up the mysql database are provided, and the problem that in the prior art, when data needs to be checked, the data needs to be exported from the mysql database and then imported into a local database, a large amount of time is occupied, and the working efficiency is low is solved.
The technical scheme adopted by the invention for solving the technical problems is as follows:
a system for automatically backing up a mysql database, comprising: the system comprises a formal database, a backup database, a formal database micro-service module, a backup database micro-service module and a java scheduler; the system comprises a formal database micro-service module, a backup database micro-service module and a java dispatcher, wherein the formal database micro-service module, the backup database micro-service module and the java dispatcher are deployed in the same server;
the formal database is a mysql database used in project engineering;
the backup database is used for backing up data in the mysql database used in the project engineering, the backup database and the formal database have the same tables and fields, and each table contains the fields: an automatic increment key id, updating time and a logic deletion zone bit;
the formal database micro-service module is connected with a formal database;
the backup database micro-service module is connected with a backup database;
the java scheduler is started at regular time and is used for accessing the formal database by calling the formal database micro-service module, accessing the backup database by calling the backup database micro-service module, searching changed data in the formal database based on comparison of fields in tables in the backup database and the formal database, and updating the changed data to the backup database.
As a further optimization, the varying data includes: new, changed and deleted data.
The data in the backup database and the data in the formal database can be kept consistent by searching and backing up the newly added, changed and deleted data.
As a further optimization, the searching for the changed data in the formal database based on the comparison of the fields in the tables in the backup database and the formal database, and updating the changed data to the backup database specifically includes:
acquiring the id of the last piece of data in a table in a backup database, comparing the id with the ids of all data in the table in a formal database, wherein all data with the id larger than the id in the table in the formal database are newly added data, and inserting the newly added data into a corresponding table of the backup database;
acquiring the id of the last data in the table in the backup database, comparing the id with the ids of all data in the table in the formal database, wherein all the ids in the table in the formal database are less than or equal to the id, the updating time is between the starting time of the java scheduler and the current time, the data with the logical deletion flag bit of 0 is updated, and the updated data is updated to the corresponding table in the backup database;
searching the table in the formal database for the updating time between the starting time of the java scheduler and the current time, taking the data with the logical deletion flag bit of 1 as deleted data, taking the logical deletion flag bit of the corresponding data as 1 in the backup database, and updating the updating time field to be the same as that of the formal database.
The changed data can be quickly searched through the comparison of the fields, so that the backup efficiency is improved.
As further optimization, the formal database micro-service module and the backup database micro-service module adopt restful interfaces and are only open to the java scheduler.
The restful interface is only opened to the java scheduler and is not opened to the outside, so that the data security in the database can be ensured, and the token security mechanism is not required to be adopted for calling the interface.
In addition, the invention also provides a method for automatically backing up the mysql database, which is applied to the system and comprises the following steps:
the java scheduler is started at fixed time, the formal database is accessed by calling the formal database micro-service module, the backup database is accessed by calling the backup database micro-service module, changed data are searched in the formal database based on comparison of fields in tables in the backup database and the formal database, and the changed data are updated to the backup database.
As a further optimization, the timing of the timed start of the java scheduler is determined according to the demand and the traffic volume.
And determining the time for the java scheduler to start regularly according to the demand and the traffic so as to meet the backup demand.
As a further optimization, the varying data includes: new, changed and deleted data.
The data in the backup database and the data in the formal database can be kept consistent by searching and backing up the newly added, changed and deleted data.
As a further optimization, the searching for the changed data in the formal database based on the comparison of the fields in the tables in the backup database and the formal database, and updating the changed data to the backup database specifically includes:
acquiring the id of the last piece of data in a table in a backup database, comparing the id with the ids of all data in the table in a formal database, wherein all data with the id larger than the id in the table in the formal database are newly added data, and inserting the newly added data into a corresponding table of the backup database;
acquiring the id of the last data in the table in the backup database, comparing the id with the ids of all data in the table in the formal database, wherein all the ids in the table in the formal database are less than or equal to the id, the updating time is between the starting time of the java scheduler and the current time, the data with the logical deletion flag bit of 0 is updated, and the updated data is updated to the corresponding table in the backup database;
searching the table in the formal database for the updating time between the starting time of the java scheduler and the current time, taking the data with the logical deletion flag bit of 1 as deleted data, taking the logical deletion flag bit of the corresponding data as 1 in the backup database, and updating the updating time field to be the same as that of the formal database.
The changed data can be quickly searched through the comparison of the fields, so that the backup efficiency is improved.
The invention has the beneficial effects that:
the method comprises the steps that a java scheduler is started regularly, two micro-services which are respectively connected with a formal database and a backup database are called, data which are changed in sending are obtained from the formal database and are backed up to the backup database; the backup is carried out automatically at regular time, so that links of exporting data from the mysql database used in project engineering and importing the data into a local database when the data needs to be checked are omitted, the working efficiency can be improved, and the correctness of the data is ensured because the data of the formal database is not modified.
Drawings
FIG. 1 is a block diagram of a system for automatically backing up a mysql database according to the present invention;
FIG. 2 is a flowchart illustrating backup of newly added data according to an embodiment;
FIG. 3 is a flowchart of backup of changed data in an embodiment;
fig. 4 is a flowchart of backup of deleted data in the embodiment.
Detailed Description
The invention aims to provide a system and a method for automatically backing up a mysql database, which solve the problem that the work efficiency is low because a large amount of time is occupied because data is firstly exported from the mysql database and then imported into a local database when the data needs to be checked in the traditional technology. The core idea is as follows: creating two databases with the same table and field, wherein one database is used as a formal database used by project engineering, and the other database is a backup database for carrying out data backup on the formal database; creating two micro services for connecting a formal database and a backup database, calling the two micro services by starting a java scheduler at regular time, acquiring and sending changed data from the formal database, and backing up the changed data to the backup database.
As shown in fig. 1, the system for automatically backing up mysql database in the present invention includes: the system comprises a formal database, a backup database, a formal database micro-service module, a backup database micro-service module and a java scheduler; the system comprises a formal database micro-service module, a backup database micro-service module and a java scheduler, wherein the formal database micro-service module, the backup database micro-service module and the java scheduler are deployed in the same server;
the formal database is a mysql database used in project engineering;
the backup database is used for backing up data in the mysql database used in the project engineering and has the same tables and fields as the formal database;
the formal database micro-service module is connected with a formal database;
the backup database micro-service module is connected with a backup database;
the java scheduler is started at regular time and is used for accessing the formal database by calling the formal database micro-service module, accessing the backup database by calling the backup database micro-service module, searching changed data in the formal database based on comparison of fields in tables in the backup database and the formal database, and updating the changed data to the backup database.
In the concrete implementation, the tables and the fields of the two databases are completely the same, so that the consistency of the data in the backup database and the data in the formal database can be ensured; when tables are built, each table must contain the following fields:
1. the self-added primary key id can quickly find out newly added data by comparing the id in the two side tables;
2. updating the time field updateTime, wherein when the project updates the data of the formal database, the time field needs to be updated simultaneously, so that the updated data can be conveniently and quickly found out;
3. the flag ifDel of the logical deletion is that the logical deletion field defaults to 0, when the project engineering deletes the formal database data (not physical deletion but logical deletion), the deletion flag position is set to 1, and the update time field needs to be updated, so that when the deleted data is searched, only the data with the deletion flag position of 1 needs to be found, and the method is fast and effective.
The java scheduler is a java project, and the framework is a springMvc framework. The timer scheduled is started at regular intervals (the starting time is determined according to the data volume of the project), and an interface provided by the micro service is called. The Java dispatcher is equivalent to a transfer station and is connected with databases at two sides, and micro-services are called to enable changed data in a formal database to be found out and updated to a backup database, and meanwhile, the Java dispatcher is also a source for initiating the whole process.
The formal database micro-service module and the backup database micro-service module are two spring boot projects, one connected database is a formal database of items, and the function of the connected database is mainly to find out changed data in the formal database; one connected database is a backup database, and the main function of the connected database is to update changed data in the formal database to the backup database. The java scheduler and the micro service are required to be deployed in a server and exist in the same network segment, so that an interface provided by the micro service can be called by the java scheduler; that is, the micro service operates by providing an interface for the java scheduler, and the interface cannot be opened to the outside and can only provide a service for the java scheduler. Because the interface is java engineering, the interface provided by the micro service is a restful interface. Because the interface is an internal interface, the call of the interface does not need to adopt a token security mechanism. The two micro services are connected through a java scheduler project, so that data transmission from one database to the other is realized. The two microservice projects are equivalent to specific operators in the process, and the changed data in the formal database is searched and updated to the backup database.
Example (b):
since data changes typically include: the embodiment will explain the backup processes of these three data changes respectively:
and (3) newly-added backup of data: as shown in fig. 2, firstly, a java scheduler invokes a backup database micro-service to find out that id of the last piece of data of a table tab is a, then invokes a formal database micro-service to find out all data in the table with id greater than a, which is data added by the table tab in the period of time, and finally invokes the backup database micro-service to insert the newly added data into a backup database table tab, thereby realizing the update of the table tab data.
Backup of update data: as shown in fig. 3, first, the java scheduler acquires the current time, then acquires the time of the last startup of the java scheduler by subtracting the interval time of the timer startup from the current time, then the scheduler calls the backup data microserver to acquire the id of the last piece of data in the table tab as I1, then the scheduler calls the formal database microserver to acquire the data with id less than or equal to I1 in the table tab, the update time between the last startup time and the current time, and the delete flag bit as 0 (indicating that the data is not logically deleted), so that the data updated in the table tab at this time is found, and finally the timer calls the backup database microserver to update the updated data into the backup database table tab.
And (3) backup of deleted data: the search for deletion data corresponds to the specific update data. As shown in fig. 4, the scheduler still obtains the current time, subtracts the timer start interval time period to obtain the last start time, then calls the formal database microservice to find out the data with the update time between the last start time and the current time in the table tab and the delete flag bit of 1 (indicating that logical deletion is performed on the data), thereby finding out the deleted data, then calls the microservice of the backup database, sets the delete flag bit of the data in the backup database to 1, and updates the update time field to be the same as the formal database.
Claims (7)
1. A system for automatically backing up mysql databases, characterized in that,
the method comprises the following steps: the system comprises a formal database, a backup database, a formal database micro-service module, a backup database micro-service module and a java scheduler; the system comprises a formal database micro-service module, a backup database micro-service module and a java scheduler, wherein the formal database micro-service module, the backup database micro-service module and the java scheduler are deployed in the same server and exist in the same network segment; the formal database micro-service module and the backup database micro-service module are connected through a java scheduler in an engineering way; the formal database micro-service module and the backup database micro-service module adopt restful interfaces and are only open to the java scheduler;
the formal database is a mysql database used in project engineering;
the backup database is used for backing up data in the mysql database used by the project engineering, the backup database and the formal database have the same tables and fields, and each table contains fields: an automatic increment key id, updating time and a logic deletion zone bit;
the formal database micro-service module is connected with a formal database;
the backup database micro-service module is connected with a backup database;
the java scheduler is started at regular time and is used for accessing the formal database by calling the interface provided by the formal database micro-service module, accessing the backup database by calling the interface provided by the backup database micro-service module, searching changed data in the formal database based on comparison of fields in tables in the backup database and the formal database, and updating the changed data to the backup database.
2. The system for automatically backing up a mysql database as claimed in claim 1,
the changed data includes: new, changed and deleted data.
3. The system for automatically backing up a mysql database as claimed in claim 2,
the searching for the changed data in the formal database based on the comparison of the fields in the tables in the backup database and the formal database, and updating the changed data to the backup database specifically includes:
acquiring the id of the last piece of data in a table in a backup database, comparing the id with the id of each piece of data in a table in a formal database, wherein all the data with the id larger than the id in the table in the formal database are newly added data, and inserting the newly added data into a corresponding table of the backup database;
acquiring the id of the last data in the table in the backup database, comparing the id with the ids of all data in the table in the formal database, wherein all the ids in the table in the formal database are less than or equal to the id, the updating time is between the starting time of the java scheduler and the current time, the data with the logical deletion flag bit of 0 is updated, and the updated data is updated to the corresponding table in the backup database;
searching for the data with the update time between the starting time of the java scheduler and the current time in the table in the formal database, wherein the data with the logical deletion flag bit of 1 is deleted, setting the logical deletion flag bit of the corresponding data to be 1 in the backup database, and updating the update time field to be the same as the formal database.
4. A method for automatically backing up mysql database, applied in a system according to any of claims 1-3, comprising:
the java scheduler is started at fixed time, the formal database is accessed by calling the formal database micro-service module, the backup database is accessed by calling the backup database micro-service module, changed data are searched in the formal database based on comparison of fields in tables in the backup database and the formal database, and the changed data are updated to the backup database.
5. The method of automatically backing up a mysql database as claimed in claim 4,
the timing of the java scheduler is determined according to the requirement and the traffic volume.
6. The method of automatically backing up a mysql database as claimed in claim 4,
the changed data includes: new, changed and deleted data.
7. The method of automatically backing up a mysql database as claimed in claim 6,
the searching for the changed data in the formal database based on the comparison of the fields in the tables in the backup database and the formal database, and updating the changed data to the backup database specifically includes:
acquiring the id of the last piece of data in a table in a backup database, comparing the id with the ids of all data in the table in a formal database, wherein all data with the id larger than the id in the table in the formal database are newly added data, and inserting the newly added data into a corresponding table of the backup database;
acquiring the id of the last data in the table in the backup database, comparing the id with the ids of all data in the table in the formal database, wherein all the ids in the table in the formal database are less than or equal to the id, the updating time is between the starting time of the java scheduler and the current time, the data with the logical deletion flag bit of 0 is updated, and the updated data is updated to the corresponding table in the backup database;
searching the table in the formal database for the updating time between the starting time of the java scheduler and the current time, taking the data with the logical deletion flag bit of 1 as deleted data, taking the logical deletion flag bit of the corresponding data as 1 in the backup database, and updating the updating time field to be the same as that of the formal database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910516092.1A CN110209534B (en) | 2019-06-14 | 2019-06-14 | System and method for automatically backing up mysql database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910516092.1A CN110209534B (en) | 2019-06-14 | 2019-06-14 | System and method for automatically backing up mysql database |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110209534A CN110209534A (en) | 2019-09-06 |
| CN110209534B true CN110209534B (en) | 2022-09-16 |
Family
ID=67792732
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910516092.1A Active CN110209534B (en) | 2019-06-14 | 2019-06-14 | System and method for automatically backing up mysql database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110209534B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112364103B (en) * | 2020-12-08 | 2022-03-01 | 四川长虹电器股份有限公司 | Data synchronization method based on relational database master-slave asynchronous replication architecture |
| CN115510166A (en) * | 2022-11-23 | 2022-12-23 | 云账户技术(天津)有限公司 | Data synchronization service method and device, remote platform and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105677516A (en) * | 2016-01-07 | 2016-06-15 | 成都市思叠科技有限公司 | Method for efficient and reliable backup recovery in calculation approach storage cloud platform |
| CN108932588A (en) * | 2018-06-29 | 2018-12-04 | 华中科技大学 | A kind of the GROUP OF HYDROPOWER STATIONS Optimal Scheduling and method of front and back end separation |
| CN109144785A (en) * | 2018-08-27 | 2019-01-04 | 北京百度网讯科技有限公司 | Method and apparatus for Backup Data |
| CN109542639A (en) * | 2018-11-06 | 2019-03-29 | 用友网络科技股份有限公司 | A kind of processing method, processing unit for ensureing micro services and calling data consistency |
| CN109582695A (en) * | 2018-12-04 | 2019-04-05 | 用友网络科技股份有限公司 | Data general-purpose querying method and inquiry system under a kind of micro services framework |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105488389B (en) * | 2014-12-08 | 2018-05-08 | 哈尔滨安天科技股份有限公司 | A kind of renewal in honeypot data storehouse and restoring method and system |
| CA3040488C (en) * | 2015-01-23 | 2021-11-02 | Servicenow, Inc. | Distributed computing system with resource managed database cloning |
| CN104615759A (en) * | 2015-02-13 | 2015-05-13 | 厦门雅迅网络股份有限公司 | Data synchronization method for different business system platforms |
| CN105701218B (en) * | 2016-01-14 | 2019-05-07 | 四川长虹电器股份有限公司 | Realize that different terminals carry out the synchronous method of data on the database |
| CN106446243A (en) * | 2016-10-10 | 2017-02-22 | 山东浪潮云服务信息科技有限公司 | Data integration structure of relational database |
| US10394663B2 (en) * | 2016-12-16 | 2019-08-27 | Red Hat, Inc. | Low impact snapshot database protection in a micro-service environment |
| CN107247639A (en) * | 2017-05-03 | 2017-10-13 | 上海动联信息技术股份有限公司 | A kind of efficient backup method of mysql databases |
| CN107577780A (en) * | 2017-09-13 | 2018-01-12 | 郑州云海信息技术有限公司 | A kind of data center's cloud resource synchronous method and device |
| US20200349172A1 (en) * | 2019-04-30 | 2020-11-05 | Microsoft Technology Licensing, Llc | Managing code and data in multi-cluster environments |
-
2019
- 2019-06-14 CN CN201910516092.1A patent/CN110209534B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105677516A (en) * | 2016-01-07 | 2016-06-15 | 成都市思叠科技有限公司 | Method for efficient and reliable backup recovery in calculation approach storage cloud platform |
| CN108932588A (en) * | 2018-06-29 | 2018-12-04 | 华中科技大学 | A kind of the GROUP OF HYDROPOWER STATIONS Optimal Scheduling and method of front and back end separation |
| CN109144785A (en) * | 2018-08-27 | 2019-01-04 | 北京百度网讯科技有限公司 | Method and apparatus for Backup Data |
| CN109542639A (en) * | 2018-11-06 | 2019-03-29 | 用友网络科技股份有限公司 | A kind of processing method, processing unit for ensureing micro services and calling data consistency |
| CN109582695A (en) * | 2018-12-04 | 2019-04-05 | 用友网络科技股份有限公司 | Data general-purpose querying method and inquiry system under a kind of micro services framework |
Non-Patent Citations (4)
| Title |
|---|
| PostgreSQL service with backup and recovery for cloud foundry;A. Kozmirchuk等;《2016 International FRUCT Conference on Intelligence, Social Media and Web (ISMW FRUCT)》;20161013;第1-6页 * |
| 基于Docker的数据库微服务系统设计与实现;吴坤安等;《国外电子测量技术》;20171215;第36卷(第12期);第57-62页 * |
| 基于SOA技术架构的多并发异构业务系统中台技术设计;沈进波;《电子技术与软件工程》;20190428(第08期);第168-171页 * |
| 微服务之数据同步Porter;科创人;《https://blog.csdn.net/heishaovvv/article/details/87859552》;20190221;第1-9页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110209534A (en) | 2019-09-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108228817B (en) | Data processing method, device and system | |
| CN107688500B (en) | Distributed task processing method, device, system and equipment | |
| CN108228814B (en) | Data synchronization method and device | |
| CN108427684B (en) | Data query method and device and computing equipment | |
| CN109857724B (en) | Method and equipment for supporting various databases based on block chain | |
| CN108984639B (en) | Data processing method and device for server cluster | |
| US20080162587A1 (en) | Server synchronization for maintenance activities | |
| CN109086382B (en) | Data synchronization method, device, equipment and storage medium | |
| CN111522631A (en) | Distributed transaction processing method, device, server and medium | |
| CN108108431B (en) | Data synchronization method and system | |
| CN110209534B (en) | System and method for automatically backing up mysql database | |
| US20150006485A1 (en) | High Scalability Data Management Techniques for Representing, Editing, and Accessing Data | |
| CN105224527A (en) | Be applicable to the general ETL method of multiple object table update mode | |
| CN109634975B (en) | Data synchronization method and device, electronic equipment and computer readable storage medium | |
| CN114185991A (en) | Method and related device for realizing data synchronization based on distributed database | |
| CN112395307A (en) | Statement execution method, statement execution device, server and storage medium | |
| CN111046106A (en) | Cache data synchronization method, device, equipment and medium | |
| CN107291938B (en) | Order inquiry system and method | |
| CN107391539B (en) | Transaction processing method, server and storage medium | |
| CN108664499B (en) | Data storage method, device and equipment | |
| EP3082050A1 (en) | Mass data fusion storage method and system | |
| CN114691307A (en) | Transaction processing method and computer system | |
| CN111797166A (en) | Quasi-real-time resume data synchronization method and device, electronic equipment and medium | |
| CN113448939A (en) | Data archiving and storing method and device and storage medium | |
| CN111090648A (en) | Relational database data synchronization conflict resolution method |
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 |