CN106599061B - SQLite-based embedded database synchronization method - Google Patents
SQLite-based embedded database synchronization method Download PDFInfo
- Publication number
- CN106599061B CN106599061B CN201611025714.3A CN201611025714A CN106599061B CN 106599061 B CN106599061 B CN 106599061B CN 201611025714 A CN201611025714 A CN 201611025714A CN 106599061 B CN106599061 B CN 106599061B
- Authority
- CN
- China
- Prior art keywords
- node
- master node
- record
- slave node
- slave
- 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
- 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
- G06F16/2365—Ensuring data consistency and integrity
-
- 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
- G06F16/2358—Change logging, detection, and notification
-
- 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/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
Abstract
The invention discloses an SQLite-based embedded database synchronization method which comprises three stages of system initialization, system starting and incremental synchronization. The invention is established on the database of the equipment, and the whole process does not need to additionally add equipment specially used for processing synchronous affairs, thereby saving the cost and conforming to the characteristics of an embedded system. Meanwhile, the database used by the method is SQLite, so that the method has the advantages of less occupied resources, good performance and no management cost, meets the requirement of cost control of the embedded equipment, and ensures the reliability and stability of synchronization; data loss caused by network transmission is prevented by means of database operation logs, and synchronous database tables can be flexibly configured according to actual needs.
Description
Technical Field
The invention belongs to the technical field of embedded databases, and particularly relates to a design of an SQLite-based embedded database synchronization method.
Background
In the field of business information systems, information stored and managed on an embedded device is often a part of an entire integrated information system, and the data is often required to be synchronized and interacted with data of the entire information system.
For the synchronization mode, the data synchronization is mainly based on incremental synchronization, that is, the data changed from one database in a period of time is transmitted to another database to achieve the consistency of the databases, and the changed data mainly comprises added data, modified data and deleted data. In this way, if the data in the first two data have a certain difference, the difference cannot be synchronized.
For the embedded information system, if a synchronization server or device is added to the synchronization system to process the synchronized transaction according to the general idea, the cost is inevitably increased; meanwhile, the network environment of the embedded device has unstable factors, and the problem that the data synchronization is not successful due to the network or other factors needs to be solved. In addition, in practical application scenarios, the data of the devices are not necessarily all required to be synchronized, and therefore, the synchronized data should be flexibly configurable.
For embedded databases, there are currently only two relatively mature items that are open source: SQLite and Berkeley DB. Only the SQLite supports SQL (Structured Query Language), which is a lightweight, cross-platform relational database and has the advantages of small occupied resources, good performance and zero management cost. The Berkeley DB is not a relational database system, and relational databases are used in most information systems.
Disclosure of Invention
The invention aims to solve the problems that the existing embedded data synchronization technology is high in cost and not flexible in configuration, and provides an SQLite-based embedded database synchronization method.
The technical scheme of the invention is as follows: the SQLite-based embedded database synchronization method comprises the following steps:
s1, configuring the role of the user' S own device in the synchronous network; in a synchronous system, synchronous equipment is called as a node, the nodes in the system are divided into a master node and a slave node, and the system only has one master node and at least one slave node; if a plurality of slave nodes exist, distinguishing through the configuration node number;
s2, configuring IP addresses for the master node and the slave node on the same network segment, and establishing FTP servers on the master node and the slave node;
s3, establishing a soap server locally by the master node;
s4, master node and slave node, based on the configuration, adding the operation record list needed by the synchronous list on the basis of the existing database structure, and adding the trigger in the database for recording the changed primary key ID in the synchronous list and the change type of the record;
s5, each slave node sends a request to the soap server of the master node to acquire the data of the master node synchronization table;
s6, the master node queues each request according to the sequence, actively packages the synchronous data on the master node into json log files which can be identified by the slave node, and sends the json log files to the FTP server of the slave node which is processed currently;
s7, after receiving the json log file, the slave node analyzes the json log file into an SQL statement and executes the SQL statement to obtain synchronous data on the master node;
s8, the master node and the slave node judge whether the synchronous table is added, deleted or updated, if yes, the step S9 is executed, and if not, the step S10 is executed;
s9, the trigger records the ID and the change type of the change record in the corresponding operation record table;
s10, the master node and the slave node judge whether the operation record table has contents, if yes, the step S11 is executed, otherwise, the step S13 is executed;
s11, the master node and the slave node are processed in the packaged thread, the record is packaged into a json log, and the corresponding record generated by the trigger in the operation record table is deleted;
s12, the master node and the slave node detect that a json log is generated, and then the sending thread sends the json log to the opposite FTP server;
s13, the master node and the slave node detect whether the received json log exists on the FTP server, if yes, the step S14 is executed, and if not, the step S8 is executed again;
s14, analyzing the json log by the analysis thread, starting a database transaction, generating a corresponding SQL statement and executing;
s15, judging whether the SQL statement is executed successfully, if so, entering a step S16, otherwise, entering a step S17;
s16, submitting the transaction and deleting the corresponding json file, and returning to the step S8 for circulation;
s17, rolling back the affairs, returning to the step S8 and circulating.
Further, in step S2, the master node needs to configure the IP addresses of one or more slave nodes, and the slave node only needs to configure the IP address of the master node.
Further, the content of the operation record table record in step S4 includes the ID of the database record and the operation mode of the record, and the operation mode is divided into three types, i.e., addition, deletion, and update.
Further, if the slave node changes the content of the synchronization table because the slave node parses the log sent by the master node in step S9, the slave node will not generate a corresponding operation record because the trigger is deleted first, thereby preventing the master node and the slave node from generating the same synchronization record circularly.
Further, the content of the json log in step S11 includes the name of the database table, the record content, and the operation type that have changed.
Further, the specific process of encapsulating the record into a json log in step S11 is as follows: the master node and the slave node firstly read the ID and the operation type recorded in the synchronous record table, read data from the corresponding synchronous table according to the ID, write the data into a file in a json format and add the operation type; when the operation type is deletion, the record content has only the ID of the record.
Further, the specific rule for the sending thread to send the json log to the peer FTP server in step S12 is as follows: the slave node only sends the slave node to the master node, and the sending threads are sequenced according to the filenames of the json log files and sequentially send the slave node to the FTP server of the master node; and the master node generates a record into json files corresponding to the plurality of slave nodes, and when the record is sent, the master node sends the corresponding json files to the FTP servers of the slave nodes.
Further, step S14 is specifically: and opening a database transaction, analyzing the thread to obtain an operation type, an operation synchronization table and record contents, and generating a corresponding SQL statement, wherein the statement is an SQL statement executed by the opposite side before, and the operation is synchronized by executing the statement.
Further, in step S14, the slave node needs to delete the trigger for recording the synchronization table operation after starting the database transaction, so as to prevent the synchronization record from being recorded by the trigger after the synchronization is performed, and avoid the synchronization of the master node and the slave node in a cycle.
Further, the slave node in step S16 needs to add the deleted corresponding flip-flop again before committing the transaction.
The invention has the beneficial effects that: the invention is established on the database of the equipment, and the whole process does not need to additionally add equipment specially used for processing synchronous affairs, thereby saving the cost and conforming to the characteristics of an embedded system. Meanwhile, the database used by the method is SQLite, so that the method has the advantages of less occupied resources, good performance and no management cost, meets the requirement of cost control of the embedded equipment, and ensures the reliability and stability of synchronization; data loss caused by network transmission is prevented by means of database operation logs, and synchronous database tables can be flexibly configured according to actual needs.
Drawings
FIG. 1 is a flowchart of an SQLite-based embedded database synchronization method provided by the present invention.
Fig. 2 is a schematic diagram of data flow of a database synchronization system according to an embodiment of the present invention.
Detailed Description
The embodiments of the present invention will be further described with reference to the accompanying drawings.
The invention provides an SQLite-based embedded database synchronization method which comprises three stages of system initialization, system starting and incremental synchronization. As shown in fig. 1, each stage specifically includes the following steps:
(1) a system initialization stage:
and S1, configuring the role of the user self equipment in the synchronous network.
The database used by the invention is SQLite, is a lightweight cross-platform relational database, occupies less resources, has good performance and has no management cost. In a database synchronization system, a synchronized device is called a node, the nodes in the system are divided into a master node and a slave node, the system only has one master node and at least one slave node; if a plurality of slave nodes exist, the slave nodes are distinguished through configuration node numbers. Taking a synchronization system with 4 embedded devices as an example, the synchronization system includes a master node and three slave nodes (slave1, slave2, slave3), where the master node and the slave node both represent independent embedded devices, and are connected through a network, each device has a separate database, and data flow between the devices is as shown in fig. 2. For the whole synchronization system, the database of the master serves as a central database, the slave node sends a command to the master after being electrified and started every time to acquire the synchronization data of the database of the master node, and the master node actively sends self synchronization data to the slave node after receiving the command to ensure that the databases of the master and the slave are consistent after being electrified.
S2, configuring IP addresses for the master node and the slave node on the same network segment, and establishing FTP servers on both the master node and the slave node. According to the actual situation, the master node needs to configure the IP addresses of one or more slave nodes, and the slave node only needs to configure the IP address of the master node.
FTP is an english abbreviation of File Transfer Protocol (File Transfer Protocol), and chinese is simply referred to as "File Transfer Protocol" for bidirectional Transfer of control files on the Internet.
S3, the master node establishes a soap server locally for the request command of each slave node.
The soap simple object access protocol is a protocol specification for exchanging data, and is a lightweight, simple, XML (a subset of the standard universal markup language) based protocol designed to exchange structured and solidified information on the WEB.
And S4, the master node and the slave node are configured, based on the existing database structure, to add an operation record table requiring a synchronization table, and add a trigger in the database for recording the changed primary key ID in the synchronization table and the change type of the record, wherein the change type includes addition, deletion and update. The content recorded by the operation record table comprises the ID of the database record and the operation mode of the record, and the operation mode is divided into three modes of addition, deletion and updating.
(2) And (3) a system starting stage:
and S5, after the system is started, each slave node sends a request to the soap server of the master node to acquire the data of the master node synchronization table.
And S6, queuing the requests by the master node according to the sequence, actively packaging the synchronous data on the master node into json log files which can be identified by the slave node, and sending the json log files to the FTP server of the slave node which is processed currently.
json (javascript Object notification) is a lightweight data exchange format that is based on a subset of ECMAScript, in a text format that is completely language independent.
And S7, after receiving the json log file, the slave node analyzes the json log file into an SQL statement and executes the SQL statement to obtain the synchronous data on the master node.
(3) An increment synchronization stage:
and S8, the master node and the slave node judge whether the synchronous table is subjected to operations of addition, deletion or updating, if so, the step S9 is executed, and if not, the step S10 is executed.
S9, the trigger records the ID and the change type of the change occurrence record in the corresponding operation record table.
Particularly, if the slave node changes the content of the synchronization table by analyzing the log sent by the master node, the slave node will not generate the corresponding operation record because the trigger is deleted first, thereby preventing the master node and the slave node from generating the same synchronization record circularly.
And S10, the master node and the slave node judge whether the operation record table has contents, if so, the step S11 is executed, and if not, the step S13 is executed.
And S11, the master node and the slave node are processed in the packaged thread, the records are packaged into json logs, and corresponding records generated by triggers in the operation record table are deleted.
The content of the json log includes the name of the database table that changed, the record content, and the type of operation. The specific process of the step is as follows:
the master node and the slave node firstly read the ID and the operation type recorded in the synchronous record table, read data from the corresponding synchronous table according to the ID, write the data into a json format file, and add the operation type, where convention 1 represents addition (insert), 2 represents update (update), and 3 represents deletion (delete), and particularly, when the operation type is deletion, the record content only has the recorded ID. The number of records processed each time is not more than 50, and the json log generated is prevented from being too large. And deleting the corresponding record in the operation record table once the encapsulation is successful.
In the embodiment of the invention, the file name format of the json log is nodex _ y, wherein x is agreed that a master node is 1, a slave1 is 2, a slave2 is 3, and so on, and y is the number of times of the operation record of the whole synchronization table. Taking an operation record as an example, if the master node configures 2 slave nodes: slave1 and slave2, then the master node will generate two files, node2_1 and node3_1, and if there is another operation record later, will generate node2_2 and node3_ 2. For the slave node, since it only sends to the master node, its file name is node1_ y, and y is the number of times of operation record.
And after detecting that the json log is generated, the S12, the master node and the slave node send the json log to the opposite FTP server by the sending thread.
As shown in step S2, the master node and the slave node are both provided with FTP servers, and are provided with addresses of the FTP servers of the other party. The specific rule for the sending thread to send the json log to the opposite FTP server in this step is as follows:
the slave node only sends the slave node to the master node, and the sending threads are sequenced according to the filenames of the json log files and sequentially send the slave node to the FTP server of the master node. The file name rule of the json log is generated according to the sequence of generating the json file, and the json file is transmitted according to the same rule during transmission, so that the transmitted json file can be generated according to time sequence. In the sending thread, the master node can determine the corresponding FTP server address of the slave node according to the json file name, for example, the node2_2 file is sent to the FTP server of the slave 1. And the master node generates a record into json files corresponding to the plurality of slave nodes, and when the record is sent, the master node sends the corresponding json files to the FTP servers of the slave nodes. When a successful transmission of a json log file is detected, the json log file is deleted.
And S13, the master node and the slave node detect whether the received json log exists on the FTP server, if so, the step S14 is executed, and if not, the step S8 is executed again.
And S14, analyzing the json log by the analysis thread, starting a database transaction, generating a corresponding SQL statement and executing.
The json log is derived from a part which is actively requested by the slave node to be sent by the master node and a part which is sent by the master node according to self change. Once json logs on the FTP server are detected, the analysis thread analyzes the logs on the FTP server, and generates and executes corresponding SQL statements. As shown in step S11, the json log contains the name of the database table, the record content and the operation type, and if the operation type is delete, the record content is only the ID of the record.
After the analysis is started, the database transaction is started, the analysis thread obtains the operation type, the synchronization table of the operation and the record content to generate a corresponding SQL statement, the statement is an SQL statement executed before the other side, and the operation is synchronized after the statement is executed. Particularly for the slave node, after the database transaction is started, the trigger for recording the synchronous table operation is deleted.
S15, judging whether the SQL statement is executed successfully, if so, entering the step S16, otherwise, entering the step S17.
And S16, submitting the transaction and deleting the corresponding json file, and returning to the step S8 for circulation.
Particularly for the slave node, the deleted corresponding flip-flop needs to be re-added before the transaction is committed. Thus, because the trigger for recording the synchronization table operation is deleted in step S14, the trigger is re-added before the transaction is submitted, so that the slave node does not generate json log again when synchronizing the records of the master node, thereby avoiding the master node and the slave node from circularly sending the same record log.
S17, rolling back the affairs, returning to the step S8 and circulating.
It will be appreciated by those of ordinary skill in the art that the embodiments described herein are intended to assist the reader in understanding the principles of the invention and are to be construed as being without limitation to such specifically recited embodiments and examples. Those skilled in the art can make various other specific changes and combinations based on the teachings of the present invention without departing from the spirit of the invention, and these changes and combinations are within the scope of the invention.
Claims (10)
1. The SQLite-based embedded database synchronization method is characterized by comprising the following steps:
s1, configuring the role of the user' S own device in the synchronous network; in a synchronous system, synchronous equipment is called as a node, the nodes in the system are divided into a master node and a slave node, and the system only has one master node and at least one slave node; if a plurality of slave nodes exist, distinguishing through the configuration node number;
s2, configuring IP addresses for the master node and the slave node on the same network segment, and establishing FTP servers on the master node and the slave node;
s3, establishing a soap server locally by the master node;
s4, master node and slave node, based on configuration, adding operation record list needed synchronization list on the basis of existing database structure, and adding trigger in database for recording changed primary key ID and changed type of primary key ID in synchronization list;
s5, each slave node sends a request to the soap server of the master node to acquire the data of the master node synchronization table;
s6, the master node queues each request according to the sequence, actively packages the synchronous data on the master node into json log files which can be identified by the slave node, and sends the json log files to the FTP server of the slave node which is processed currently;
s7, after receiving the json log file, the slave node analyzes the json log file into an SQL statement and executes the SQL statement to obtain synchronous data on the master node;
s8, the master node and the slave node judge whether the synchronous table is added, deleted or updated, if yes, the step S9 is executed, and if not, the step S10 is executed;
s9, the trigger records the ID and the change type of the change record in the corresponding operation record table;
s10, the master node and the slave node judge whether the operation record table has contents, if yes, the step S11 is executed, otherwise, the step S13 is executed;
s11, the master node and the slave node are processed in the packaged thread, the record is packaged into a json log, and the corresponding record generated by the trigger in the operation record table is deleted;
s12, the master node and the slave node detect that a json log is generated, and then the sending thread sends the json log to the opposite FTP server;
s13, the master node and the slave node detect whether the received json log exists on the FTP server, if yes, the step S14 is executed, and if not, the step S8 is executed again;
s14, analyzing the json log by the analysis thread, starting a database transaction, generating a corresponding SQL statement and executing;
s15, judging whether the SQL statement is executed successfully, if so, entering a step S16, otherwise, entering a step S17;
s16, submitting the transaction and deleting the corresponding json file, and returning to the step S8 for circulation;
s17, rolling back the affairs, returning to the step S8 and circulating.
2. The SQLite-based embedded database synchronization method of claim 1, wherein in the step S2, the master node needs to configure the IP addresses of one or more slave nodes, and the slave node only needs to configure the IP address of the master node.
3. The SQLite-based embedded database synchronization method of claim 1, wherein the content of the operation record table record in step S4 comprises ID of the database record and operation mode of the changed primary key ID, and the operation modes are divided into three operation modes, i.e. add, delete and update.
4. The SQLite-based embedded database synchronization method of claim 1, wherein if the slave node changes the contents of the synchronization table due to parsing the log sent by the master node in step S9, the slave node will not generate the corresponding operation record because the trigger is deleted first, thereby preventing the master node and the slave node from generating the same synchronization record circularly.
5. The SQLite-based embedded database synchronization method as recited in claim 1, wherein the content of the json log in the step S11 comprises the name of the database table, the record content and the operation type which are changed.
6. The SQLite-based embedded database synchronization method according to claim 5, wherein the specific process of encapsulating records as json logs in the step S11 is as follows: the master node and the slave node firstly read the ID and the operation type recorded in the synchronous record table, read data from the corresponding synchronous table according to the ID, write the data into a file in a json format and add the operation type; when the operation type is deletion, the record content has only the ID of the record.
7. The SQLite-based embedded database synchronization method according to claim 1, wherein the specific rule that the sending thread sends the json log to the opposite FTP server in the step S12 is as follows: the slave node only sends the slave node to the master node, and the sending threads are sequenced according to the filenames of the json log files and sequentially send the slave node to the FTP server of the master node; and the master node generates a record into json files corresponding to the plurality of slave nodes, and when the record is sent, the master node sends the corresponding json files to the FTP servers of the slave nodes.
8. The SQLite-based embedded database synchronization method according to claim 5, wherein the step S14 specifically comprises: and opening a database transaction, analyzing the thread to obtain an operation type, an operation synchronization table and a record content, and generating a corresponding SQL statement, wherein the statement is an SQL statement executed before the opposite side, and the operation corresponding to the json log is synchronized by executing the statement.
9. The SQLite-based embedded database synchronization method according to claim 8, wherein in the step S14, the slave node needs to delete the trigger for recording the operation of the synchronization table after starting the database transaction, thereby preventing the synchronization record of the operation corresponding to the json log from being recorded by the trigger after the synchronization is performed, and avoiding the synchronization of the master node and the slave node from being circulated and the same record.
10. The SQLite-based embedded database synchronization method of claim 9, wherein the slave node in step S16 needs to re-add the deleted corresponding trigger before committing the transaction.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611025714.3A CN106599061B (en) | 2016-11-16 | 2016-11-16 | SQLite-based embedded database synchronization method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611025714.3A CN106599061B (en) | 2016-11-16 | 2016-11-16 | SQLite-based embedded database synchronization method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106599061A CN106599061A (en) | 2017-04-26 |
| CN106599061B true CN106599061B (en) | 2020-06-30 |
Family
ID=58592367
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611025714.3A Active CN106599061B (en) | 2016-11-16 | 2016-11-16 | SQLite-based embedded database synchronization method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106599061B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107657002A (en) * | 2017-09-20 | 2018-02-02 | 北京九桥同步软件有限公司 | File synchronisation method and device |
| CN107590256A (en) * | 2017-09-20 | 2018-01-16 | 北京九桥同步软件有限公司 | Heterogeneous database synchronization method and device |
| CN108009282A (en) * | 2017-12-22 | 2018-05-08 | 武汉楚鼎信息技术有限公司 | A kind of json data are synchronized to the method and system device of relevant database |
| CN109271450B (en) * | 2018-10-10 | 2020-12-04 | 北京百度网讯科技有限公司 | Database synchronization method, device, server and storage medium |
| CN109542926B (en) * | 2018-11-06 | 2021-04-09 | 北京新唐思创教育科技有限公司 | Block processing method and computer storage medium |
| CN109933630B (en) * | 2019-03-19 | 2021-11-23 | 武汉达梦数据库股份有限公司 | Real-time database data synchronization method and device |
| CN110188118B (en) * | 2019-04-25 | 2021-06-25 | 广州至真信息科技有限公司 | Data synchronization method and device |
| CN110263052B (en) * | 2019-06-25 | 2021-07-20 | 苏宁消费金融有限公司 | Automatic synchronization technology innovation method based on big data Hadoop platform ODS |
| CN110347652B (en) * | 2019-07-12 | 2022-03-18 | 天津凯发电气股份有限公司 | Multi-machine database synchronization realization method for power quality management system |
| CN110704532A (en) * | 2019-09-18 | 2020-01-17 | 南方电网数字电网研究院有限公司 | Method and device for synchronizing data among databases, computer equipment and storage medium |
| CN111522897B (en) * | 2020-05-07 | 2022-07-08 | 福州市勘测院有限公司 | Method for incremental synchronization of spatial data between ArcSDE (android System File) and File GDB (graphics database) |
| CN113220968B (en) * | 2021-05-26 | 2023-03-14 | 西安热工研究院有限公司 | Clustered network crawler-based automatic power technology standard updating system and method |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101751394A (en) * | 2008-12-16 | 2010-06-23 | 青岛海信传媒网络技术有限公司 | Method and system for synchronizing data |
| CN102033889A (en) * | 2009-09-29 | 2011-04-27 | 熊凡凡 | Distributed database parallel processing system |
| CN102262674A (en) * | 2011-08-11 | 2011-11-30 | 大唐移动通信设备有限公司 | Data synchronization method and system for distributed memory database |
| CN102693324A (en) * | 2012-01-09 | 2012-09-26 | 西安电子科技大学 | Distributed database synchronization system, synchronization method and node management method |
| CN102722126A (en) * | 2012-07-13 | 2012-10-10 | 卓璐 | Four-roll plate bending machine control system based on advanced RISC machine (ARM) and Wince |
| CN102982171A (en) * | 2012-12-17 | 2013-03-20 | 山东神思电子技术股份有限公司 | Database synchronization method |
| CN103747091A (en) * | 2014-01-16 | 2014-04-23 | 电信科学技术第一研究所 | Distributed data synchronization system and method for embedded equipment |
| CN105243067A (en) * | 2014-07-07 | 2016-01-13 | 北京明略软件系统有限公司 | Method and apparatus for realizing real-time increment synchronization of data |
-
2016
- 2016-11-16 CN CN201611025714.3A patent/CN106599061B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101751394A (en) * | 2008-12-16 | 2010-06-23 | 青岛海信传媒网络技术有限公司 | Method and system for synchronizing data |
| CN102033889A (en) * | 2009-09-29 | 2011-04-27 | 熊凡凡 | Distributed database parallel processing system |
| CN102262674A (en) * | 2011-08-11 | 2011-11-30 | 大唐移动通信设备有限公司 | Data synchronization method and system for distributed memory database |
| CN102693324A (en) * | 2012-01-09 | 2012-09-26 | 西安电子科技大学 | Distributed database synchronization system, synchronization method and node management method |
| CN102722126A (en) * | 2012-07-13 | 2012-10-10 | 卓璐 | Four-roll plate bending machine control system based on advanced RISC machine (ARM) and Wince |
| CN102982171A (en) * | 2012-12-17 | 2013-03-20 | 山东神思电子技术股份有限公司 | Database synchronization method |
| CN103747091A (en) * | 2014-01-16 | 2014-04-23 | 电信科学技术第一研究所 | Distributed data synchronization system and method for embedded equipment |
| CN105243067A (en) * | 2014-07-07 | 2016-01-13 | 北京明略软件系统有限公司 | Method and apparatus for realizing real-time increment synchronization of data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106599061A (en) | 2017-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106599061B (en) | SQLite-based embedded database synchronization method | |
| US11848871B2 (en) | Network slice management | |
| US9367261B2 (en) | Computer system, data management method and data management program | |
| US20100161551A1 (en) | Selective database replication | |
| CN105740418A (en) | File monitoring and message pushing based real-time synchronization system | |
| US10069941B2 (en) | Scalable event-based notifications | |
| US20150317371A1 (en) | Method, device, and system for peer-to-peer data replication and method, device, and system for master node switching | |
| CN104468299A (en) | Enterprise service bus system based on user rule | |
| JP2020042809A (en) | Technique for interfacing between web service and interface description language (idl)-based remote procedure call (rpc) service and optical communication system implementing the same | |
| WO2016082594A1 (en) | Data update processing method and apparatus | |
| US11507591B2 (en) | Methods, systems, and computer readable mediums for command engine execution | |
| CN105610917B (en) | Method and system for realizing synchronous data repair in system | |
| CN109710223B (en) | API gateway hot plug system based on distributed KV storage system | |
| CN106547790B (en) | Relational database service system | |
| CN113204600B (en) | InfluxDB distributed clustering method based on table routing fragmentation engine | |
| CN113067860B (en) | Method, apparatus, device, medium and product for synchronizing information | |
| US10545667B1 (en) | Dynamic data partitioning for stateless request routing | |
| KR102226915B1 (en) | Method, apparatus and computer program for operating the flow rules database in software defined network | |
| US20190387054A1 (en) | Method, electronic device and computer program product for searching for node | |
| US10860580B2 (en) | Information processing device, method, and medium | |
| CN109413118B (en) | Method, device, storage medium and program product for realizing session synchronization | |
| US11526516B2 (en) | Method, apparatus, device and storage medium for generating and processing a distributed graph database | |
| KR20190051627A (en) | Operation layer improving apparatus and method of network configuration protocol in network management system | |
| US10303787B2 (en) | Forgetting items with knowledge based synchronization | |
| US20230214520A1 (en) | Systems, methods and computer program products for messaging in a heterogeneous environment |
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 |