CN105320681A - Database content combination method and device - Google Patents
Database content combination method and device Download PDFInfo
- Publication number
- CN105320681A CN105320681A CN201410339322.9A CN201410339322A CN105320681A CN 105320681 A CN105320681 A CN 105320681A CN 201410339322 A CN201410339322 A CN 201410339322A CN 105320681 A CN105320681 A CN 105320681A
- Authority
- CN
- China
- Prior art keywords
- source
- merging
- database
- data
- consolidation strategy
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Abstract
The invention provides a database content combination method and device. The method includes the steps of establishing a mirror image database corresponding to a source database, wherein the mirror image database is completely the same as the source database; conducting form information combination on a source form of the mirror image database and a target form, needing to be combined with the source form, in a target database according to the combination strategy corresponding to the source form in the mirror image database. By means of the scheme, the aim of combining with applications of complex service logic in the prior art is achieved, and the capacity for processing database content combination is improved.
Description
Technical field
The present invention relates to computer realm, particularly relate to a kind of data-base content merging method and device.
Background technology
Along with the development of computer technology, the use of database in main software system is more and more general, especially in some application scenarios, needs to overlap two of same application software independently data-base content and merges into a set of data-base content and manage.
For the merging of database, the Data Migration Tools that usual usage data base management system provides self merges migration to carry out data.But because this kind of Data Migration Tools is unitized instrument, it can only process simple Data Migration logic, such as by the data supplementing of a form in database A in the some forms in database B.
And for having the application program of complicated business logic, this Migration tools is often helpless, there is significant limitation.So how realizing the consolidation problem of the application program for complicated business logic, is have problem to be solved.
Summary of the invention
The object of this invention is to provide a kind of data-base content merging method and device, solve the consolidation problem for the application program of complicated business logic in prior art.
To achieve these goals, the invention provides a kind of data-base content merging method, comprising:
Set up the mirror database that source database is corresponding, identical with described source database in described mirror database;
The consolidation strategy corresponding according to the source form in described mirror database, to the source form of described mirror database, the object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
Wherein, the described step setting up mirror database corresponding to source database comprises:
Backup source database, obtains the backup file carrying form data;
Choose the data base management system (DBMS) belonging to destination data storehouse;
In described data base management system (DBMS), set up mirror database corresponding to described source database, and the form data of carrying in described backup file is added in described mirror database.
Wherein, the described consolidation strategy corresponding according to the source form in described mirror database, to the source form of described mirror database, with the object form needing in destination data storehouse to carry out with described source form merging, the step of carrying out form data merging comprises:
The consolidation strategy that source form in described mirror database in acquisition configuration file is corresponding;
When there being inspection policies in consolidation strategy, according to described inspection policies, choose sql statement and/or merge the form that plug-in unit detects in mirror database and destination data storehouse and can carry out form data merging, if detect successfully, then according to the form consolidation strategy in described consolidation strategy, to the source form of described mirror database, the object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
Wherein, according to the form consolidation strategy in described consolidation strategy, to the source form of described mirror database, with the object form needing in destination data storehouse to carry out with described source form merging, the step of carrying out form data merging comprises:
To obtain in mirror database the set of active form;
Set up in the set of source form the corresponding relation needing to carry out form and the form consolidation strategy merged with the object form in destination data storehouse;
According to priority order carries out form data merging to the object form in source form and destination data storehouse.
Wherein, the step that the object form in source form and destination data storehouse carries out form data merging is comprised:
The form consolidation strategy that source form in the set of acquisition source form is corresponding;
If described form consolidation strategy is for specifying consolidation strategy and specifying consolidation strategy type for merging or being amendment strategy, then judge in destination data storehouse, whether to there is the object form of the same name with source form, if exist, then to source form and and source form object form of the same name carry out form data merging, otherwise, in destination data storehouse, create the object form of the same name with source form, then form data merging is carried out to source form and object form.
Wherein, the step that source form and object form carry out form data merging is comprised:
Judge that whether source form is consistent with the list structure of object form, if, according to the appointment consolidation strategy of described source form, form data merging is carried out to source form and object form, otherwise, the list structure of source form is converted to consistent with the list structure of object form after, then according to the appointment consolidation strategy of described source form, form data merging is carried out to source form and object form.
Wherein, according to the appointment consolidation strategy of described source form, the step of source form and object form being carried out to form data merging comprises:
If described source form does not specify consolidation strategy, obtain the record sum of source form;
If the record sum of described source form is not 0, performs and insert statement, all records in the form of source are inserted in object form.
Wherein, according to the appointment consolidation strategy of described source form, the step of source form and object form being carried out to form data merging comprises:
If described source form has appointment consolidation strategy, then by appointment consolidation strategy, source form is modified, obtain the record of amended source form;
The record of this amended source form is inserted in object form.
Wherein, modify to source form, the step obtaining the record of amended source form comprises:
The record of the record or major key conflict of violating constraint rule in the form of described source is modified or deleted, obtains the record of amended source form; Or
To in the form of described source certainly add or sequence adds a fixed value, obtain the record of amended source form; Or
There is external key to described source form to rely on, when modifying to dependence parent table, dependence sublist also being carried out to the amendment of related content, obtaining the record of amended source form.
Wherein, the step that the record of this amended source form is inserted in object form is comprised:
If object form employs trigger and object form is not relied on by other table, then, when inserting the record of source form in object form, what utilize trigger automatically to generate record increases progressively ID; Otherwise when inserting the record of source form in object form, forbid described trigger, after at record, insertion completes, then to recover trigger be state before merging.
Embodiments of the invention also provide a kind of data-base content to merge device, comprising:
Set up module, for setting up mirror database corresponding to source database, identical with described source database in described mirror database;
Merge module, for the consolidation strategy corresponding according to the source form in described mirror database, to the source form of described mirror database, the object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
Wherein, set up module to comprise:
Backup submodule, for backup source database, obtains the backup file carrying form data;
Connexon module, for choosing the data base management system (DBMS) belonging to destination data storehouse;
Setting up submodule, for setting up mirror database corresponding to described source database in described data base management system (DBMS), and the form data of carrying in described backup file being added in described mirror database.
Wherein, merge module to comprise:
Obtain submodule, for obtaining consolidation strategy corresponding to source form in the described mirror database in configuration file;
Merge submodule, for when there being inspection policies in consolidation strategy, according to described inspection policies, choose sql statement and/or merge the form that plug-in unit detects in mirror database and destination data storehouse and can carry out form data merging, if detect successfully, then according to the form consolidation strategy in described consolidation strategy, to the source form of described mirror database, object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
Technique scheme of the present invention has following technique effect:
By adopting the method for the invention, the flow process that general data-base content merges can be realized.For the form without the need to special processing, directly give tacit consent in the form of the same name charting in source database is appended in destination data storehouse by merging master routine; For the form comprising the complicated business logical data merging master routine None-identified, by the consolidation strategy of specifying its correspondence in policy configuration file, merge master routine carries out data merging according to this consolidation strategy; For the application scenarios of the overwhelming majority, developer only need configure some sql statements in policy configuration file can reach the object revising the list data that cannot directly merge, and in extreme complicated application scenarios, developer can be incorporated into the secondary development plug-in unit that oneself coding realizes and merge in flow process; In addition, the present invention additionally uses the treatment mechanism of concurrent thread, improves the processing speed of merging.
Accompanying drawing explanation
The method flow diagram that the data-base content that Fig. 1 provides for the embodiment of the present invention merges;
The method specific embodiment process flow diagram that the data-base content that Fig. 2 provides for the embodiment of the present invention merges;
The process flow diagram that in the method that the data-base content that Fig. 3 provides for the embodiment of the present invention merges, form merges;
The apparatus structure block diagram that the data-base content that Fig. 4 provides for embodiments of the invention merges.
Embodiment
For making the object of the embodiment of the present invention, technical scheme and advantage clearly, below in conjunction with accompanying drawing, specific embodiment is described in detail.
As shown in Figure 1, embodiments of the invention provide a kind of data-base content merging method, comprising:
Step 11, sets up the mirror database that source database is corresponding, identical with described source database in described mirror database;
Step 12, the consolidation strategy corresponding according to the source form in described mirror database, to the source form of described mirror database, the object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
This embodiment of the present invention is by setting up and the identical mirror database of source database, and the consolidation strategy corresponding according to the source form in mirror database, need the object form merged with described source form to carry out form data merging in the source form of described mirror database and destination data storehouse; Thus two of same application software can be overlapped the scheme that independently data-base content merges into a set of data-base content, the service logic of various complexity can be adapted to.
In a specific embodiment of the present invention, above-mentioned steps 11 can comprise:
Step 111, backup source database, obtains the backup file carrying form data;
Step 112, chooses the data base management system (DBMS) belonging to destination data storehouse;
Step 113, sets up mirror database corresponding to described source database, and the form data of carrying in described backup file is added in described mirror database in described data base management system (DBMS).
In this embodiment of the present invention, an interim image database is created in the data base management system (DBMS) at place, destination data storehouse, by Backup and Restore function (or other data migration methods), source database is returned in this interim image database, then using this interim image database as source database.Access originator and destination data storehouse while of this makes it possible to allow user in sql statement.
In another specific embodiment of the present invention, above-mentioned steps 12 specifically can comprise:
Step 121, the consolidation strategy that the source form in the described mirror database in acquisition configuration file is corresponding;
Step 122, when there being inspection policies in consolidation strategy, according to described inspection policies, choose sql statement and/or merge the form that plug-in unit detects in mirror database and destination data storehouse and can carry out form data merging, if detect successfully, then according to the form consolidation strategy in described consolidation strategy, to the source form of described mirror database, object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
In this embodiment of the present invention, for adapting to complicated service logic, so also need user to configure " consolidation strategy " to be combined flow process carry out intervention needs, the scene had in merging process does not need to merge, therefore, need to detect before merging, identify the application scenarios that some cannot merge.Such as in student's register information management system, do not allow to occur ID (identity number) card No. identical two and above student's record, if the situation comprising this conflict in two sets of data storehouse contents to be combined detected before merging, should forbid carrying out follow-up merging flow process; Again such as, two data-base contents to be combined are produced by the application software of different editions, and data structure is incompatible, also should not merge.Detect before merging, according to the form consolidation strategy in described consolidation strategy, need the object form merged with described source form to carry out form data merging in the source form of described mirror database and destination data storehouse, business processing efficiency can be improved.
In the above-described embodiment, in step 122, according to the form consolidation strategy in described consolidation strategy, to the source form of described mirror database, with the object form needing in destination data storehouse to carry out with described source form merging, the specific implementation process of carrying out form data merging can comprise:
Step 1221, to obtain in mirror database the set of active form;
Step 1222, sets up in the set of source form, needs and object form in destination data storehouse carries out the corresponding relation of form and the form consolidation strategy merged;
Step 1223, according to priority order carries out form data merging to the object form in source form and destination data storehouse.
As shown in Figure 2, data-base content merges flow process entirety and comprises the specific implementation of this embodiment:
(1) backup needs all source databases participating in merging, obtains its backup file;
(2) specify the data base management system (DBMS) at place, destination data storehouse, successfully connect into the identity of system manager's (or other meet the role of operating right);
(3) specify all backup files needing to participate in the source database merged, be that each source database creates corresponding interim image database automatically, and recover the content of all source databases;
(4) all consolidation strategies in configuration file are resolved;
(5) according to the inspection policies in consolidation strategy, perform the testing before merging, if return failure, then forward step (9) to, terminate merging work; If returned successfully, or do not configure any inspection policies, then continue process subsequent step;
(6) all table information aggregates in all source databases to be combined of device sequence acquisition are merged, again in conjunction with all consolidation strategies obtained in (2) step, set up the mapping relations of all tables to be combined and consolidation strategy, here table to be combined is: in the set of source form, to need and object form in destination data storehouse carries out the form that merges, and sort according to the priority level defined in consolidation strategy;
(7) according to priority level sequencing from high to low, other all form of concurrent processing same priority, after the form of this priority level is all disposed, the form that reprocessing priority level is lower, until all Form Handle are complete;
(8) merge device and delete the volatile data base created;
(9) end-of-job is merged.
In the above embodiment of the present invention, the specific implementation flow process of the object form in source form and destination data storehouse being carried out to form data merging comprises:
Step 12231, the form consolidation strategy that the source form in the set of acquisition source form is corresponding;
Step 12232, if described form consolidation strategy is for specifying consolidation strategy and specifying consolidation strategy type for merging or being amendment strategy, then judge in destination data storehouse, whether to there is the object form of the same name with the source form in the set of source form, if exist, then form data merging is carried out to object form of the same name with source form in source form and destination data storehouse, otherwise, in destination data storehouse, create the object form of the same name with source form, then form data merging is carried out to source form and object form.
In further step 12232, the step of source form and object form being carried out to form data merging comprises:
Judge that whether source form is consistent with the list structure of object form, if, according to the appointment consolidation strategy of described source form, form data merging is carried out to source form and object form, otherwise, the list structure of source form is converted to consistent with the list structure of object form after, then according to the appointment consolidation strategy of described source form, form data merging is carried out to source form and object form.
Further, in step 12232, according to the appointment consolidation strategy of described source form, the step of source form and object form being carried out to form data merging comprises:
Step 122321, if described source form does not specify consolidation strategy, obtains the record sum of source form; If the record sum of described source form is not 0, performs and insert statement, all records in the form of source are inserted in object form.
Step 122322, if described source form has appointment consolidation strategy, then modifies to source form by appointment consolidation strategy, obtains the record of amended source form; The record of this amended source form is inserted in object form.
In step 122322, modify to source form, the step obtaining the record of amended source form comprises:
The record of the record or major key conflict of violating constraint rule in the form of described source is modified or deleted, obtains the record of amended source form; Or
To in the form of described source certainly add or sequence adds a fixed value, obtain the record of amended source form; Or
There is external key to described source form to rely on, when modifying to dependence parent table, dependence sublist also being carried out to the amendment of related content, obtaining the record of amended source form.
Wherein, the step that the record of this amended source form is inserted in object form is comprised:
If object form employs trigger and object form is not relied on by other table, then, when inserting the record of source form in object form, what utilize trigger automatically to generate record increases progressively ID; Otherwise when inserting the record of source form in object form, forbid described trigger, after at record, insertion completes, then to recover trigger be state before merging.
The merging specific implementation flow process of this form as shown in Figure 3, comprising:
1. search the form consolidation strategy of this table correspondence, if specify form consolidation strategy and policing type is nonjoinder strategy, then this table merges flow process and terminates at this, forwards step to 8.; If form consolidation strategy do not specified by this table, or policing type is amendment strategy, then continue merging flow process below;
If 2. there is not same famous-brand clock in destination data storehouse, then create mutually isostructural form of the same name wherein, and forward step to 4.;
3. obtain the structural information of this table in source database and destination data storehouse, whether comparison sheet structure is consistent; If consistent, then turn next step; If inconsistent, judge whether this table specifies form consolidation strategy, if do not specify form consolidation strategy, or specify form consolidation strategy and set and carried out by " merging treatment device " flow path switch that in source database and destination data storehouse, list structure is inconsistent, then merge list structure in the automatic converting source data storehouse of device, make it consistent with the list structure in destination data storehouse; If specify consolidation strategy and consolidation strategy setting can't help " merging treatment device " carried out the flow path switch that in source database and destination data storehouse, list structure is inconsistent, then do not do any process, turn next step;
If 4. form consolidation strategy do not specified by this table, then obtain the record sum of this table of source database, if record adds up to 0, then forward the merging flow process that 8. step terminates this table to, otherwise forward the additional merging that 6. step carries out table record to;
If 5. this table specifies consolidation strategy, then merge the step of device according to this strategy execution a series of Update Table storehouse content; If consolidation strategy setting can't help " merging treatment device " carried out the merging flow process of data after amendment, then forward step to 7., otherwise continue step below;
6. perform insert statement, all record additions of this table in source database are inserted in the same famous-brand clock in destination data storehouse;
If 7. this table specifies consolidation strategy, and the setting of this strategy have disabled some trigger, then the trigger recovered in destination data storehouse is the state before merging;
8. this table merging flow process terminates.
In above-mentioned flow process, concrete, the revised context consolidation strategy of table, being the child node of database policies, for revising data to be combined in merging process, comprising following content:
1. table name claims, and specifies the concrete table that this strategy is corresponding;
2. policing type is " amendment " type;
3. priority level, optional, if assigned priority is not other, is defaulted as the priority level inheriting father node database, after the table that priority level is high has merged, the table that priority level is low could be merged.For the table having external key dependence, " merging treatment device " can automatically identify from the system table of data base management system (DBMS), and then Lookup protocol priority, can not need user to carry out priority setting.
4. sql statement, child node, optional, configurable multiple child node, for revising list structure in source database or destination data storehouse or data content (be not only confined to revise the table when pre-treatment, also can revise other association dependence tables);
5. merge plugin name, child node, optional, configurable multiple child node, for before merging when the complicated business logic that sql statement cannot process, merge plug-in unit process for merging secondary development that master routine invoke user realizes;
6. whether carried out by " merging treatment device " flow path switch that in source database and destination data storehouse, list structure is inconsistent, child node, optional.Be defaulted as "Yes", when this list structure is inconsistent in source database and destination data storehouse, carried out the structure shown in converting source data storehouse by " merging treatment device ", make it identical with the structure shown in destination data storehouse; If be "No", represent that this conversion has been come by user configured sql statement or " merging plug-in unit ", " merging treatment device " does not participate in flow path switch.
7. the merging flow process of data after whether being revised by " merging treatment device ", child node, optional, be defaulted as "Yes", represent after " merging treatment device " performs a series of user configured sql or " merging plug-in unit " revises data to be combined, " merging treatment device " table content the most at last in source database is simply appended in the same famous-brand clock in destination data storehouse; If be configured to "No", represent that the merging process of this table completes in user configured sql or " merging plug-in unit ", " merging treatment device " is no longer needed to participate in, for the service logic of some complexity, mode not by simply adding merges, then now can be masked the flow process of " merging treatment device " by this mode, carried out the merging flow process of some table leading completely by user;
8. from adding and corresponding sequence names, specify in current table which is classified as from adding, child node, optional.Certainly adding in physical definition, " merging treatment device " can be inquired about and identify from the system table of data base management system (DBMS), even if so user does not specify its concrete row title, also can automatically process; Under some scene, although certain row is not defined as from adding, it uses sequence or other service logic algorithms to realize similar certainly increasing function, and this situation of " merging treatment device " None-identified, therefore must specify respective column title by user; If employ sequence, also need specified sequence title, " merging treatment device " just can adopt some algorithm automatically to revise the value of these row according to this two each and every one information, to avoid violating the constraint from adding uniqueness, and the currency of synchronizing sequence;
9. from adding association external key sublist title and row title, be child node 7., optional, configurable multiple child node.If this table is relevant sublist also, maintained parent subrelation is carried out from the uniqueness added by parent table, then need to specify corresponding sublist title and row title in parent table strategy, merge master routine like this and automatically can revise when revising certainly the adding of master meter the foreign key column associating sublist;
10. the trigger title forbidden is needed, optional, child node, configurable multiple child node.Merge in the process of current table whether forbid appointment trigger by user according to service logic decision, merged its original state of rear recovery.
This tactful applicable surface is comparatively wide, for herein recited above need special processing scene (3), (4), (5), (6), (7), (8), (9).Provide the example of an xml configuration below:
<databasesource＝”db1”destination＝"db1">
--need the combined statement strategy of revised context, name specifies table name to claim, strategy named policer type,
Level assigned priority is other,
-->
<tablename＝"table_c"strategy＝"modify"level＝"1">
--sql statement, Update Table content, deletes record--the > that in source database, id repeats
<sql>deletefrom％SOURCE(db1)％.table_cwhereidin(selectidfromdb1.table_c)</sql>
-merge plugin name-->
<plugin>com.merge.plugin.table.test</plugin>
--specifying merging treatment device to complete the flow path switch of list structure difference-->
<transformByTool>true</transformByTool>
--specifying merging treatment device to carry out the merging flow process of the rear data of amendment-->
<mergeByTool>true</mergeByTool>
-coluemn specifies from adding name, sequence specified sequence title-->
<identitycolumn＝”c1”sequence＝”seq1”>
The sublist that-association is added certainly, assigned source database name, table name, row name-->
<childTabledb＝”db1”name＝”table_d”column＝”cc1”></>
</identity>
--specifying the trigger title needing forbidding-->
<disableTriggerdb＝”db1”name＝”tg1”></disableTrigger>
</table>
</database>
Adopt the method for the invention, by the data base management system (DBMS) at source database place, all databases participating in merging that needs are backed up.The parameter connecting place, destination data storehouse data base management system (DBMS) is set, enters with system manager's identity logs.The backup file path of assigned source database, in the data base management system (DBMS) at place, destination data storehouse, creates volatile data base for each source database and recovers.Parses policy configuration file.The complete all tables of the concurrent merging of the consolidation strategy of specifying according to default processing flow and user.The flip-flop states that reduction is forbidden in merging process.Delete volatile data base.The flow process that general data-base content merges can be realized.Overall merging flow process has been come by merging master routine; For the form without the need to special processing, merge master routine acquiescence and the table record in source database is appended in the same famous-brand clock in destination data storehouse; For the form comprising the complicated business logical data merging master routine None-identified, in policy configuration file, specify its consolidation strategy by developer, merge master routine carries out data merging according to its consolidation strategy; In most application scenarios, developer only need configure some sql statements in policy configuration file can reach the object revising the table data that cannot directly merge, in extreme complicated application scenarios, developer can be incorporated into the secondary development plug-in unit that oneself coding realizes and merge in flow process; In addition, merge the treatment mechanism that device have employed concurrent thread, improve the processing speed merged.
Embodiments of the invention also provide a kind of data-base content to merge device, comprising:
Set up module, for setting up mirror database corresponding to source database, identical with described source database in described mirror database;
Merge module, for the consolidation strategy corresponding according to the source form in described mirror database, to the source form of described mirror database, the object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
Wherein, set up module to comprise:
Backup submodule, for backup source database, obtains the backup file carrying form data;
Connexon module, for choosing the data base management system (DBMS) belonging to destination data storehouse;
Setting up submodule, for setting up mirror database corresponding to described source database in described data base management system (DBMS), and the form data of carrying in described backup file being added in described mirror database.
Wherein, merge module to comprise:
Obtain submodule, for obtaining consolidation strategy corresponding to source form in the described mirror database in configuration file;
Merge submodule, for when there being inspection policies in consolidation strategy, according to the title of described inspection policies, choose sql statement and/or merge the form that plug-in unit detects in mirror database and destination data storehouse and can carry out form data merging, if detect successfully, then according to the form consolidation strategy in described consolidation strategy, to the source form of described mirror database, object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
This device is the device corresponding with said method, and all implementations in said method embodiment are all applicable in the embodiment of this device, also can reach identical technique effect.
Concrete, as shown in Figure 4, the concrete framework of this device is as follows:
Above-mentioned merging module can be specifically the merging treatment flow process of merging treatment device, the built-in acquiescence of merging treatment device, and a set of alternative general consolidation strategy treatment scheme; " merging master routine " is responsible for all " consolidation strategy " information comprised in resolution system, for there is no the table of specifying " consolidation strategy " in system, acquiescence flow process is used to merge, for the table specifying " consolidation strategy ", the treatment scheme of being somebody's turn to do " consolidation strategy " corresponding is used to merge.It should not rely on the service logic of concrete some application software, and just only processes data merging from the angle of database;
Consolidation strategy, some table cannot be merged by the carrying out that default processing flow is correct, then need user to specify special form consolidation strategy, makes " merging treatment device " according to this form consolidation strategy to carry out data merging; The syntactic definition of form consolidation strategy should not rely on the service logic of concrete some application software equally, and is to provide the form consolidation strategy that various application software can be general.
Merge plug-in unit, the scope that the complexity that some service logic shown merges flow process can process beyond " merging master routine ", need user to specify in " consolidation strategy " " the merging plug-in unit " of this table correspondence, call this plug-in unit to complete merging work for " merging master routine "; The standard interface that " merging plug-in unit " is defined according to merging device by user realizes.
Such as, the content of merge database A and database A', merge device with database A for source database, database for the purpose of database A', the net result after merging is embodied on the A' of destination data storehouse.For following several scene, " merging treatment device " there is the treatment scheme of acquiescence:
The first scene: the table a in source database A, have table a corresponding with it, and list structure is identical, in this case, gives tacit consent to and is all appended to inside the table a in the A' of destination data storehouse by all records showing a in source database A in the A' of destination data storehouse;
The second scene: the table a in source database A, table a corresponding is with it had in the A' of destination data storehouse, and list structure is not identical (if reasonable in design, application program should be avoided occurring this situation as far as possible), in this case, acquiescence needs the structure showing a in the A of converting source data storehouse, makes it identical with the structure showing a in the A' of destination data storehouse (precondition is that application program allows this conversion), and then merges in the mode of the first scene; The treatment scheme of conversion table structure, automatically can be processed by the difference of merging treatment device according to the table information obtained in Database System Tables, also can process according to user configured consolidation strategy.
The third scene: the table a in source database A, table a corresponding is not with it had in the A' of destination data storehouse, in this case, merging treatment device creates of the same name with it and that structure is identical table in the A' of destination data storehouse, and the mode of planting scene with (1) more afterwards merges;
4th kind of scene: the table a in the A' of destination data storehouse, not having table a corresponding with it, in this case, giving tacit consent to without the need to carrying out any merging in source database A.
Can find out, above four kinds of scenes, the 4th kind of scene can neglect, and other three kinds can be converted into the first scene to process.But the processing mode of the first scene acquiescence the most simply merges mode (this is also the processing mode that data base management system (DBMS) carries Data Migration Tools), complicated service logic cannot be adapted to, so also need user to configure " consolidation strategy " to be combined the flow process intervention.
Need in merging process to specify the scene of the special merging flow process of " consolidation strategy " roughly to have following several:
(1) need first to detect before merging, identify the application scenarios that some cannot merge.Such as in student's register information management system, do not allow to occur ID (identity number) card No. identical two and above student's record, if the situation comprising this conflict in two sets of data storehouse contents to be combined detected before merging, should forbid carrying out follow-up merging flow process; Again such as, two data-base contents to be combined are produced by the application software of different editions, and data structure is incompatible, also should not merge.
(2) some table does not need to participate in merging.Some preserve the table of initialization data, in the content of every sets of data storehouse, all certainly exist identical data, and only need to retain a content in destination data storehouse, and this kind of table should not participate in merging; Such as, one is had for preserving the table of Student Cadre position kind in student's register information management system, when each system is installed, the initialization data storehouse stage has just inserted the record of all Student Cadre position kinds automatically, also can not carry out additions and deletions to this table again and change operation during system cloud gray model; So when merging, if this table record in source database being merged in destination data storehouse, the record that there are two cover repetitions in this table can being caused, and then cause service logic mistake, therefore should not merge this table.
(3) some the table definition in source database and the definition in destination data storehouse are inconsistent, need to convert to unanimously, then merge.
(4) some table only needs to merge the partial content in source database, instead of full content.Equally in student's register information management system for preserving the table of Student Cadre position kind, if some record is inserted automatically when system installs initialization data storehouse in this table, can not delete and retouching operation this part record during system cloud gray model, but cadre's position type records of some users input may be increased newly; Merge time, the record that in source database, user increases newly should be merged, and not should combination system install time initialized record; In more complicated cases, if also can delete and retouching operation the initialization data of this table during system cloud gray model, record not identical with cadre's position title in destination data storehouse for all source databases all should be merged in destination data storehouse so in theory, and the identical record of cadre's position title should not merge.
(5) some table may violate data constraint when merging---such as major key conflict, violate unique constraints etc. (constraint in list structure definition or service logic, can regard as and violate data constraint).For the record violating data constraint, the service logic of application software is different, and the strategy taked also may be different; User merges after can selecting to delete and violating the record of constraint in source database again, merges after also can selecting to violate the record of constraint in amendment source database again.
(6) some table employs from adding (or sequence), may there is the ID of conflict during merging.A fixed value can be added by unified for certainly adding in source database (or using row of sequence), just can the ID of conflict removal, and then carry out union operation; The acquisition of this fixed value, can adopt this algorithm: this row minimum value in this row maximal value+1-source database in fixed value=destination data storehouse; For certainly adding, should opening when merge record from adding insertion characteristic, so just can retain the ID value inserting record; For sequence, because it can not be automatically synchronous with table record, also should adjust the currency of sequence in destination data storehouse, also add identical fixed value.
(7) there is father and son's dependence in some table---such as external key dependence etc. (list structure definition or service logic on dependence, Existence dependency relationship can be regarded as), and done additions and deletions by the related content relying on parent table change operation when merging---than (4) planting and (5) kind scene as elucidated before, so rely on sublist and also should make corresponding amendment, to continue to meet original dependence; Plant in scene from the dependence added as external key for (6), if relied on certainly adding of parent table to add when merging the fixed value that is avoided constraint conflict, the associated column so relying on sublist also needs to add identical fixed value when merging.
(8) there is successively dependence in some database or table on merge order, needs to specify a priority level to it.Under default situations, in order to improve the speed of merging, for other table of same priority, merging device and should carry out the merging treatment of multilist with concurrent fashion, between these tables, there is not whose order first after whom; If some table specifies higher priority, then first should merge, after all forms merge under treating this priority, just can carry out the merging flow process of the lower table of priority.
(9) some table employs trigger, needs to determine whether forbidding trigger according to the difference of service logic.Such as, in the application software had, the mode using trigger to add sequence is simulated from the effect added (not from the concept added in oracle), in corresponding table, often insert a record, will the logic of Automatically invoked trigger, revise the incrementing integers that its ID is sequence; When merging this table, if this table is not relied on by other tables, then can the function of trigger be that the record generation of merging increases progressively ID automatically in relieved application target database; If this table is relied on by other tables, then recommend temporarily to forbid the trigger in destination data storehouse, but use the mode described in (6) kind scene to carry out merge record, the flip-flop states in destination data storehouse is restored after merging, the benefit so done is when merging dependence sublist, only need simply to add identical fixed value to the associated column relying on sublist, efficiency is higher, and treatment scheme is also simpler.
(10) some structure showing to define in source database and destination data storehouse is inconsistent, and the flow process of the acquiescence converting source data database table structure of merging treatment device cannot adapt to service logic, needs user oneself to realize flow path switch.
For the special processing scene of several merging of appeal, need user in " consolidation strategy ", indicate consolidation strategy definition corresponding to concrete table, do not specify the table of consolidation strategy, then give tacit consent to and all records shown in source database are all appended to inside the table in destination data storehouse.
In addition, above various application scenarios, in most cases, just can realize by performing sql statement, the testing process before merging under such as the first scene, usually only needing to perform some inter-library Connection inquiring can judge; If but source database and destination data storehouse be not in same data base management system (DBMS), sql statement is then used merely to be difficult to realize this measuring ability, also need user to go to realize special " merging plug-in unit " and carried out this function, the difficulty merging device will be used by adding users like this; Therefore, in order to simplify merging process, making user only need to understand sql knowledge as far as possible and just can complete most of pooling function, just needing source database and destination data storehouse to be incorporated in same data base management system (DBMS), therefore, first step during this merging device busy is:
Merge device and create an interim image database in the data base management system (DBMS) at place, destination data storehouse, by Backup and Restore function (or other data migration methods), source database is returned in this interim image database, then with this interim image database as source database.Access originator and destination data storehouse while of this makes it possible to allow user in sql statement.
For several scene needing the special merging flow process of specifying " consolidation strategy " recited above, this merging device sums up corresponding consolidation strategy, and its function is built in " merging treatment device ", for user with various configuration file for carrier sets " consolidation strategy " of some special list.Mainly contain following several consolidation strategy:
(1) database policies, specifies the database-name needing to participate in merging, if there is multiple database to need to merge, then needs to configure many database policies.This strategy comprises following content:
1. source database title;
2. destination data library name;
3. priority level, optional, if assigned priority is not other, be defaulted as minimum rank; Because the merging of database finally all will be converted into the merging of the daughter element of database, therefore the setting value of database priority, can be inherited by its daughter element, the daughter element that priority is high first merges, merge after the daughter element that priority is low, the daughter element of equal priority can concurrently merge.
Provide the example of an xml configuration below:
--database policies: specify the source and destination database-name-> needing to participate in merging
<databasesource＝”db1”destination＝"db1">
</database>
--level assigned priority is other, and it is higher to be worth more large level, does not specify, is defaulted as 0-->
<databasesource＝”db2”destination＝"db2"level＝"1">
</database>
(2) inspection policies, optional, configurable multiple inspection policies, comprises following content:
1. policy name, optional; Some " merging plug-in unit " may need to identify this title, realizes different treatment schemees according to the difference of this title;
2. the information do not passed through is detected, for " merging treatment device " log or be shown to user;
3. sql statement, child node, optional, configurable multiple child node, agreement returns certain value and is and detects unsuccessfully;
Attention: sql is needed to stress, user configured sql needs access originator database and destination data storehouse simultaneously in most cases, but because this merging device is to replace source database with interim image database, so real source database title should be interim image database-name, conflict in order to avoid bearing the same name appears in ephemeral data library name and the database-name in destination data storehouse (cannot create in a data base management system (DBMS) two of the same name database), merge device certain algorithm can be used to generate title that certain unique string is used as this interim image database, unforeseen for user, when therefore specifying source database title in sql statement, do not use real database-name, but replace in macrodefined mode, such as use %SOURCE (db1) % to represent the interim image database-name of source database db1, this macro definition can be replaced with actual database-name when performing sql by " merging treatment device " automatically.
4. merge plugin name, optional, for when sql statement cannot detect, " the merging plug-in unit " that realize for " merging treatment device " invoke user detects; Under normal circumstances, merging plugin name is the secondary development class name that user realizes.
And 4. 3. can optional one, also can exist, any one returns failure simultaneously, then represent and detect unsuccessfully.
This strategy is for this paper scene (1) needing special processing recited above.Provide the example of an xml configuration below:
(3) the nonjoinder strategy shown, is the child node of database policies, comprises following content:
1. table name claims, and specifies the concrete table that this strategy is corresponding;
2. policing type is " nonjoinder " type.
This strategy is for this paper scene (2) needing special processing recited above, and the table of specifying does not participate in merging, and only retains the same famous-brand clock data in destination data storehouse.Provide the example of an xml configuration below:
(4) the revised context consolidation strategy shown, being the child node of database policies, for revising data to be combined in merging process, comprising following content:
1. table name claims, and specifies the concrete table that this strategy is corresponding;
2. policing type is " amendment " type;
3. priority level, optional, if assigned priority is not other, is defaulted as the priority level inheriting father node database, after the table that priority level is high has merged, the table that priority level is low could be merged.For the table having external key dependence, " merging treatment device " can automatically identify from the system table of data base management system (DBMS), and then Lookup protocol priority, can not need user to carry out priority setting.
4. sql statement, child node, optional, configurable multiple child node, for revising list structure in source database or destination data storehouse or data content (be not only confined to revise the table when pre-treatment, also can revise other association dependence tables);
5. merge plugin name, child node, optional, configurable multiple child node, for before merging when the complicated business logic that sql statement cannot process, merge plug-in unit process for merging secondary development that master routine invoke user realizes;
6. whether carried out by " merging treatment device " flow path switch that in source database and destination data storehouse, list structure is inconsistent, child node, optional.Be defaulted as "Yes", when this list structure is inconsistent in source database and destination data storehouse, carried out the structure shown in converting source data storehouse by " merging treatment device ", make it identical with the structure shown in destination data storehouse; If be "No", represent that this conversion has been come by user configured sql statement or " merging plug-in unit ", " merging treatment device " does not participate in flow path switch.
7. the merging flow process of data after whether being revised by " merging treatment device ", child node, optional, be defaulted as "Yes", represent after " merging treatment device " performs a series of user configured sql or " merging plug-in unit " revises data to be combined, " merging treatment device " table content the most at last in source database is simply appended in the same famous-brand clock in destination data storehouse; If be configured to "No", represent that the merging process of this table completes in user configured sql or " merging plug-in unit ", " merging treatment device " is no longer needed to participate in, for the service logic of some complexity, mode not by simply adding merges, then now can be masked the flow process of " merging treatment device " by this mode, carried out the merging flow process of some table leading completely by user;
8. from adding and corresponding sequence names, specify in current table which is classified as from adding, child node, optional.Certainly adding in physical definition, " merging treatment device " can be inquired about and identify from the system table of data base management system (DBMS), even if so user does not specify its concrete row title, also can automatically process; Under some scene, although certain row is not defined as from adding, it uses sequence or other service logic algorithms to realize similar certainly increasing function, and this situation of " merging treatment device " None-identified, therefore must specify respective column title by user; If employ sequence, also need specified sequence title, " merging treatment device " just can adopt some algorithm automatically to revise the value of these row according to this two each and every one information, to avoid violating the constraint from adding uniqueness, and the currency of synchronizing sequence;
9. from adding association external key sublist title and row title, be child node 7., optional, configurable multiple child node.If this table is relevant sublist also, maintained parent subrelation is carried out from the uniqueness added by parent table, then need to specify corresponding sublist title and row title in parent table strategy, merge master routine like this and automatically can revise when revising certainly the adding of master meter the foreign key column associating sublist;
10. the trigger title forbidden is needed, optional, child node, configurable multiple child node.Merge in the process of current table whether forbid appointment trigger by user according to service logic decision, merged its original state of rear recovery.
This device of the present invention can realize the flow process that general data-base content merges.Overall merging flow process has been come by merging master routine; For the form without the need to special processing, merge master routine acquiescence and the table record in source database is appended in the same famous-brand clock in destination data storehouse; For the form comprising the complicated business logical data merging master routine None-identified, in policy configuration file, specify its consolidation strategy by developer, merge master routine carries out data merging according to its consolidation strategy; In most application scenarios, developer only need configure some sql statements in policy configuration file can reach the object revising the table data that cannot directly merge, in extreme complicated application scenarios, developer can be incorporated into the secondary development plug-in unit that oneself coding realizes and merge in flow process; In addition, merge the treatment mechanism that device have employed concurrent thread, improve the processing speed merged.
The above is only the preferred embodiment of the present invention; it should be pointed out that for those skilled in the art, under the premise without departing from the principles of the invention; can also make some improvements and modifications, these improvements and modifications also should be considered as protection scope of the present invention.
Claims (13)
1. a data-base content merging method, is characterized in that, comprising:
Set up the mirror database that source database is corresponding, identical with described source database in described mirror database;
The consolidation strategy corresponding according to the source form in described mirror database, to the source form of described mirror database, the object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
2. the method for claim 1, is characterized in that, the described step setting up mirror database corresponding to source database comprises:
Backup source database, obtains the backup file carrying form data;
Choose the data base management system (DBMS) belonging to destination data storehouse;
In described data base management system (DBMS), set up mirror database corresponding to described source database, and the form data of carrying in described backup file is added in described mirror database.
3. the method for claim 1, it is characterized in that, the described consolidation strategy corresponding according to the source form in described mirror database, to the source form of described mirror database, with the object form needing in destination data storehouse to carry out with described source form merging, the step of carrying out form data merging comprises:
The consolidation strategy that source form in described mirror database in acquisition configuration file is corresponding;
When there being inspection policies in consolidation strategy, according to described inspection policies, choose sql statement and/or merge the form that plug-in unit detects in mirror database and destination data storehouse and can carry out form data merging, if detect successfully, then according to the form consolidation strategy in described consolidation strategy, to the source form of described mirror database, the object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
4. method as claimed in claim 3, it is characterized in that, according to the form consolidation strategy in described consolidation strategy, to the source form of described mirror database, with the object form needing in destination data storehouse to carry out with described source form merging, the step of carrying out form data merging comprises:
To obtain in mirror database the set of active form;
Set up in the set of source form the form needing to carry out with the object form in destination data storehouse merging, with the corresponding relation of form consolidation strategy;
According to priority order carries out form data merging to the object form in source form and destination data storehouse.
5. method as claimed in claim 4, it is characterized in that, the step of the object form in source form and destination data storehouse being carried out to form data merging comprises:
The form consolidation strategy that source form in the set of acquisition source form is corresponding;
If described form consolidation strategy is for specifying consolidation strategy and specifying consolidation strategy type for merging or being amendment strategy, then judge in destination data storehouse, whether to there is the object form of the same name with source form, if exist, then to source form and and source form object form of the same name carry out form data merging, otherwise, in destination data storehouse, create the object form of the same name with source form, then form data merging is carried out to source form and object form.
6. method according to claim 5, is characterized in that, the step of source form and object form being carried out to form data merging comprises:
Judge that whether source form is consistent with the list structure of object form, if, according to the appointment consolidation strategy of described source form, form data merging is carried out to source form and object form, otherwise, the list structure of source form is converted to consistent with the list structure of object form after, then according to the appointment consolidation strategy of described source form, form data merging is carried out to source form and object form.
7. method according to claim 6, is characterized in that, according to the appointment consolidation strategy of described source form, the step of source form and object form being carried out to form data merging comprises:
If described source form does not specify consolidation strategy, obtain the record sum of source form;
If the record sum of described source form is not 0, performs and insert statement, all records in the form of source are inserted in object form.
8. method according to claim 6, is characterized in that, according to the appointment consolidation strategy of described source form, the step of source form and object form being carried out to form data merging comprises:
If described source form has appointment consolidation strategy, then by appointment consolidation strategy, source form is modified, obtain the record of amended source form;
The record of this amended source form is inserted in object form.
9. method according to claim 8, is characterized in that, modifies to source form, and the step obtaining the record of amended source form comprises:
The record of the record or major key conflict of violating constraint rule in the form of described source is modified or deleted, obtains the record of amended source form; Or
To in the form of described source certainly add or sequence adds a fixed value, obtain the record of amended source form; Or
There is external key to described source form to rely on, when modifying to dependence parent table, dependence sublist also being carried out to the amendment of related content, obtaining the record of amended source form.
10. method according to claim 8, is characterized in that, the step that the record of this amended source form is inserted in object form is comprised:
If object form employs trigger and object form is not relied on by other table, then, when inserting the record of source form in object form, what utilize trigger automatically to generate record increases progressively ID; Otherwise when inserting the record of source form in object form, forbid described trigger, after at record, insertion completes, then to recover trigger be state before merging.
11. 1 kinds of data-base contents merge device, it is characterized in that, comprising:
Set up module, for setting up mirror database corresponding to source database, identical with described source database in described mirror database;
Merge module, for the consolidation strategy corresponding according to the source form in described mirror database, to the source form of described mirror database, the object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
12. devices as claimed in claim 11, is characterized in that, set up module and comprise:
Backup submodule, for backup source database, obtains the backup file carrying form data;
Connexon module, for choosing the data base management system (DBMS) belonging to destination data storehouse;
Setting up submodule, for setting up mirror database corresponding to described source database in described data base management system (DBMS), and the form data of carrying in described backup file being added in described mirror database.
13. devices as claimed in claim 11, is characterized in that, merge module and comprise:
Obtain submodule, for obtaining consolidation strategy corresponding to source form in the described mirror database in configuration file;
Merge submodule, for when there being inspection policies in consolidation strategy, according to described inspection policies, choose sql statement and/or merge the form that plug-in unit detects in mirror database and destination data storehouse and can carry out form data merging, if detect successfully, then according to the form consolidation strategy in described consolidation strategy, to the source form of described mirror database, object form with needing in destination data storehouse to carry out with described source form merging, carries out form data merging.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410339322.9A CN105320681B (en) | 2014-07-16 | 2014-07-16 | Database content merging method and device |
| PCT/CN2014/090271 WO2015117429A1 (en) | 2014-07-16 | 2014-11-04 | Method and device for merging database contents |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410339322.9A CN105320681B (en) | 2014-07-16 | 2014-07-16 | Database content merging method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105320681A true CN105320681A (en) | 2016-02-10 |
| CN105320681B CN105320681B (en) | 2020-06-30 |
Family
ID=53777244
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410339322.9A Active CN105320681B (en) | 2014-07-16 | 2014-07-16 | Database content merging method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105320681B (en) |
| WO (1) | WO2015117429A1 (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108205559A (en) * | 2016-12-19 | 2018-06-26 | 腾讯科技（深圳）有限公司 | A kind of data managing method and its equipment |
| CN110334098A (en) * | 2019-06-27 | 2019-10-15 | 烽火通信科技股份有限公司 | A kind of database combining method and system based on script |
| CN110532254A (en) * | 2018-05-25 | 2019-12-03 | 杭州海康威视数字技术股份有限公司 | The method and apparatus of fused data table |
| WO2020125537A1 (en) * | 2018-12-17 | 2020-06-25 | 中兴通讯股份有限公司 | Database component merge into function compatibility method, device and storage medium |
| US11500832B2 (en) * | 2016-12-19 | 2022-11-15 | Tencent Technology (Shenzhen) Company Limited | Data management method and server |
| CN117331963A (en) * | 2023-11-28 | 2024-01-02 | 恒生电子股份有限公司 | Data access processing method and device, electronic equipment and storage medium |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109254969A (en) * | 2018-08-31 | 2019-01-22 | 平安科技（深圳）有限公司 | Tables of data processing method, device, equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060161606A1 (en) * | 2005-01-19 | 2006-07-20 | Biswal Dilip K | Synchronization-replication concurrency using non-shared snapshot query on a history table at read-uncommitted isolation level |
| CN101355726A (en) * | 2007-07-25 | 2009-01-28 | 国际商业机器公司 | Method and system for synchronizing data base based on multimedia information transference |
| CN102591666A (en) * | 2012-01-04 | 2012-07-18 | 浪潮集团山东通用软件有限公司 | Metadata management method for version of hierarchy structure |
| CN103309997A (en) * | 2013-06-25 | 2013-09-18 | 上海航天测控通信研究所 | Internal and external network parallel running system for database merging and method of database merging |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8543540B1 (en) * | 2012-05-09 | 2013-09-24 | Bertec Corporation | System and method for the merging of databases |
| CN103077242B (en) * | 2013-01-11 | 2016-03-09 | 北京佳讯飞鸿电气股份有限公司 | The method of a kind of fulfillment database server two-node cluster hot backup |
-
2014
- 2014-07-16 CN CN201410339322.9A patent/CN105320681B/en active Active
- 2014-11-04 WO PCT/CN2014/090271 patent/WO2015117429A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060161606A1 (en) * | 2005-01-19 | 2006-07-20 | Biswal Dilip K | Synchronization-replication concurrency using non-shared snapshot query on a history table at read-uncommitted isolation level |
| CN101355726A (en) * | 2007-07-25 | 2009-01-28 | 国际商业机器公司 | Method and system for synchronizing data base based on multimedia information transference |
| CN102591666A (en) * | 2012-01-04 | 2012-07-18 | 浪潮集团山东通用软件有限公司 | Metadata management method for version of hierarchy structure |
| CN103309997A (en) * | 2013-06-25 | 2013-09-18 | 上海航天测控通信研究所 | Internal and external network parallel running system for database merging and method of database merging |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108205559A (en) * | 2016-12-19 | 2018-06-26 | 腾讯科技（深圳）有限公司 | A kind of data managing method and its equipment |
| US11500832B2 (en) * | 2016-12-19 | 2022-11-15 | Tencent Technology (Shenzhen) Company Limited | Data management method and server |
| CN110532254A (en) * | 2018-05-25 | 2019-12-03 | 杭州海康威视数字技术股份有限公司 | The method and apparatus of fused data table |
| WO2020125537A1 (en) * | 2018-12-17 | 2020-06-25 | 中兴通讯股份有限公司 | Database component merge into function compatibility method, device and storage medium |
| CN110334098A (en) * | 2019-06-27 | 2019-10-15 | 烽火通信科技股份有限公司 | A kind of database combining method and system based on script |
| CN117331963A (en) * | 2023-11-28 | 2024-01-02 | 恒生电子股份有限公司 | Data access processing method and device, electronic equipment and storage medium |
| CN117331963B (en) * | 2023-11-28 | 2024-03-08 | 恒生电子股份有限公司 | Data access processing method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2015117429A1 (en) | 2015-08-13 |
| CN105320681B (en) | 2020-06-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105320681A (en) | Database content combination method and device | |
| US11169784B2 (en) | Computing expression medium, development environment, and device communication and control architecture | |
| US10324909B2 (en) | Omega names: name generation and derivation utilizing nested three or more attributes | |
| US8769494B2 (en) | Globally sound and consistent configuration management for distributed datacenter components | |
| US10466998B2 (en) | Model based upgrade campaign generation | |
| CN103605518A (en) | Object deserialization method and device | |
| CN105683940A (en) | Processing a data flow graph of a hybrid flow | |
| US9830333B1 (en) | Deterministic data replication with conflict resolution | |
| US9483508B1 (en) | Omega names: name generation and derivation | |
| US10747643B2 (en) | System for debugging a client synchronization service | |
| US10970193B2 (en) | Debugging a client synchronization service | |
| CN104461531A (en) | Implementing method for self-defined functions of reporting system | |
| CN111767144A (en) | Transaction routing determination method, device, equipment and system for transaction data | |
| Huynh et al. | Automatic modularity conformance checking | |
| CN113515303B (en) | Project transformation method, device and equipment | |
| CN110941422B (en) | Code automatic generation method, code generator and readable storage medium | |
| CN101908174A (en) | Method, device and EAP (Enterprise Application Platform) system for processing part object information in drawing file | |
| CN111125996B (en) | Method for realizing instruction set based on bidirectional constraint tree of pseudo-random excitation generator | |
| US20200409669A1 (en) | Technique for transforming a standard messaging component to a customized component | |
| Flores et al. | A formal model of object-oriented design and GoF design patterns | |
| CN112799673B (en) | Network protocol data checking method and device | |
| US10853331B1 (en) | System and method for editing materializations of a data store | |
| CN104462108A (en) | Database structure object processing method and device | |
| US8656410B1 (en) | Conversion of lightweight object to a heavyweight object | |
| CN113157934A (en) | Knowledge graph origin processing method and system, electronic device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |