CN103744947A - Version-ID-related (version-identity-related) data reference processing method and system - Google Patents
Version-ID-related (version-identity-related) data reference processing method and system Download PDFInfo
- Publication number
- CN103744947A CN103744947A CN201310754669.5A CN201310754669A CN103744947A CN 103744947 A CN103744947 A CN 103744947A CN 201310754669 A CN201310754669 A CN 201310754669A CN 103744947 A CN103744947 A CN 103744947A
- Authority
- CN
- China
- Prior art keywords
- data
- document
- version
- current version
- revision
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Document Processing Apparatus (AREA)
Abstract
The invention provides a version-ID-related data reference processing method. The method comprises the steps of establishing a first document which contains original data, and the original data contain an original version ID which serves as a current vision ID; version-updating the first document and performing exchange of the current version ID. During every update, data of the new version can be added on the basis of retaining the original data, wherein the data of the new version contain a new current version ID, and the new current version ID is exchanged with the original version ID to become the current version ID of the data of the new version. The invention also provides a version-ID-related data reference processing method. According to the version-ID-related data reference processing method and system, the current version ID of the data of a latest document version maintains unchanged, so that the coding difficulty and the workload of other documents for referring the data of the latest version of the first document can be reduced.
Description
Technical field
The present invention relates to areas of information technology, particularly relate to a kind of disposal route and system that relates to the data referencing of revision ID.
Background technology
In need to recording the scene of version or log history, the mode of data referencing and inquiry directly affects work efficiency.When historical record data is quoted or inquired about, that generally quote is current version ID.And in traditional version processing procedure, the current version ID that difference records version is different.As, in a customer data document along with the renewal of document version, the redaction that can produce, the data of redaction have new current version ID, as shown in table 1:
Table 1: customer data document
| Customer name | Contact person | Version number | Current version ID | Main revision ID |
| JinDie Software | Zhang San | 1.0 | 1001 | 1001 |
| JinDie Software | Li Si | 2.0 | 1002 | 1001 |
| JinDie Software | King five | 3.0 | 1003 | 1001 |
| JinDie Software | Zhao six | n.0 | …… | 1001 |
When other documents are quoted above-mentioned document, need to set up reference field and quote current version ID.For example a contract data document need to be quoted the data message in customer data document, and the current version ID of the data of the document version of field his-and-hers watches 1 quotes by reference, as shown in table 2, and wherein the reference field of table 2 is " Customer ID ".
Table 2: contract data document
| Contract NO | Contract date | Customer ID |
| ORDER-01 | 2004-01-01 | 1001 |
| ORDER-02 | 2005-01-01 | 1002 |
| ORDER-03 | 2006-01-01 | 1003 |
| ORDER-04 | 2007-01-01 | …… |
Adopt this traditional version disposal route realize to data quote with view procedure in, reference field can only be pointed to the data of fixing document version, can not upgrade along with the renewal of document version.Want to allow reference field quote the data of up-to-date document version, need to upgrade whole contracts card, this is unpractical in production environment.
In this case, check or quote latest data record, just need to pass through current version ID version query this shop, and by version number is sorted and finds latest edition, then open latest edition page of data.Thisly quote or check that mode process is loaded down with trivial details, workload also can significantly increase.If form or inquiry etc. need to obtain data by structured query sentence time, cannot complete inquiry by a structured query sentence, increased code and write difficulty.
Summary of the invention
Based on this, be necessary for the problems referred to above, provide a kind of and can reduce the disposal route that code is write the data referencing that relates to revision ID of difficulty and workload.
A kind of disposal system that relates to the data referencing of revision ID is also provided.
A disposal route that relates to the data referencing of revision ID, comprises the following steps: set up the first document, described the first document comprises raw data, and described raw data comprises that prototype version ID is as current version ID; Described the first document is carried out to version updating, revision ID exchange before the trade of going forward side by side; During each renewal, can on the basis that retains raw data, add the data of redaction, the data of described redaction comprise a new current version ID, by described new current version ID and described prototype version ID exchange, make described prototype version ID become the current version ID of the data of described redaction; Set up the second document, described the second document comprises at least one group of data, every group of data include reference field, described reference field when quoting the second document described in described the first document typing described in the current version ID of data of document version of the first document last update; By described reference field, obtain and check the data of described the first document.
Therein in an embodiment, described step of carrying out current version ID exchange, be by the current version ID of the data of this version updating, go forward side by side before the trade after revision ID exchange with a front version updating, this current version ID of data of a front upgraded edition exchanges.
Therein in an embodiment, describedly by described reference field, obtain and check in the step of data of described the first document, described by described reference field obtain and the data of checking described the first document for to realize by structured query sentence.
Therein in an embodiment, the major key that described current version ID is database.
A disposal system that relates to the data referencing of revision ID, comprising: the first document is set up module, and for setting up the first document, described the first document comprises raw data, and described raw data comprises that prototype version ID is as current version ID; Update module, for carrying out version updating to described the first document; The data of redaction are added in each renewal meeting on the basis that retains raw data, and the data of described redaction comprise a new current version ID; Switching Module, for carrying out current version ID exchange, described Switching Module, by described new current version ID and described prototype version ID exchange, makes described prototype version ID become the current version ID of the data of described redaction; The second document is set up module, for setting up the second document; Described the second document comprises at least one group of data, and every group of data include reference field, described reference field when quoting the second document described in described the first document typing described in the current version ID of data of document version of the first document last update; Check module, for obtain and check the data of described the first document by described reference field.
Therein in an embodiment, described Switching Module carries out current version ID exchange, be by the current version ID of the data of this version updating, go forward side by side before the trade after revision ID exchange with a front version updating, this current version ID of data of a front upgraded edition exchanges.。
Therein in an embodiment, described in check that module is obtained by described reference field and the data of checking described the first document for to realize by structured query sentence.
Therein in an embodiment, the major key that described current version ID is database.
Above-mentioned disposal route and the system that relates to the data referencing of revision ID, by the first document of setting up being carried out to version updating and current version ID and the described prototype version ID of the data of the document version after upgrading being exchanged, make the current version ID of the data of up-to-date document version remain constant.Thereby the reference field in the second document by reference this current revision ID is quoted the latest data of the first document, and need not upgrade whole the second document, has reduced code and write difficulty and workload when meeting form demand.
Accompanying drawing explanation
Fig. 1 is the process flow diagram that relates to version updating in the disposal route of data referencing of revision ID in an embodiment;
Fig. 2 is the process flow diagram that relates to data referencing in the disposal route of data referencing of revision ID in an embodiment;
Fig. 3 is the process flow diagram of disposal route that relates to the data referencing of revision ID in a specific embodiment;
Fig. 4 is the theory diagram of the disposal system of data referencing in an embodiment.
Embodiment
In order to make object of the present invention, technical scheme and advantage clearer, below in conjunction with drawings and Examples, the present invention is further elaborated.Should be appreciated that specific embodiment described herein, only in order to explain the present invention, is not intended to limit the present invention.
As shown in Figure 1, in one embodiment, a kind of disposal route that relates to the data referencing of revision ID, comprises the following steps;
Step S110, sets up the first document.
The first document of setting up comprises raw data.Raw data comprises current version ID.Current version ID is for distinguishing the different editions of the first document.Therefore,, in the first document of foundation, each version is to there being the current version ID of oneself, and current version ID is not reproducible.In the present embodiment, the raw data of the first document of foundation also comprises main revision ID.Main revision ID is for the first document is identified, and therefore, in the different editions of the first document, main revision ID remains constant.Current version ID can identify the first document version, and therefore, current version ID can be database major key, a field that can unique each record of identification in database table.In the present embodiment using prototype version ID corresponding to raw data as current version ID.
S120, carries out version updating to the first document.
After the first document is set up, because the data of document are continuous updatings, need to synchronously upgrade the first document, therefore can produce new version.The data of new version are added on the basis of raw data that retains the first document, realize the version updating to the first document.Wherein, the data of the redaction of interpolation comprise a new current version ID.
S130, carries out current version ID exchange to the first document.
The first document is being carried out after version updating, on the basis of raw data, adding after the data of redaction, in the data of redaction, comprising a new current version ID.The first document is carried out to current version ID exchange, and the current version ID and the prototype version ID that are about to the data of redaction exchange, and make prototype version ID become the current version ID of the data of redaction.
In the present embodiment, the first document is carried out to current version ID exchange, complete once to after the renewal of the first document, when having the data of redaction to produce, repeated execution of steps S120 and S130 again, guarantee all current version ID to be exchanged after each version updating, make the current version ID of the data of up-to-date document version remain constant.Particularly, carrying out current version ID exchange is by the current version ID of the data of this version updating, goes forward side by side before the trade after revision ID exchange with a front version updating, and this current version ID of data of a front upgraded edition exchanges.In the time need to the data of the first document being quoted or be checked, the current version ID of data that can be by the document version to up-to-date quotes, and guarantees that reference data is up-to-date data always.And need to after document version updating, the whole document of quoting not upgraded, and by a structured query sentence, can complete the data of the up-to-date document version of the first document are quoted and inquired about, reduced workload and code is write difficulty., the current version ID of the data of document version is exchanged meanwhile, do not affect the existence of history release, can keep the function of version management.
In other embodiment, as shown in Figure 2, the above-mentioned disposal route that relates to the data referencing of revision ID also comprises step:
S140, sets up the second document.
The second document need to be quoted the data of the first document.In the present embodiment, the data of the first document are quoted is the data of quoting the document version of the first document last update to the second document.Therefore, the second document of foundation at least comprises one group of data, and every group of data all comprise that reference field is for quoting the data of the up-to-date document version of the first document.When particularly, reference field is quoted first document typing the second document, be the current version ID of the data of the document version of the first document last update by reference.Because the first document can upgrade version, and what after upgrading, meeting was corresponding exchanges current version ID, make the current version ID of the data of up-to-date document version remain constant, therefore, the reference field of second document can be pointed to the data of the up-to-date document version of the first document all the time, and need not to the second document, carry out update all because of the renewal of the first document, and reduced workload, also reduced the code coding difficulty of reference field.
S150, the data of the first document are obtained and checked to field by reference.
In the present embodiment, field can complete the data of the first document are quoted by reference.Meanwhile, by structured query sentence, can the data of the first document be obtained and be checked.That quote due to reference field is the current version ID of data of the up-to-date document version of the first document, and its current version ID remains constant, therefore by structured query sentence, the data of the first document is being obtained and is being checked.And in view procedure, only need to can realize by a structured query sentence, reduce greatly the difficulty that code is write, also improve obtaining and search efficiency the data of the first document.
The above-mentioned disposal route that relates to the data referencing of revision ID, by the first document of setting up being carried out to version updating and by the current version ID of the data of the document version after upgrading, with a front version updating and carry out after version exchange, the current version ID of the data of a front version exchanges, and makes the current version ID of the data of up-to-date document version remain constant.Thereby the reference field in the second document by reference this current revision ID is quoted the latest data of the first document, and need not upgrade whole the second document, has reduced code and write difficulty and workload when meeting form demand.
Below in conjunction with a concrete application scenarios in Fig. 3, the above-mentioned disposal route that relates to the data referencing of revision ID is further described in detail.
S310, sets up customer data document.
Set up a customer data document, at this document, comprise raw data.Raw data comprises current version ID and main revision ID.In the present embodiment, the current version ID of the raw data of customer data document is prototype version ID.The raw data of the customer data document of setting up is as shown in table 3:
Table 3: the raw data of customer data document
| Customer name | Contact person | Version number | Current version ID | Main revision ID |
| JinDie Software | Zhang San | 1.0 | 1001 | 1001 |
That is, in the present embodiment, current version ID corresponding to raw data is 1001.
S320, carries out version updating to customer data document.
Because customer data is not unalterable, but constantly update.After each renewal, all can produce a redaction.The redaction producing comprises a new current version ID.It is on the basis of raw data, to add the data of redaction that document is carried out to version updating.Table 4 is for to carry out the result after version updating to customer data document.
Table 4: customer data document is carried out to the result after version updating
| Customer name | Contact person | Version number | Current version ID | Main revision ID |
| JinDie Software | Zhang San | 1.0 | 1001 | 1001 |
| JinDie Software | Li Si | 2.0 | 1002 | 1001 |
In the present embodiment, the current version ID of the data of redaction is 1002.
S330, exchanges the current version ID of customer data document.
The current version ID of the data of redaction and prototype version ID are exchanged and preserved.The result of carrying out after current version ID exchange is as shown in table 5:
Table 5: the result after current version ID is exchanged
| Customer name | Contact person | Version number | Current version ID | Main revision ID |
| JinDie Software | Zhang San | 1.0 | 1002 | 1001 |
| JinDie Software | Li Si | 2.0 | 1001 | 1001 |
Now, the current version ID of the data of up-to-date version is 1001.
In the present embodiment, need to make the current version ID of the data of up-to-date document version remain constant to each redaction execution step S320 and S330 of producing, be 1001.In the time need to the data of the first document being quoted or be checked, the current version ID of data that can be by the document version to up-to-date quotes, and guarantees that reference data is up-to-date data always.And need to after document version updating, the whole document of quoting not upgraded, and by a structured query sentence, can complete the data of the up-to-date document version of the first document are quoted and inquired about, reduced workload and code is write difficulty., the current version ID of the data of document version is exchanged meanwhile, do not affect the existence of history release, can keep the function of version management.
Customer data document is being carried out to after version updating and current version ID exchange, can also comprise step S340 and S350.
S340, sets up contract data document.
The contract data document of setting up need to be quoted the customer data of aforementioned foundation, and need to quote the data of its up-to-date document version.Contract data document comprises multi-group data, and every group of data all comprise that a reference field quotes for the data to customer data.In the present embodiment, reference field is " Customer ID " field.The reference field by reference current version ID of the data of the up-to-date document version of customer data is quoted, and the contract data of foundation is as shown in table 6:
Table 6: the contract data document of foundation
| Contract NO | Contract date | Customer ID |
| ORDER-01 | 2004-01-01 | 1001 |
| ORDER-02 | 2005-01-01 | 1001 |
| ORDER-03 | 2006-01-01 | 1001 |
| ORDER-04 | 2007-01-01 | 1001 |
By the current version ID of the data of customer data document version being exchanged to the current version ID of the data that make up-to-date document version, remain constant.Therefore, the current version ID of the data of the document version that reference field in contract data document is up-to-date by reference quotes customer data, can quote all the time up-to-date customer data, and need not upgrade whole contract data document, when meeting form demand, reduce code and write difficulty and workload.
S350, customer data document is obtained and checked to field by reference.
In the present embodiment, field can complete the data of customer data document are quoted by reference.While colluding, cross the data that structured query sentence can customer data document and obtain and check.That quote due to reference field is the current version ID of data of the up-to-date document version of customer data document, its current version ID remains constant, therefore by structured query sentence, the data of customer data document are obtained and view procedure in, only need to can realize by a structured query sentence, reduce greatly the difficulty that code is write, also improved obtaining and search efficiency the data of the first document.
As shown in Figure 4, provide a kind of disposal system that relates to the data referencing of revision ID.A kind of disposal system that relates to the data referencing of revision ID comprises that the first document sets up module 402, update module 404 and Switching Module 406.
The first document is set up module 402 for setting up the first document.The first document that the first document is set up module 402 foundation comprises raw data.Raw data comprises that prototype version ID is as current version ID.Current version ID is for distinguishing the different editions of the first document.Therefore,, in the first document of foundation, each version is to there being the current version ID of oneself, and current version ID is not reproducible.Therefore, current version ID can be database major key, a field that can unique each record of identification in database table.
Update module 404 is for carrying out version updating to the first document.At the first document, set up module 402 and set up after the first document, because the data of document are continuous updatings, need to synchronously upgrade the first document, therefore can produce redaction.Update module 404 is added the data of redaction on the basis of raw data that retains the first document, realizes the version updating to the first document.Wherein, the data of the redaction of interpolation comprise a new current version ID.
Switching Module 406 is for carrying out current version ID exchange.At 404 pairs of the first documents of update module, carry out after version updating, on the basis of raw data, add after the data of redaction, in the data of redaction, comprised a new current version ID.Therefore, Switching Module 406 exchanges the current version ID of the data of redaction and prototype version ID, makes prototype version ID become the current version ID of the data of redaction.
In the present embodiment, 406 pairs of the first documents of Switching Module carry out current version ID exchange, complete once to after the renewal of the first document, when having the data of redaction to produce, 404 pairs of the first documents of update module carry out version updating, Switching Module 406 carries out current version ID exchange, guarantees all current version ID to be exchanged after each version updating, makes the current version ID of the data of up-to-date document version remain constant.Particularly, Switching Module 406 carries out current version ID exchange, is by the current version ID of the data of this version updating, goes forward side by side before the trade after revision ID exchange with a front version updating, and this current version ID of data of a front upgraded edition exchanges.In the time need to the data of the first document being quoted or be checked, the current version ID of data that can be by the document version to up-to-date quotes, and guarantees that reference data is up-to-date data always.And need to after document version updating, the whole document of quoting not upgraded, and by a structured query sentence, can complete the data of the up-to-date document version of the first document are quoted and inquired about, reduced workload and code is write difficulty., the current version ID of the data of document version is exchanged meanwhile, do not affect the existence of history release, can keep the function of version management.
In other embodiments, the above-mentioned disposal system that relates to the data referencing of revision ID can also comprise that the second document sets up module and enquiry module.
The second document is set up module for setting up the second document.The second document need to be quoted the data of the first document.In the present embodiment, the data of the first document are quoted is the data of quoting the up-to-date document version of the first document to the second document.Therefore, the second document that the second document is set up module foundation at least comprises one group of data, and every group of data all comprise that reference field is for quoting the data of the up-to-date document version of the first document.When particularly, reference field is quoted first document typing the second document, be the current version ID of the data of the document version of the first document last update by reference.Owing to can version being upgraded in the first document, and what after upgrading, meeting was corresponding exchanges current version ID, make the current version ID of the data of up-to-date document version remain constant, therefore, the reference field of second document can be pointed to the data of the up-to-date document version of the first document all the time, and need not to the second document, carry out update all because of the more capable of the first document, and reduced workload, also reduced the code coding difficulty of reference field.
The data of enquiry module for obtaining and check described the first document by described reference field.In the present embodiment, field can complete the data of the first document are quoted by reference.Meanwhile, by structured query sentence, can the data of the first document be obtained and be checked.That quote due to reference field is the current version ID of data of the up-to-date document version of the first document, its current version ID remains constant, therefore by structured query sentence, the data of the first document are obtained and view procedure in, only need to can realize by a structured query sentence, reduce greatly the difficulty that code is write, also improved obtaining and search efficiency the data of the first document.
The above embodiment has only expressed several embodiment of the present invention, and it describes comparatively concrete and detailed, but can not therefore be interpreted as the restriction to the scope of the claims of the present invention.It should be pointed out that for the person of ordinary skill of the art, without departing from the inventive concept of the premise, can also make some distortion and improvement, these all belong to protection scope of the present invention.Therefore, the protection domain of patent of the present invention should be as the criterion with claims.
Claims (8)
1. a disposal route that relates to the data referencing of revision ID, comprises the following steps:
Set up the first document, described the first document comprises raw data, and described raw data comprises that prototype version ID is as current version ID;
Described the first document is carried out to version updating, revision ID exchange before the trade of going forward side by side; During each renewal, can on the basis that retains raw data, add the data of redaction, the data of described redaction comprise a new current version ID, by described new current version ID and described prototype version ID exchange, make described prototype version ID become the current version ID of the data of described redaction;
Set up the second document, described the second document comprises at least one group of data, every group of data include reference field, described reference field when quoting the second document described in described the first document typing described in the current version ID of data of document version of the first document last update;
By described reference field, obtain and check the data of described the first document.
2. the disposal route that relates to the data referencing of revision ID according to claim 1, it is characterized in that, described step of carrying out current version ID exchange, by the current version ID of the data of this version updating, go forward side by side before the trade after revision ID exchange with a front version updating, this current version ID of data of a front upgraded edition exchanges.
3. the disposal route that relates to the data referencing of revision ID according to claim 1, it is characterized in that, describedly by described reference field, obtain and check in the step of data of described the first document, described by described reference field obtain and the data of checking described the first document for to realize by structured query sentence.
4. the disposal route that relates to the data referencing of revision ID according to claim 1, is characterized in that, the major key that described current version ID is database.
5. a disposal system that relates to the data referencing of revision ID, is characterized in that, comprising:
The first document is set up module, and for setting up the first document, described the first document comprises raw data, and described raw data comprises that prototype version ID is as current version ID;
Update module, for carrying out version updating to described the first document; The data of redaction are added in each renewal meeting on the basis that retains raw data, and the data of described redaction comprise a new current version ID;
Switching Module, for carrying out current version ID exchange, described Switching Module, by described new current version ID and described prototype version ID exchange, makes described prototype version ID become the current version ID of the data of described redaction;
The second document is set up module, for setting up the second document; Described the second document comprises at least one group of data, and every group of data include reference field, described reference field when quoting the second document described in described the first document typing described in the current version ID of data of document version of the first document last update;
Check module, for obtain and check the data of described the first document by described reference field.
6. the disposal system that relates to the data referencing of revision ID according to claim 5, it is characterized in that, described Switching Module carries out current version ID exchange, by the current version ID of the data of this version updating, go forward side by side before the trade after revision ID exchange with a front version updating, this current version ID of data of a front upgraded edition exchanges.
7. the disposal system that relates to the data referencing of revision ID according to claim 5, is characterized in that, described in check that module is obtained by described reference field and the data of checking described the first document for to realize by structured query sentence.
8. the disposal system that relates to the data referencing of revision ID according to claim 5, is characterized in that, the major key that described current version ID is database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310754669.5A CN103744947B (en) | 2013-12-31 | 2013-12-31 | It is related to the processing method and system of the data referencing of revision ID |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310754669.5A CN103744947B (en) | 2013-12-31 | 2013-12-31 | It is related to the processing method and system of the data referencing of revision ID |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103744947A true CN103744947A (en) | 2014-04-23 |
| CN103744947B CN103744947B (en) | 2017-12-12 |
Family
ID=50501965
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310754669.5A Active CN103744947B (en) | 2013-12-31 | 2013-12-31 | It is related to the processing method and system of the data referencing of revision ID |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103744947B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110019179A (en) * | 2017-07-31 | 2019-07-16 | 北京嘀嘀无限科技发展有限公司 | Update method and device, the electronic equipment, storage medium of index database |
| CN112068894A (en) * | 2019-05-23 | 2020-12-11 | 华为技术有限公司 | Configuration object processing method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1315017A (en) * | 1998-08-19 | 2001-09-26 | 埃默里有限公司 | Difference extraction between two versions of data-tables containing intra-reference |
| US20070006137A1 (en) * | 2005-06-30 | 2007-01-04 | Uday Savagaonkar | Generating and communicating information on locations of program sections in memory |
| CN102819565A (en) * | 2012-07-09 | 2012-12-12 | 梁振宇 | System and method for automatically generating freely customized numbers |
| CN102957814A (en) * | 2011-08-18 | 2013-03-06 | ***通信集团江苏有限公司 | Method and system for realizing character color ring back tone |
-
2013
- 2013-12-31 CN CN201310754669.5A patent/CN103744947B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1315017A (en) * | 1998-08-19 | 2001-09-26 | 埃默里有限公司 | Difference extraction between two versions of data-tables containing intra-reference |
| US20070006137A1 (en) * | 2005-06-30 | 2007-01-04 | Uday Savagaonkar | Generating and communicating information on locations of program sections in memory |
| CN102957814A (en) * | 2011-08-18 | 2013-03-06 | ***通信集团江苏有限公司 | Method and system for realizing character color ring back tone |
| CN102819565A (en) * | 2012-07-09 | 2012-12-12 | 梁振宇 | System and method for automatically generating freely customized numbers |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110019179A (en) * | 2017-07-31 | 2019-07-16 | 北京嘀嘀无限科技发展有限公司 | Update method and device, the electronic equipment, storage medium of index database |
| CN112068894A (en) * | 2019-05-23 | 2020-12-11 | 华为技术有限公司 | Configuration object processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103744947B (en) | 2017-12-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103377336B (en) | The control method of a kind of computer system user authority and system | |
| CN111951101B (en) | Data checking method and device | |
| CN104216893A (en) | Partitioned management method for multi-tenant shared data table, server and system | |
| CN101908040A (en) | Data report system | |
| CN105808653B (en) | A kind of data processing method and device based on user tag system | |
| CN106933836B (en) | Data storage method and system based on sub-tables | |
| CN102521412A (en) | Data association device and data association method | |
| CN105787058B (en) | A kind of user tag system and the data delivery system based on user tag system | |
| CN106021207A (en) | A patent writing system and method | |
| CN103064757A (en) | Method and system for backing up data | |
| CN105095392B (en) | A kind of method and device of Data Mart data sharing | |
| CN101452556A (en) | Customer information processing system and method | |
| CN105069138A (en) | Association analysis system and method | |
| CN106997369B (en) | Data cleaning method and device | |
| CN116521956A (en) | Graph database query method and device, electronic equipment and storage medium | |
| CN114022188A (en) | Target crowd circling method, device, equipment and storage medium | |
| US10332046B2 (en) | Social workflow engine | |
| CN107656943B (en) | Task query method and server | |
| US20210216516A1 (en) | Management of a secondary vertex index for a graph | |
| CN103744947A (en) | Version-ID-related (version-identity-related) data reference processing method and system | |
| CN114240344A (en) | Enterprise personnel data processing method and device, computer equipment and storage medium | |
| CN106095511A (en) | A kind of server updating method and apparatus | |
| CN106503166A (en) | Date storage method and device | |
| CN106372121B (en) | Server and data processing method | |
| CN101609462B (en) | Task recognition system in spatial environment of personal data and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |