CN101174204A - Device for upgrading data version - Google Patents

Device for upgrading data version Download PDF

Info

Publication number
CN101174204A
CN101174204A CNA2006101504523A CN200610150452A CN101174204A CN 101174204 A CN101174204 A CN 101174204A CN A2006101504523 A CNA2006101504523 A CN A2006101504523A CN 200610150452 A CN200610150452 A CN 200610150452A CN 101174204 A CN101174204 A CN 101174204A
Authority
CN
China
Prior art keywords
version
upgrading
data
database
transition
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.)
Withdrawn
Application number
CNA2006101504523A
Other languages
Chinese (zh)
Inventor
刘民
王瑞丰
武银成
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CNA2006101504523A priority Critical patent/CN101174204A/en
Publication of CN101174204A publication Critical patent/CN101174204A/en
Withdrawn legal-status Critical Current

Links

Images

Landscapes

  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention provides a data version upgrading device, which comprises a version write-in module used for writing a lower version database and a version transition bank into a software system, and an upgrading agent module used for guiding a lower version data into a high version database to be upgraded to the high version database. The upgrading agent module comprises a database version number reading unit used for reading the version number of the lower version database and a version database, a high version database establishing unit used for changing the name of the lower version database and establishing a high version database, a transition rule reading unit used for establishing the rule function and the storage process used in the version upgrading process and reading all transition rules, and an upgrading unit used for upgrading each sheet and feeding back the upgrading state information of all sheets after the datum of all the sheets are led into. Through the invention, the datum can be smoothly upgraded, and the system structure is clear and is simple to be realized.

Description

The device of data version upgrading
Technical field
The present invention relates to a kind of device of data version upgrading, more specifically, relate to a kind of device that is applicable to computing machine, the communications field etc. based on the data smoothing upgrading of the software systems of large-scale database system.
Background technology
In existing software systems, have much is to serve as that the relevant configuration data of management system operation and other data are come in the basis with large-scale database system (such as ORACLE, SQL SERVER, SYBASE, DB2 etc.), but because software product always constantly pushes away and brings out a new edition, and the release of redaction each time all may relate to the variation of data structure and the variation of related data algorithm, so will inevitably the smooth upgrade of legacy data be claimed.And at present a lot of software products need provide special upgrading handbook when upgrading, and the ROMPaq of write specialized processes, and such implementation not only workload is big, and extendability, dirigibility, maintainability are all very poor.In addition, though being arranged, some software products made certain improvement, but each redaction all wants correspondence to write corresponding SQL upgrade script file, by the upgrading of calling fulfillment database step by step to the SQL script file, the shortcoming of doing like this is to safeguard the upgrade script file of a large amount of complexity, be difficult for understanding and maintainable relatively poor, increased the possibility of upgrading failure.
Summary of the invention
Therefore, the present invention proposed be that workload of the prior art is big in order to overcome, shortcomings such as extendability, dirigibility and maintainable difference, realization is the data updating method of core with the general version transition storehouse of a cover, this method can be embedded in the installation procedure of software during application, when installing, software systems realize the smooth upgrade of data, thereby, can switch to redaction smoothly after feasible upgrading is finished.Like this, in daily performance history, only need the simple relatively transition rule of a rule in the maintenance release transition storehouse to get final product, improved exploitation and maintenance efficiency greatly.
One aspect of the present invention provides a kind of implementation method of data version upgrading, and it comprises: lowest version database and the version transition storehouse from the lowest version to the highest version are written to software systems; And according to pre-defined rule, with the lowest version data importing in the highest version database, thereby with the lowest version database upgrade to the highest version database.
According to an aspect of the present invention, version transition storehouse comprises the version upgrade file that exists with the tables of data form, comprising upgrading rule and the method between each version and the last version.
According to an aspect of the present invention, the version upgrade file comprise following one of at least: version information table, transition rule table and the function and the storing process information that realize transition rule.
According to an aspect of the present invention, the transition rule table is kept at the data transition rule in the data version upgrading process, and the data transition rule is relatively independent.
In the present invention, pre-defined rule comprises: reading database version number, version database this shop comprise the version number of lowest version database to be upgraded and the highest version database that will be upgraded to; The lowest version database is renamed, create the highest version database; In the highest version database, create rule function and the storing process information that will use in the edition upgrading that defines in the version transition storehouse, read in the transition rule table all transition rules between two versions; And each table upgraded, after the data of all tables of import, return the upgrade status information of all tables.
In the above-mentioned process that every table is upgraded, may further comprise the steps: import and carry out the required master data of upgrading; According to the transition rule of every table, call the differentiation file and carry out the variation and the upgrading of data; And the upgrade status information that writes down every table.
Wherein, upgrade status information comprise escalate into merit information and the upgrading failure information.
In the present invention, if return the upgrading successful information, then upgrading finishes.If return the upgrading failure information, then return to the preceding lowest version database of upgrading.
Another aspect of the present invention provides a kind of implement device of data version upgrading, and it comprises: the version writing module is used to write lowest version database and the version transition storehouse from the lowest version to the highest version to software systems; And the upgrading proxy module, be used for the lowest version data importing being upgraded to the highest version database to the highest version database.
According to an aspect of the present invention, in the version writing module, version transition storehouse comprises the version upgrade file that exists with the tables of data form, comprising upgrading rule and the method between each version and the last version.
According to an aspect of the present invention, the version upgrade file comprise following one of at least: version information table, transition rule table and the function and the storing process information that realize transition rule.Wherein, the transition rule table is kept at the data transition rule in the data version upgrading process, and the data transition rule is relatively independent.
In the present invention, the upgrading proxy module comprises: version database this shop reading unit, be used for reading database version number, and version database this shop comprises the version number of lowest version database to be upgraded and the highest version database that will be upgraded to; The highest version database creation unit is used for the lowest version database is renamed, and creates the highest version database; The transition rule reading unit is used at the highest version database, creates rule function and the storing process information that will use in the edition upgrading that defines in the version transition storehouse, reads in the transition rule table all transition rules between two versions; And the upgrading unit, be used for each table is upgraded, after the data of all tables of import, return the upgrade status information of all tables.
Comprise according to upgrading of the present invention unit: the data importing chunk is used to import the required master data of execution upgrading; Data variation and upgrading chunk are used for the transition rule according to every table, call correlated expression formula, function or storing process information are carried out the data that import in the data importing unit special variation and upgrading; And the upgrade status record blocking, be used to write down the upgrade status information of every table.Wherein, upgrade status information comprise escalate into merit information and the upgrading failure information.
According to another aspect of the present invention, provide a kind of upgrading Proxy Method, it comprises: reading database version number, version database this shop comprise the version number of lowest version database to be upgraded and the highest version database that will be upgraded to; The lowest version database is renamed, create the highest version database; In the highest version database, create rule function and the storing process information that will use in the edition upgrading that defines in the version transition storehouse, read in the transition rule table all transition rules between two versions; And each table upgraded, after the data of all tables of import, return the upgrade status information of all tables.
May further comprise the steps in the above-mentioned process that every table is upgraded: import and carry out the required master data of upgrading; According to the transition rule of every table, call the differentiation file and carry out the variation and the upgrading of data; And the upgrade status information that writes down every table.Wherein, upgrade status information comprise escalate into merit information and the upgrading failure information.
In this upgrading Proxy Method, if return the upgrading successful information, then upgrading finishes.In addition, if return the upgrading failure information, then return to the preceding lowest version database of upgrading.
Another aspect of the present invention provides a kind of upgrading proxy module of versions of data, it comprises: version database this shop reading unit, be used for reading database version number, version database this shop comprises the version number of lowest version database to be upgraded and the highest version database that will be upgraded to; The highest version database creation unit is used for the lowest version database is renamed, and creates the highest version database; The transition rule reading unit is used at the highest version database, creates rule function and the storing process information that will use in the edition upgrading that defines in the version transition storehouse, reads in the transition rule table all transition rules between two versions; And the upgrading unit, be used for each table is upgraded, after the data of all tables of import, return the upgrade status information of all tables.
In the upgrading module, comprising: the data importing chunk is used to import the required master data of execution upgrading; Data variation and upgrading chunk are used for the transition rule according to every table, call correlated expression formula, function or storing process information are carried out the data that import in the data importing unit special variation and upgrading; And the upgrade status record blocking, be used to write down the upgrade status information of every table.Wherein, upgrade status information comprise escalate into merit information and the upgrading failure information.
Thereby, the present invention adopts data upgrading agency and version transition storehouse to carry out the upgrading of data system, the ROMPaq or the complicated SQL script file that do not need each all write specialized, the version transition storehouse that only need safeguard each software version correspondence gets final product, software product itself had versatility widely, simplified the development amount greatly, and the dirigibility of system, extendability, maintainable better.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 shows the process flow diagram according to the implementation method of data version upgrading of the present invention;
Fig. 2 is the system construction drawing of the implementation method of data version upgrading of the present invention;
Fig. 3 shows at the block diagram according to the pre-defined rule in the implementation method of data version upgrading of the present invention;
Fig. 4 shows the process flow diagram of the process that every table is upgraded;
Fig. 5 shows the detail flowchart according to the upgrading Proxy Method of the embodiment of the invention;
Fig. 6 is the block diagram according to the implement device of data version upgrading of the present invention;
Fig. 7 shows at the block diagram according to the upgrading proxy module in the implement device of data version upgrading of the present invention; And
Fig. 8 shows the block diagram of the upgrading unit in the upgrading proxy module.
Embodiment
Describe specific embodiments of the invention in detail below in conjunction with accompanying drawing.
Fig. 1 shows the block diagram according to the implementation method of data version upgrading of the present invention, and Fig. 2 is the system construction drawing of the implementation method of data version upgrading of the present invention.With reference to figure 1 and Fig. 2, the implementation method of upgrading comprises: S102 is written to software systems with lowest version database 202 and the version transition storehouse 204 from the lowest version to the highest version; And S104, according to pre-defined rule, with the lowest version data importing in the highest version database, thereby with this lowest version database upgrade to highest version database 208, wherein, in data upgrading Agent 206, realize the upgrade method of versions of data.Version transition storehouse 204 comprises the version upgrade file that exists with the tables of data form, comprising upgrading rule and the method between each version and the last version.
By Fig. 1 and Fig. 2 as can be seen, the core of the implementation method of data upgrading is the upgrading Proxy Method, and the basis of upgrade method is exactly definition and management to version transition storehouse.
Wherein, the Description of table definition descriptors such as current version database this shop, date issued, product type, transition rule refers to: the variation that the comparison of the data dictionary by height edition data storehouse can not show, such as the redefining etc. of the addition subtraction multiplication and division computing of the fractionation of field, field, field rule.Transition rule can be a simple calculations expression formula, also can utilize the technology of database itself to write complicated function or storing process information etc. flexibly and carry out operation of data and conversion, and each bar transition rule is all relatively independent, in the performance history of redaction, only need to increase a transition rule and get final product.
Version transition storehouse 204 comprises Description of table and transition rule table, below provides instantiation.
(1) definition of Description of table comprises following field:
VERSION: Production Version;
VERDATE: version date;
DBVER: version database this shop;
PRODTYPE: product category, regulation must just allow upgrading by the identical database of product category; And
PREDB: the lowest version database-name before the upgrading, this field is filled in after upgrading is finished, and initial value is empty.
(2) definition of transition rule table comprises following field:
CURVERSION: current version number;
PREVERSION: last version number;
TABLENAME: table name;
FIELDNAME: field name;
EXPRESSION: transition rule expression formula; And
PROCNAME: the storing process information name of calling.
Expression formula is the expression formula of carrying out computing by the field in the table, this expression formula is write according to the demand of reality, will guarantee that when writing expression formula must be correct, the data-switching that can use various operational symbols and database functions and User-Defined Functions to wait in expression formula to realize the complexity relevant with field concerns.
For system can be upgraded flexibly, also increased the PROCNAME field, the table name of front, field name and expression formula field were all invalid when this field was effective, the database store process information name that need call especially when having described upgrading, relevant storing process information is one section sql like language program, can finish the upgrading of some special circumstances that general regular expression can't finish.
The example of expression formula below will be described, wherein, suppose in version 1.01, the numeric field AA in the TEST table in the version 1.0 to be split as AA and AA1, the Value Data of AA1 source is that the AA field of the table TEST in 1.0 is from 0 to 4 value, in addition, the minimum value of field BB in 1.0 versions is 0, and the minimum value in 1.01 versions is 100, in version transition storehouse following record should be arranged so:
V01.01,V01.00,TEST,AA1,F_SPLIT_BIT(AA,0,4),NULL
V01.01,V01.00,TEST,BB,BB+100,NULL
Suppose when version 1.0 is upgraded to version 1.01, to also have some special data upgradings to define, then can be write as the sql procedure information of relative complex and finish, be described below with transition rule with expression formula:
V01.01,V01.00,NULL,NULL,NULL,PROC_UPDATE_TO_VER0101
If the user need show upgrading, as long as transition rule of definition is written in the transition rule table, like this, when releasing, redaction, just can guarantee the smooth upgrade of data so as long as guarantee the complete of transition rule table.
With reference to figure 3, show at block diagram according to the pre-defined rule in the implementation method of data version upgrading of the present invention.Carry out the step of Fig. 3: S302 in the data version upgrading process of step S104 in Fig. 1, reading database version number, version database this shop comprise the version number of lowest version database to be upgraded 202 and the highest version database 208 that will be upgraded to; S304 renames the lowest version database, creates highest version database 208; S306 in the highest version database, creates rule function and the storing process information that will use in the edition upgrading that defines in the version transition storehouse, reads in the transition rule table all transition rules between two versions; And S308, each table is upgraded, after the data of all tables of import, return the upgrade status information of all tables.
Fig. 4 shows the process flow diagram of the process of among the step S308 in Fig. 3 every table being upgraded.In process to every table upgrading, carry out following steps: S402, import and carry out the required master data of upgrading; S404 according to the transition rule of every table, calls the differentiation file and carries out the variation and the upgrading of data; And S406, write down the upgrade status information of every table.Wherein, upgrade status information comprise escalate into merit information and the upgrading failure information.
In step S308, if return the upgrading successful information, then upgrading finishes.In addition, if return the upgrading failure information, then return to the preceding lowest version database of upgrading according to step S304.
Fig. 5 shows the detailed upgrade method according to the versions of data of the embodiment of the invention.Describe the process flow diagram of Fig. 5 in detail below with reference to Fig. 3 and Fig. 4.
S302 in Fig. 3: reading database version number, version database this shop comprise the version number of lowest version database to be upgraded and the highest version database that will be upgraded to, and corresponding diagram 5 step S501 receive the edition upgrading order, read current database version number.
Next, execution in step S304: the lowest version database is renamed, create the highest version database.Corresponding diagram 5 steps are:
S502 renames the database of lowest version; And
S503 sets up the highest version database.
Then, execution in step S306: in the highest version database, create rule function and the storing process information that to use in the edition upgrading that defines in the version transition storehouse, read in the transition rule table all transition rules between two versions, the following steps in the corresponding diagram 5.
S504 creates rule function and the storing process information of using in the edition upgrading in the database of highest version, read the transition rule table; And
S505 imports needs and the table name of upgrading is put into temporary table.
Next execution in step S506; Check whether the table that does not import is arranged.
In S506, inspection is when the table that does not import is arranged, then to enter the step S308 among Fig. 3: each table is upgraded, after the data of all tables of import, return the upgrade status information of all tables.Below, will step in the corresponding diagram 5 be described with reference to figure 4, wherein:
S507 takes out a table name and carries out the importing of this table master data from the lowest version storehouse to the highest version storehouse from temporary table; (corresponding S402)
S508 checks the transition rule that whether has defined this literary name section in version transition storehouse, if any then forwarding 509 to, forwards 510 to as not defining;
S509 finishes the special variation upgrading (the corresponding S404 of above-mentioned two steps) of data according to transition rule; And
S510 is changed to 1 with the sign of importing of temporary table, writes down the upgrading success/failure flags (corresponding S406) of this table.
S511; Check whether all show all to have upgraded to finish, and as then not forwarding the upgrading of 506 other tables of continuation to, all tables then forward 512 to as having upgraded; And
At last, carry out S512; Return data is upgraded successfully/failure information, and edition upgrading finishes.
Above-mentioned upgrading Proxy Method is embedded in the installation procedure of software systems, just can be used as a upgrading proxy module, be used for realizing when system installs the smooth upgrade of data.
Fig. 6 is the block diagram according to the implement device of data version upgrading of the present invention.As shown in Figure 6, the implement device 600 of data version upgrading comprises: version writing module 602 is used to write lowest version database and the version transition storehouse from the lowest version to the highest version to software systems; And upgrading proxy module 604, be used for the lowest version data importing being upgraded to the highest version database to the highest version database.
In above-mentioned version writing module 602, version transition storehouse comprises the version upgrade file that exists with the tables of data form, comprising upgrading rule and the method between each version and the last version.The version upgrade file comprises version information table, transition rule table and the function and the storing process information that realize transition rule.The transition rule table is kept at the data transition rule in the data version upgrading process, and the data transition rule is relatively independent.
Fig. 7 shows at the block diagram according to the upgrading proxy module 604 in the implement device 600 of data version upgrading of the present invention.Upgrading proxy module 604 comprises: version database this shop reading unit 702, be used for reading database version number, and version database this shop comprises the version number of lowest version database to be upgraded and the highest version database that will be upgraded to; Highest version database creation unit 704 is used for the lowest version database is renamed, and creates the highest version database; Transition rule reading unit 706 is used at the highest version database, creates rule function and the storing process information that will use in the edition upgrading that defines in the version transition storehouse, reads in the transition rule table all transition rules between two versions; And upgrading unit 708, be used for each table is upgraded, after the data of all tables of import, return the upgrade status information of all tables.
Wherein, upgrade status information comprise escalate into merit information and the upgrading failure information.If return the upgrading successful information, then upgrading finishes.In addition, if return the upgrading failure information, then return to the preceding lowest version database of upgrading according to the highest version database creation unit.
In upgrading unit 708, carry out upgrading to every table, comprise chunk as shown in Figure 8.Fig. 8 shows the block diagram of the upgrading unit in the upgrading proxy module.
As shown in Figure 8, upgrading unit 708 comprises: data importing chunk 802 is used to import the required master data of execution upgrading; Data variation and upgrading chunk 804 are used for the transition rule according to every table, call correlated expression formula, function or storing process information are carried out the data that import in the data importing unit special variation and upgrading; And upgrade status record blocking 806, be used to write down the upgrade status information of every table.
Can see that according to top realization of the present invention the present invention has realized the smooth upgrade of software system data by the maintenance of writing unified upgrading Proxy Method and version transition storehouse, and system architecture is clear, realizes simple relatively.
Be the preferred embodiments of the present invention only below, be not limited to the present invention, for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.

Claims (10)

1. a device that is used for data version upgrading is characterized in that, comprising:
The version writing module is used for lowest version database and the version transition storehouse from the lowest version to the highest version are written to software systems; And
The upgrading proxy module is used for the lowest version data importing being upgraded to the highest version database to the highest version database.
2. the device that is used for data version upgrading according to claim 1, it is characterized in that, in described version writing module, described version transition storehouse comprises the version upgrade file that exists with the tables of data form, comprising upgrading rule and the method between each version and the last version.
3. the device that is used for data version upgrading according to claim 2 is characterized in that, define described version upgrade file comprise following one of at least: version information table, transition rule table and the function and the storing process information that realize transition rule.
4. the device that is used for data version upgrading according to claim 3 is characterized in that, described transition rule table is kept at the data transition rule in the described data version upgrading process, and described data transition rule is relatively independent.
5. the device that is used for data version upgrading according to claim 1 is characterized in that, described upgrading proxy module comprises:
Version database this shop reading unit, the version number that is used to read lowest version database to be upgraded and the highest version database that will be upgraded to;
The highest version database creation unit is used for the lowest version database is renamed, and creates the highest version database;
The transition rule reading unit is used at described highest version database, creates the rule function that will use in edition upgrading and the storing process that define in the described version transition storehouse, reads in the described transition rule table all transition rules between two versions; And
The upgrading unit is used for each table is upgraded, and after the data of all tables of import, returns the upgrade status information of all tables.
6. the device that is used for data version upgrading according to claim 5 is characterized in that, described upgrading unit comprises:
The data importing chunk is used to import the required master data of execution upgrading;
Data variation and upgrading chunk are used for the transition rule according to described every table, call correlated expression formula, function or storing process carry out the described data that import in described data importing unit special variation and upgrading; And
The upgrade status record blocking is used to write down the upgrade status information of described every table.
7. the device that is used for data version upgrading according to claim 6 is characterized in that, described upgrade status information comprise escalate into merit information and the upgrading failure information.
8. the upgrading proxy module of a versions of data is characterized in that, comprising:
Version database this shop reading unit is used for reading database version number, and described version database this shop comprises lowest version database to be upgraded and the version number of the highest version database that will be upgraded to;
The highest version database creation unit is used for the lowest version database is renamed, and creates the highest version database;
The transition rule reading unit is used at described highest version database, creates rule function and the storing process that will use in the edition upgrading that defines in the version transition storehouse, reads in the transition rule table all transition rules between two versions; And
The upgrading unit is used for each table is upgraded, and after the data of all tables of import, returns the upgrade status information of all tables.
9. the upgrading proxy module of versions of data according to claim 8 is characterized in that, described upgrading module comprises:
The data importing chunk is used to import the required master data of execution upgrading;
Data variation and upgrading chunk are used for the transition rule according to described every table, call correlated expression formula, function or storing process carry out the described data that import in described data importing unit special variation and upgrading; And
The upgrade status record blocking is used to write down the upgrade status information of described every table.
10. the upgrading proxy module of versions of data according to claim 9 is characterized in that, described upgrade status information comprise escalate into merit information and the upgrading failure information.
CNA2006101504523A 2006-10-31 2006-10-31 Device for upgrading data version Withdrawn CN101174204A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNA2006101504523A CN101174204A (en) 2006-10-31 2006-10-31 Device for upgrading data version

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNA2006101504523A CN101174204A (en) 2006-10-31 2006-10-31 Device for upgrading data version

