CN106599061A - SQLite-based embedded database synchronization method - Google Patents
SQLite-based embedded database synchronization method Download PDFInfo
- Publication number
- CN106599061A CN106599061A CN201611025714.3A CN201611025714A CN106599061A CN 106599061 A CN106599061 A CN 106599061A CN 201611025714 A CN201611025714 A CN 201611025714A CN 106599061 A CN106599061 A CN 106599061A
- Authority
- CN
- China
- Prior art keywords
- nodes
- master
- json
- slave
- record
- 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.)
- Granted
Links
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
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)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a SQLite-based embedded database synchronization method. The method comprises three stages of system initialization, system startup and increment synchronization. The method is established in a database of a device; a special device for handling a synchronization business does not need to be additionally added in the whole process, so that the cost is reduced; and the characteristics of an embedded system are met. Meanwhile, the database used in the method is SQLite, occupies few resources, is good in performance and free from management cost, meets cost control demand of an embedded device, and ensures synchronization reliability and stability; and the data loss caused by network transmission is prevented through database operation logs, and synchronized database tables can be flexibly configured according to actual needs.
Description
Technical field
The invention belongs to Embedded Database Technology field, and in particular to a kind of embedded database based on SQLite is same
The design of one step process.
Background technology
In commercial information system field, the information for storing and managing on embedded device is all often whole integrated information
A part for system, and these data are often required for synchronizing and interacting with the data of whole information system, with embedded
The development of formula technology and extensively application, embedded data is synchronous and interaction becomes more and more important.
For the method for synchronization, current data syn-chronization is mainly based upon increment and synchronizes, i.e., in a period of time one
The data transfer of individual data base's change reaches data base unanimously to another data base, and the data of change mainly have the number of increase
According to, the data of modification, the data of deletion.In this manner, if the data most started in two data possess certain difference
Away from, then this operative gap cannot be by synchronization.
For embedded information system, if according to common thinking, one is individually added in synchronization system together
Walk server or equipment to process synchronous affairs, then the increase of cost will necessarily be caused；Meanwhile, the network of embedded device
There are the factors of instability in environment, need to solve to cause synchrodata not have successful problem by network or other factors.This
Outward, in practical application scene, the data of equipment be not necessarily it is all be required for synchronization, therefore, synchronous data should can be
Flexible configuration.
For embedded database, the project of only two comparative maturities increased income at present：SQLite and
Berkeley DB.Wherein, only SQLite supports SQL (Structured Query Language, SQL),
It is a lightweight, cross-platform relevant database, and few, functional and zero management cost with resource is taken
Advantage.Berkeley DB are not a system Rs, and relational data is all used in most information system
Storehouse.
The content of the invention
The invention aims to it is relatively costly to solve existing embedded data simultaneous techniquess, and configure underaction
Problem, it is proposed that a kind of embedded database synchronous method based on SQLite.
The technical scheme is that：Based on the embedded database synchronous method of SQLite, comprise the following steps：
S1, configuration role of user's equipment of itself in synchronizing network；In synchronization system, synchronous equipment is referred to as section
Point, the node in system are divided into two kinds of master nodes and slave nodes, can only have a master node, at least in system
There is a slave node；If multiple slave nodes, then distinguished by configuration section period；
S2, on the same network segment be master nodes and slave nodes configuration IP address, and in master nodes and
Ftp server is set up on slave nodes all；
S3, master node is in a locally created soap server；
, according to configuration, on the basis of available data library structure, increasing needs together for S4, master node and slave nodes
The operation sheet of step table, and increases trigger in data base, for the major key ID that changes in recording synchronism table and this
The variation type of record；
S5, each slave node send request to the soap servers of master nodes, and acquisition request master node is same
The data of step table；
S6, master node makees queuing process to each request according to sequencing, and the synchronization on master nodes
Data are actively encapsulated as the json journal files that slave nodes are capable of identify that, are sent to the currently processed slave nodes for arriving
On ftp server；
S7, receive json journal files after, slave nodes are resolved to SQL statement and are performed, obtain master nodes
On synchrodata；
S8, master node and slave nodes judge the operation whether synchronous meter increases, deletes or update, if
Step S9 is entered then, otherwise into step S10；
S9, trigger record the ID and change type for occurring to change record in corresponding operation sheet；
Whether S10, master node and slave nodes have content in judging operation sheet, and step is entered if having
S11, otherwise into step S13；
S11, master node and slave nodes are processed in the thread of encapsulation, and record is encapsulated as json daily records,
And the corresponding record that trigger is produced in deletion action log；
S12, master node and slave nodal tests send thread to other side's ftp server to generating after json daily records
Send json daily records；
Whether the json daily record that receive is had on S13, master node and slave nodal test ftp servers, if then
Into step S14, otherwise return to step S8；
S14, parsing thread parsing json daily records, turn-on data storehouse affairs generate corresponding SQL statement and perform；
S15, judge whether SQL statement runs succeeded, if then entering step S16, otherwise into step S17；
S16, submit affairs to and delete corresponding json files, return to step S8 is circulated；
S17, transaction rollback, return to step S8 are circulated.
Further, in step S2, master nodes need the IP address for configuring one or more slave node,
Slave nodes then only need to the IP address for configuring master nodes.
Further, in step S4, the content of operation note table record includes the ID's and the record of data-base recording
Mode of operation, mode of operation are divided into increase, delete and update three kinds.
Further, if slave nodes change synchronization because of the daily record of parsing master node transmissions in step S9
The content of table, then slave nodes will not generate corresponding operation note due to first deleting trigger, so as to prevent
Master nodes and the same synchronous recording of generation of slave nodes circulation.
Further, the content of json daily records includes changing in step S11 database table title, recorded content with
And action type.
Further, in step S11 the detailed process that record is encapsulated as json daily records it is：Master nodes and slave
ID and action type that node is recorded in first reading synchronous recording table, in correspondence synchronous meter read data according to ID, are written to
In the file of json forms, and add action type；When action type is to delete, the ID that recorded content is only recorded.
Further, thread is sent in step S12 to the specific rules that other side's ftp server sends json daily records is：
Slave nodes are simply sent to master nodes, send thread and sort according to the filename of json journal files, are sent to successively
The ftp server of master nodes；Master nodes generate the corresponding json files of multiple slave nodes a record,
During transmission, master nodes are sent to corresponding json files the ftp server of each slave node.
Further, step S14 is specially：Turn-on data storehouse affairs, parse thread and obtain action type, the synchronization of operation
Corresponding SQL statement is generated after table and recorded content, the SQL statement that the sentence was performed before being exactly other side is performed
The sentence, the operation have just obtained synchronization.
Further, in step S14, slave nodes need deletion record synchronization table handling after the affairs of turn-on data storehouse
Trigger, after preventing from performing synchronization, the synchronous recording is again recorded by trigger, it is to avoid master nodes and slave nodes are followed
The same record of synchronization of ring.
Further, in step S16, slave nodes needed the corresponding trigger deleted to add before affairs are submitted to again
Add.
The invention has the beneficial effects as follows：The present invention is set up on the data base of equipment, and whole process additionally need not increase
The equipment of special disposal synchronized transaction, has saved cost, the characteristics of meet embedded system.Meanwhile, the data that the present invention is used
Storehouse is SQLite, and it is few, functional and without management cost to take resource, meets the demand of embedded device cost control, and protects
The reliability and stability of synchronization is demonstrate,proved；Prevented by way of database manipulation daily record because the data that network transmission is caused are lost
Lose, synchronous database table can carry out flexible configuration according to the actual needs.
Description of the drawings
The embedded database synchronous method flow chart based on SQLite that Fig. 1 is provided for the present invention.
Database synchronous system data flow schematic diagrams of the Fig. 2 for the embodiment of the present invention.
Specific embodiment
Below in conjunction with the accompanying drawings embodiments of the invention are further described.
The invention provides a kind of embedded database synchronous method based on SQLite, including system initialization, system
Start and increment synchronization three phases.As shown in figure 1, each stage specifically includes following steps：
(1) system initialisation phase：
S1, configuration role of user's equipment of itself in synchronizing network.
The data base that the present invention is used is SQLite, and it is a lightweight, cross-platform relevant database, and is accounted for
With resource it is few, functional, without management cost.In database synchronous system, synchronous equipment is referred to as node, in system
Node is divided into two kinds of master nodes and slave nodes, can only have a master node, at least one slave in system
Node；If multiple slave nodes, then distinguished by configuration section period.Synchronization system with 4 embedded devices is
Example, just includes a master node and three slave nodes (slave1, slave2, slave3), wherein master nodes with
Slave nodes all represent independent embedded device, are attached by network between them, and each equipment has one individually
Data base, between them, data flow is as shown in Figure 2.For whole synchronization system, the data base of master is used as center
Data base, sends to master nodes after each electrifying startup of slave nodes and orders, obtain the synchronization of master node databases
Data, after master nodes receive order, actively send itself synchrodata and give slave nodes, it is ensured that both numbers after upper electricity
It is consistent according to storehouse.
S2, on the same network segment be master nodes and slave nodes configuration IP address, and in master nodes and
Ftp server is set up on slave nodes all.According to practical situation, master nodes need to configure one or more slave section
The IP address of point, slave nodes then only need to the IP address for configuring master nodes.
FTP is the English abbreviation of File Transfer Protocol (file transfer protocol (FTP)), and Chinese is referred to as " text biography association
View ", for the transmitted in both directions of the control file on Internet.
S3, master node in a locally created soap server, for the request command of each slave node.
Soap Simple Object Access Protocols are a kind of protocol specifications of exchange data, be a kind of light weight, it is simple, be based on
The agreement of XML (a subset under standard generalized markup language), it is designed to the letter that structuring and solidification are exchanged on WEB
Breath.
, according to configuration, on the basis of available data library structure, increasing needs together for S4, master node and slave nodes
The operation sheet of step table, and increases trigger in data base, for the major key ID that changes in recording synchronism table and this
The variation type of record, changing type has increase, deletes and update.The content of operation note table record includes data-base recording
The mode of operation of ID and the record, mode of operation are divided into increase, delete and update three kinds.
(2) system start-up phase：
After S5, system start-up, each slave node sends request, acquisition request to the soap servers of master nodes
The data of master node synchronous meters.
S6, master node makees queuing process to each request according to sequencing, and the synchronization on master nodes
Data are actively encapsulated as the json journal files that slave nodes are capable of identify that, are sent to the currently processed slave nodes for arriving
On ftp server.
Json (JavaScript Object Notation) is a kind of data interchange format of lightweight, and it is to be based on
The a subset of ECMAScript, using the text formatting for being totally independent of language.
S7, receive json journal files after, slave nodes are resolved to SQL statement and are performed, obtain master nodes
On synchrodata.
(3) the increment synchronization stage：
S8, master node and slave nodes judge the operation whether synchronous meter increases, deletes or update, if
Step S9 is entered then, otherwise into step S10.
S9, trigger record the ID and change type for occurring to change record in corresponding operation sheet.
Special situation is, if slave nodes change synchronous meter because of the daily record of parsing master node transmissions
Content, then slave nodes will not generate corresponding operation note due to first deleting trigger, so as to prevent master
Node and the same synchronous recording of generation of slave nodes circulation.
Whether S10, master node and slave nodes have content in judging operation sheet, and step is entered if having
S11, otherwise into step S13.
S11, master node and slave nodes are processed in the thread of encapsulation, and record is encapsulated as json daily records,
And the corresponding record that trigger is produced in deletion action log.
The content of json daily records includes database table title, recorded content and the action type for changing.The step
Detailed process be：
ID and action type that master nodes and slave nodes are recorded in first reading synchronous recording table, according to ID to right
Data are read in answering synchronous meter, is written in the file of json forms, and add action type, agreement 1 is represented and increased
(insert), 2 renewal (update) is represented, (delete) is deleted in 3 representatives, particularly, when action type is to delete, records interior
Hold the ID of only record.Record strip number per treatment is less than 50, prevents the json daily records for generating excessive.It once is packaged into
Work(, with regard to corresponding record in deletion action log.
In the embodiment of the present invention, the file name formats of json daily records are nodex_y, and wherein x is about set to master nodes and is
1, slave1 be 2, slave2 be 3, by that analogy, y is the number of times of whole synchronous meter operation note.With an operation note it is
Example, if master nodes are configured with 2 slave nodes：Slave1 and slave2, then master nodes will generate node2_
1st, two files of node3_1, if having an operation note later again, then node2_2, node3_2 will be generated.For
For slave nodes, as it is simply sent to master nodes, then the number of times of the entitled node1_y of its file, y for operation note.
S12, master node and slave nodal tests send thread to other side's ftp server to generating after json daily records
Send json daily records.
From step S2, master nodes and slave nodes are all configured with ftp server, and are configured with other side FTP
The address of server.Thread is sent in the step then as follows to the specific rules that other side's ftp server sends json daily records：
Slave nodes are simply sent to master nodes, send thread and sort according to the filename of json journal files, successively
It is sent to the ftp server of master nodes.The filename rule of json daily records is generated, it is suitable according to the priority for generating json files
Sequence, also sends according to same rule when sending, it is possible to ensure that the json files for sending are given birth to according to time order and function
Into.Send thread in master nodes according to json filenames it may determine that the corresponding FTP service of other side's slave nodes
Device address, such as, node2_2 files are sent on the ftp server of slave1.Master nodes give birth to a record
Into the corresponding json files of multiple slave nodes, when sending, master nodes are sent to each corresponding json files
The ftp server of slave nodes.Send successfully when a json journal file is detected, this json journal file is just deleted
Remove.
Whether the json daily record that receive is had on S13, master node and slave nodal test ftp servers, if then
Into step S14, otherwise return to step S8.
S14, parsing thread parsing json daily records, turn-on data storehouse affairs generate corresponding SQL statement and perform.
Json daily records are from the part of slave node active requests master node transmission and master nodes according to certainly
Body changes the part for sending.Once detecting, parsing thread will parse daily record above,
Generate corresponding SQL statement and perform.From step S11, contain in json daily records database table title, recorded content and
Action type, if action type is to delete, then the ID that recorded content is just only recorded.
After parsing starts, turn-on data storehouse affairs parse thread and obtain in action type, the synchronous meter of operation and record
Corresponding SQL statement is generated after appearance, the SQL statement that the sentence was performed before being exactly other side performs the sentence, this
Operation has just obtained synchronization.Particularly for slave nodes, after the affairs of turn-on data storehouse, deletion record synchronous meter
The trigger of operation.
S15, judge whether SQL statement runs succeeded, if then entering step S16, otherwise into step S17.
S16, submit affairs to and delete corresponding json files, return to step S8 is circulated.
Particularly for slave nodes, needed the corresponding trigger deleted to add again before affairs are submitted to
On.It is so as the trigger of recording synchronism table handling is deleted in step S14, again which is heavy before affairs are submitted to here
In new addition so that slave nodes do not produce json daily records again in the record of synchronous master nodes, it is to avoid cause
Master nodes and slave nodes cycle through same log.
S17, transaction rollback, return to step S8 are circulated.
One of ordinary skill in the art will be appreciated that embodiment described here is to aid in reader and understands this
Bright principle, it should be understood that protection scope of the present invention is not limited to such especially statement and embodiment.This area
It is each that those of ordinary skill can make various other without departing from essence of the invention according to these technologies enlightenment disclosed by the invention
Plant concrete deformation and combine, these deformations and combination are still within the scope of the present invention.
Claims (10)
1. the embedded database synchronous method based on SQLite, it is characterised in that comprise the following steps：
S1, configuration role of user's equipment of itself in synchronizing network；In synchronization system, synchronous equipment is referred to as node,
Node in system is divided into two kinds of master nodes and slave nodes, can only have a master node in system, and at least one
Individual slave nodes；If multiple slave nodes, then distinguished by configuration section period；
S2, on the same network segment it is master nodes and slave nodes configuration IP address, and in master nodes and slave
Ftp server is set up on node all；
S3, master node is in a locally created soap server；
, according to configuration, on the basis of available data library structure, increase needs synchronous meter for S4, master node and slave nodes
Operation sheet, and increase trigger in data base, for the major key ID that changes in recording synchronism table and the record
Variation type；
S5, each slave node send request, acquisition request master node synchronous meter to the soap servers of master nodes
Data；
S6, master node makees queuing process to each request according to sequencing, and the synchrodata on master nodes
The json journal files that slave nodes are capable of identify that actively are encapsulated as, the FTP clothes of the currently processed slave nodes for arriving are sent to
On business device；
S7, receive json journal files after, slave nodes are resolved to SQL statement and are performed, obtain master nodes on
Synchrodata；
S8, master node and slave nodes judge the operation whether synchronous meter increases, deletes or update, if then entering
Enter step S9, otherwise into step S10；
S9, trigger record the ID and change type for occurring to change record in corresponding operation sheet；
Whether S10, master node and slave nodes have content in judging operation sheet, and step S11 is entered if having, no
Step S13 is entered then；
S11, master node and slave nodes are processed in the thread of encapsulation, record is encapsulated as json daily records, and is deleted
The corresponding record that trigger is produced in division operation log；
S12, master node and slave nodal tests send thread and send to other side's ftp server to generating after json daily records
Json daily records；
Whether the json daily record that receive is had on S13, master node and slave nodal test ftp servers, if then entering
Step S14, otherwise return to step S8；
S14, parsing thread parsing json daily records, turn-on data storehouse affairs generate corresponding SQL statement and perform；
S15, judge whether SQL statement runs succeeded, if then entering step S16, otherwise into step S17；
S16, submit affairs to and delete corresponding json files, return to step S8 is circulated；
S17, transaction rollback, return to step S8 are circulated.
2. the embedded database synchronous method based on SQLite according to claim 1, it is characterised in that the step
In S2, master nodes need the IP address for configuring one or more slave node, slave nodes then to only need to configuration
The IP address of master nodes.
3. the embedded database synchronous method based on SQLite according to claim 1, it is characterised in that the step
In S4, the content of operation note table record includes the mode of operation of the ID and the record of data-base recording, and mode of operation is divided into
Increase, delete and update three kinds.
4. the embedded database synchronous method based on SQLite according to claim 1, it is characterised in that the step
If slave nodes change the content of synchronous meter because of the daily record of parsing master node transmissions in S9, then slave nodes
Due to first deleting trigger, corresponding operation note will not be generated, so as to prevent master nodes and the circulation of slave nodes
The same synchronous recording of generation.
5. the embedded database synchronous method based on SQLite according to claim 1, it is characterised in that the step
In S11, the content of json daily records includes database table title, recorded content and the action type for changing.
6. the embedded database synchronous method based on SQLite according to claim 5, it is characterised in that the step
In S11 the detailed process that record is encapsulated as json daily records it is：Master nodes and slave nodes are first read in synchronous recording table
The ID and action type of record, in correspondence synchronous meter reads data according to ID, is written in the file of json forms, and adds
Action type；When action type is to delete, the ID that recorded content is only recorded.
7. the embedded database synchronous method based on SQLite according to claim 1, it is characterised in that the step
Thread is sent in S12 to the specific rules that other side's ftp server sends json daily records is：Slave nodes are simply sent to master
Node, sends thread and sorts according to the filename of json journal files, be sent to the ftp server of master nodes successively；
Master nodes generate the corresponding json files of multiple slave nodes a record, and when sending, master nodes are correspondence
Json files be sent to the ftp server of each slave node.
8. the embedded database synchronous method based on SQLite according to claim 5, it is characterised in that the step
S14 is specially：Turn-on data storehouse affairs, parse after thread obtains action type, the synchronous meter of operation and recorded content and generate
Corresponding SQL statement, the SQL statement that the sentence was performed before being exactly other side, performs the sentence, and the operation must
Synchronization is arrived.
9. the embedded database synchronous method based on SQLite according to claim 8, it is characterised in that the step
In S14, slave nodes need the trigger of deletion record synchronization table handling after the affairs of turn-on data storehouse, prevent from performing synchronization
The synchronous recording is recorded by trigger again afterwards, it is to avoid the same record of synchronization of master nodes and the circulation of slave nodes.
10. the embedded database synchronous method based on SQLite according to claim 9, it is characterised in that the step
In rapid S16, slave nodes needed the corresponding trigger deleted to add before affairs are submitted to again.
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 true CN106599061A (en) | 2017-04-26 |
| CN106599061B 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) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107590256A (en) * | 2017-09-20 | 2018-01-16 | 北京九桥同步软件有限公司 | Heterogeneous database synchronization method and device |
| CN107657002A (en) * | 2017-09-20 | 2018-02-02 | 北京九桥同步软件有限公司 | File synchronisation 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 |
| CN109271450A (en) * | 2018-10-10 | 2019-01-25 | 北京百度网讯科技有限公司 | Database synchronization method, device, server and storage medium |
| CN109542926A (en) * | 2018-11-06 | 2019-03-29 | 北京新唐思创教育科技有限公司 | Block processes method and computer storage medium |
| CN109933630A (en) * | 2019-03-19 | 2019-06-25 | 武汉达梦数据库有限公司 | Database data real-time synchronization method and equipment |
| CN110188118A (en) * | 2019-04-25 | 2019-08-30 | 广州至真信息科技有限公司 | A kind of method of data synchronization, device |
| CN110263052A (en) * | 2019-06-25 | 2019-09-20 | 苏宁消费金融有限公司 | One kind automating simultaneous techniques innovative approach based on big data Hadoop platform ODS |
| CN110347652A (en) * | 2019-07-12 | 2019-10-18 | 天津凯发电气股份有限公司 | A kind of Power quality management system multimachine database synchronization implementation method |
| CN110704532A (en) * | 2019-09-18 | 2020-01-17 | 南方电网数字电网研究院有限公司 | Method and device for synchronizing data among databases, computer equipment and storage medium |
| CN111522897A (en) * | 2020-05-07 | 2020-08-11 | 福州市勘测院 | Method for incremental synchronization of spatial data between ArcSDE (android System File) and File GDB (graphics database) |
| CN113220968A (en) * | 2021-05-26 | 2021-08-06 | 西安热工研究院有限公司 | 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 |
Cited By (19)
| 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 |
| CN109271450A (en) * | 2018-10-10 | 2019-01-25 | 北京百度网讯科技有限公司 | Database synchronization method, device, server and storage medium |
| CN109542926B (en) * | 2018-11-06 | 2021-04-09 | 北京新唐思创教育科技有限公司 | Block processing method and computer storage medium |
| CN109542926A (en) * | 2018-11-06 | 2019-03-29 | 北京新唐思创教育科技有限公司 | Block processes method and computer storage medium |
| CN109933630B (en) * | 2019-03-19 | 2021-11-23 | 武汉达梦数据库股份有限公司 | Real-time database data synchronization method and device |
| CN109933630A (en) * | 2019-03-19 | 2019-06-25 | 武汉达梦数据库有限公司 | Database data real-time synchronization method and equipment |
| CN110188118A (en) * | 2019-04-25 | 2019-08-30 | 广州至真信息科技有限公司 | A kind of method of data synchronization, device |
| CN110263052A (en) * | 2019-06-25 | 2019-09-20 | 苏宁消费金融有限公司 | One kind automating simultaneous techniques innovative approach based on big data Hadoop platform ODS |
| CN110263052B (en) * | 2019-06-25 | 2021-07-20 | 苏宁消费金融有限公司 | Automatic synchronization technology innovation method based on big data Hadoop platform ODS |
| CN110347652A (en) * | 2019-07-12 | 2019-10-18 | 天津凯发电气股份有限公司 | A kind of Power quality management system multimachine database synchronization implementation method |
| 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 |
| CN111522897A (en) * | 2020-05-07 | 2020-08-11 | 福州市勘测院 | Method for incremental synchronization of spatial data between ArcSDE (android System File) and File GDB (graphics database) |
| 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) |
| CN113220968A (en) * | 2021-05-26 | 2021-08-06 | 西安热工研究院有限公司 | Clustered network crawler-based automatic power technology standard updating system and method |
| CN113220968B (en) * | 2021-05-26 | 2023-03-14 | 西安热工研究院有限公司 | Clustered network crawler-based automatic power technology standard updating system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106599061B (en) | 2020-06-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106599061A (en) | SQLite-based embedded database synchronization method | |
| EP3754514B1 (en) | Distributed database cluster system, data synchronization method and storage medium | |
| US8260742B2 (en) | Data synchronization and consistency across distributed repositories | |
| US7240114B2 (en) | Namespace management in a distributed file system | |
| CN103235820B (en) | Date storage method and device in a kind of group system | |
| CN103365873B (en) | The method for pushing of business datum and device | |
| CN102262680A (en) | Distributed database proxy system based on massive data access requirement | |
| KR20090040473A (en) | Concatenation discovery web service | |
| CN108595522A (en) | A kind of increment synchronization method, apparatus and system | |
| CN106953910A (en) | A kind of Hadoop calculates storage separation method | |
| CN109145060B (en) | Data processing method and device | |
| CN106339498A (en) | Method, device and system for synchronizing data | |
| CN103825918B (en) | Method of data synchronization, terminal device, server and system | |
| CN113704790A (en) | Abnormal log information summarizing method and computer equipment | |
| CN109873857A (en) | Mobile terminal method of data synchronization and device under a kind of no network state | |
| CN113946559A (en) | Data processing method, target database system and data processing system | |
| CN113761079A (en) | Data access method, system and storage medium | |
| CN104731827B (en) | The generation method and device of fast distributed file system files metadata | |
| CN107180034A (en) | The group system of MySQL database | |
| KR101825910B1 (en) | Heterogeneous database synchronization system and method using neutral data based on redo log analysis | |
| CN109947592A (en) | A kind of method of data synchronization, device and relevant device | |
| CN110555064A (en) | data service system and method for insurance business | |
| US7441252B2 (en) | Cache control device, and method and computer program for the same | |
| US7543300B2 (en) | Interface for application components | |
| CN115826679A (en) | Method, system, equipment and storage medium for managing clock source in kubernets cluster |
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 |