Publications (1)

Publication Number Publication Date
CN101174204A true CN101174204A (en) 2008-05-07

Family

ID=39422738

Family Applications (1)

Application Number Title Priority Date Filing Date
CNA2006101504523A Withdrawn CN101174204A (en) 2006-10-31 2006-10-31 Device for upgrading data version

Country Status (1)

Country Link
CN (1) CN101174204A (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012083613A1 (en) * 2010-12-20 2012-06-28 中兴通讯股份有限公司 Multiversion upgrade method and apparatus for user self-defined performance indicator
CN105335436A (en) * 2014-08-11 2016-02-17 方正国际软件(北京)有限公司 Method and equipment for upgrading database structure
CN106462639A (en) * 2014-06-24 2017-02-22 谷歌公司 Processing mutations for remote database
CN107758461A (en) * 2017-10-28 2018-03-06 林光琴 A kind of control software field debugging system
CN109241672A (en) * 2018-10-15 2019-01-18 中冶赛迪技术研究中心有限公司 A kind of the model version upgrade-system and method of Logistics Simulation Software
CN109445812A (en) * 2018-09-10 2019-03-08 山东中磁视讯股份有限公司 A kind of software psychology test scale dissemination method and system

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012083613A1 (en) * 2010-12-20 2012-06-28 中兴通讯股份有限公司 Multiversion upgrade method and apparatus for user self-defined performance indicator
CN106462639A (en) * 2014-06-24 2017-02-22 谷歌公司 Processing mutations for remote database
US10521417B2 (en) 2014-06-24 2019-12-31 Google Llc Processing mutations for a remote database
US10545948B2 (en) 2014-06-24 2020-01-28 Google Llc Processing mutations for a remote database
CN106462639B (en) * 2014-06-24 2020-04-24 谷歌有限责任公司 Handling changes to a remote database
US11455291B2 (en) 2014-06-24 2022-09-27 Google Llc Processing mutations for a remote database
CN105335436A (en) * 2014-08-11 2016-02-17 方正国际软件(北京)有限公司 Method and equipment for upgrading database structure
CN107758461A (en) * 2017-10-28 2018-03-06 林光琴 A kind of control software field debugging system
CN109019217A (en) * 2017-10-28 2018-12-18 林光琴 A kind of lift control software field debugging system
CN109019217B (en) * 2017-10-28 2020-09-18 吉安品位环保科技有限公司 Elevator control software field debugging system
CN109445812A (en) * 2018-09-10 2019-03-08 山东中磁视讯股份有限公司 A kind of software psychology test scale dissemination method and system
CN109241672A (en) * 2018-10-15 2019-01-18 中冶赛迪技术研究中心有限公司 A kind of the model version upgrade-system and method of Logistics Simulation Software

Similar Documents

Publication Publication Date Title
CN100517229C (en) Data version upgrading method
CN101499069B (en) Internal memory database file updating method and apparatus
CN101046821B (en) Generic database manipulator
US8566808B2 (en) Object storage and synchronization hooks for occasionally-connected devices
CN101582079B (en) Object query method and device
CN103136231B (en) Method of data synchronization between a kind of heterogeneous database and system
CN101661509B (en) Method for generating major key field of database table and device thereof
CN102567399B (en) Method and device for accessing database
CN101174204A (en) Device for upgrading data version
CN111324610A (en) Data synchronization method and device
CN102103567A (en) Passing data from a cpu to a graphics processor by writing multiple versions of the data in a shared memory
CN103049251B (en) A kind of data base persistence layer device and database operation method
CN104517181B (en) Enterprise content management system and method for nuclear power station
CN104794147A (en) Heterogeneous database access method
CN101673287A (en) SQL sentence generation method and system
CN103020268A (en) Serial number applying method and system of relational database
EP1217547A2 (en) Object integrated management system
CN105808653A (en) User label system-based data processing method and device
CN103946794A (en) Cross-reference and priority claim to related applications
CN102541923B (en) Database read-write separating method and device
CN105787058A (en) User label system and data pushing system based on same
CN105224527A (en) Be applicable to the general ETL method of multiple object table update mode
CN103345501A (en) Method and device for updating database
CN106557307A (en) The processing method and processing system of business datum
CN104636260A (en) Data management method and system for charging services

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C04 Withdrawal of patent application after publication (patent law 2001)
WW01 Invention patent application withdrawn after publication