CN106599167B - System and method for supporting increment updating of database - Google Patents
System and method for supporting increment updating of database Download PDFInfo
- Publication number
- CN106599167B CN106599167B CN201611129545.8A CN201611129545A CN106599167B CN 106599167 B CN106599167 B CN 106599167B CN 201611129545 A CN201611129545 A CN 201611129545A CN 106599167 B CN106599167 B CN 106599167B
- Authority
- CN
- China
- Prior art keywords
- sql
- executed
- file
- database
- sql file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 238000012216 screening Methods 0.000 claims abstract description 40
- 238000004458 analytical method Methods 0.000 claims description 12
- 238000007726 management method Methods 0.000 description 12
- 238000011161 development Methods 0.000 description 4
- 238000013500 data storage Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000000739 chaotic effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and a system for supporting increment upgrading of a database, wherein the method comprises the following steps: analyzing the version information of the executed SQL file in the database; analyzing the SQL files in the appointed folder to obtain the version information of all the SQL files in the appointed folder; screening out SQL files with version information different from that of the SQL files executed in the database from all the SQL files in the specified folder as pre-execution SQL files; and executing the pre-execution SQL file, and recording the SQL file execution information of the pre-execution SQL file. The version information of the SQL files executed in the database is compared before the newly added SQL file is executed, if the version information does not exist in the SQL files executed in the database, the SQL file is executed as the pre-executed SQL file, otherwise, the SQL file is not executed, reasonable and effective management of the version information of the database is achieved, the SQL files executed in increments and the SQL file execution results are recorded, and the files specifically executed by each module can be obtained according to the recorded information.
Description
Technical Field
The invention relates to the technical field of database management, in particular to a system and a method for supporting incremental upgrading of a database.
Background
With the continuous progress and development of computer technology, hardware and software are rapidly developed in respective fields, support each other and promote each other, and since the update and upgrade of the hardware and the software are asynchronous in many times. For example, hardware of a computer is determined when the computer is used, and with the continuous development of computer software, in order to optimize the performance of the computer, bring the performance of the hardware into full play and improve the utilization efficiency of equipment, a new algorithm is generally used for system upgrade to improve the operation efficiency of the equipment.
In the process of software product development and upgrading, the version control of the database is always in a relatively chaotic management state, for example, in the process of upgrading the database at a certain time, a certain part of the database is upgraded, and in the process of upgrading other databases, other parts of the database are upgraded, so that the database version information before and after upgrading of all versions exists in the whole database in the process of upgrading at one time, the management of the database is very inconvenient, and if the subsequent database needs to be upgraded, the upgrading of so many database version information in the database is very inconvenient.
Disclosure of Invention
The invention aims to provide a system and a method for supporting increment upgrading of a database, which can clearly manage database version information in the development and upgrading processes and improve the database management development efficiency.
In order to solve the above technical problem, an embodiment of the present invention provides a method for supporting incremental upgrade of a database, including:
analyzing the version information of the executed SQL file in the database;
analyzing the SQL file in the appointed folder, and obtaining the version information of the SQL file in the appointed folder;
screening out SQL files in the designated folder, wherein the version information of the SQL files is different from that of the SQL files executed in the database, and using the SQL files as pre-execution SQL files;
and executing the pre-executed SQL file and recording the SQL file execution information of the pre-executed SQL file.
The version information comprises a system version number, a module name and a module SQL version number.
The SQL file execution information comprises a system version number, a module SQL version number, a module name, an SQL file name, execution time and execution user information.
The name format of the SQL file is system version number _ module name.
The screening out the SQL files in the designated folder, of which the version information is different from that of the SQL files executed in the database, as the pre-execution SQL files comprises the following steps:
and screening out SQL files with different system version numbers, different module SQL version numbers or different module names from the SQL files executed in the database in the SQL files in the designated folder as pre-execution SQL files.
Wherein the executing the pre-execution SQL file comprises:
and executing the pre-execution SQL file from small to large according to the version number of the pre-execution SQL file.
In addition, an embodiment of the present invention further provides a system for supporting incremental upgrading of a database, including:
analyzing means for analyzing version information of the executed SQL file in the database;
the analysis device is used for analyzing the SQL file in the specified folder to obtain the version information of the SQL file in the specified folder;
the screening device is connected with the analysis device and is used for screening out the SQL files in the designated folder, which are different from the version information of the executed SQL files in the database, as the pre-executed SQL files;
and the execution recording device is connected with the screening device and is used for executing the pre-executed SQL file and recording the SQL file execution information of the pre-executed SQL file.
The version information comprises a system version number, a module name and a module SQL version number.
The SQL file execution information comprises a system version number, a module SQL version number, a module name, an SQL file name, execution time and execution user information.
The name format of the SQL file is system version number _ module name.
Compared with the prior art, the system and the method for supporting the incremental upgrading of the database provided by the embodiment of the invention have the following advantages:
the method for supporting the incremental upgrading of the database provided by the embodiment of the invention comprises the following steps:
analyzing the version information of the executed SQL file in the database;
analyzing the SQL file in the appointed folder, and obtaining the version information of the SQL file in the appointed folder;
screening out SQL files in the designated folder, wherein the version information of the SQL files is different from that of the SQL files executed in the database, and using the SQL files as pre-execution SQL files;
and executing the pre-executed SQL file and recording the SQL file execution information of the pre-executed SQL file.
The system supporting the incremental upgrading of the database provided by the embodiment of the invention comprises the following steps:
analyzing means for analyzing version information of the executed SQL file in the database;
the analysis device is used for analyzing the SQL file in the specified folder to obtain the version information of the SQL file in the specified folder;
the screening device is connected with the analysis device and is used for screening out the SQL files in the designated folder, which are different from the version information of the executed SQL files in the database, as the pre-executed SQL files;
and the execution recording device is connected with the screening device and is used for executing the pre-executed SQL file and recording the SQL file execution information of the pre-executed SQL file.
The system and the method for supporting the incremental upgrading of the database compare the version information of the SQL files executed in the database before the newly added SQL file is executed, if the version information does not exist in the SQL file executed in the database, the SQL file is executed as the pre-executed SQL file, otherwise, the SQL file is not executed, so that the reasonable and effective management of the version information of the database is realized, the incrementally executed SQL file and the execution result of the SQL file are recorded, and the files specifically executed by each module can be obtained according to the recorded information.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic flowchart illustrating steps of a specific implementation of a method for supporting incremental upgrade of a database according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a specific implementation of the system for supporting incremental upgrade of a database according to the embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1-2, fig. 1 is a schematic flowchart illustrating steps of a method for supporting incremental upgrade of a database according to an embodiment of the present invention; fig. 2 is a schematic structural diagram of a specific implementation of the system for supporting incremental upgrade of a database according to the embodiment of the present invention.
In a specific embodiment, the method for supporting incremental upgrade of a database, as shown in fig. 1, includes:
step 1, analyzing version information of an executed SQL file in a database;
step 2, analyzing the SQL file in the appointed folder, and obtaining the version information of the SQL file in the appointed folder;
step 3, screening out SQL files in the specified folder, wherein the version information of the SQL files is different from that of the SQL files executed in the database, and using the SQL files as pre-execution SQL files;
and 4, executing the pre-executed SQL file and recording the SQL file execution information of the pre-executed SQL file.
It should be noted that, in the present invention, the process of analyzing the version information of the SQL file executed in the database and the process of analyzing the SQL file in the designated folder and obtaining the version information of the SQL file in the designated folder are parallel and do not affect each other, so the problem of front and back order is not considered during execution.
In step 2 of the present invention, analyzing the SQL file in the designated folder and obtaining the version information of the SQL file in the designated folder means analyzing all the SQL files in the designated folder, so that the executed SQL file in the database is not repeatedly executed, and only the newly added SQL file is executed.
The SQL Language is an abbreviation of Structured Query Language (Structured Query Language). The SQL language is a database query and programming language for accessing data and querying, updating, and managing relational database systems; and is also an extension of the database script file.
The SQL language is a high-level, non-procedural programming language that allows users to work on high-level data structures. The method does not require a user to specify a data storage method and does not require the user to know a specific data storage mode, so that different database systems with completely different underlying structures can use the same structured query language as an interface for data input and management. SQL language statements can be nested, which gives him great flexibility and powerful functionality.
In the invention, the database is upgraded by using the file edited by SQL language.
It should be noted that in the present invention, the added SQL file is placed in the designated folder before being executed.
The added SQL file is analyzed before the added SQL file is executed, the version information of the added SQL file is obtained, in order to enable only the added SQL file to be executed, the added SQL file in the appointed file is screened, and the added SQL file different from the SQL file executed in the database is screened out. Comparing the version information of the analyzed SQL file in the specified folder with the version information of the SQL file in the executed database, if the version information does not exist in the executed SQL file in the database, executing the SQL file as a pre-executed SQL file, otherwise, not executing the SQL file. Therefore, only the newly added SQL file is executed in the added SQL file, and the reasonable and effective management of the database version information is realized. Meanwhile, because the SQL files executed in increments are recorded in the execution process, the SQL file execution result can obtain which files are specifically executed by each module according to the recorded information.
In the invention, the version information of the SQL file generally comprises a system version number, a module name and a module SQL version number.
In a specific embodiment, the SQL file execution information includes a system version number, a module SQL version number, a module name, an SQL file name, an execution time, and execution user information.
The SQL file execution information is used for recording the execution condition of the newly added SQL file and also can be used as the SQL file executed in the database, so that the SQL file execution information is used as a part of the database in the next added SQL file screening and comparing process, and the upgrading management of the whole database is more perfect.
It should be noted that, the system version number, the module name, and the module SQL version number in the version information may be generally used, and other information in the version information may also be used, which is not specifically limited in the present invention, but only because the system version number and the module SQL version number have corresponding numbers, for example, in the process of upgrading from a 1.0 system to a 1.1 system, the system version number changes, which reduces the difficulty and process of screening, and improves the upgrading speed and the upgrading efficiency of the database, and meanwhile, in the upgrading process, besides the upgrading of the system, some modules may be upgraded, for example, the upgrading of an authentication module therein, and the like.
In a specific embodiment, the name format of the SQL file is system version number _ module name. The system version number and the module version number in the name format of the SQL file are placed in front, and the comparison speed and the screening speed can be increased due to the fact that the version number is a number.
It should be noted that the name format of the SQL file in the present invention may also be in other forms, such as module version number _ system version number _ module name. SQL, or module name _ module version number _ system version number. SQL, or may also be in a name format with other version information added, which is not limited in this invention.
For screening out newly added SQL files from the added SQL files, in a specific embodiment, the screening out SQL files in the designated folder that have different version information from the SQL files executed in the database as pre-execution SQL files includes:
and screening out SQL files with different system version numbers, different module SQL version numbers or different module names from the SQL files executed in the database in the SQL files in the designated folder as pre-execution SQL files.
In the actual process of comparing and screening the newly added SQL file, the system version number and the module SQL version number may be compared separately or may be put together, that is, the system version number and the module SQL version number are combined into a version number for processing. Because the module is generally used as the unit for upgrading, the version numbers can be directly compared, and the processing efficiency is high because the version numbers are all digital.
Of course, in the present invention, the added SQL file may be classified first, that is, the added SQL file is classified into SQL files corresponding to different modules, so that only the comparison of the version number is needed, and the comparison of the module type is not needed to be added each time, which can improve the screening efficiency.
Because there are many SQL files in each upgrade process, and the upgraded SQL files may not be completely the same in the upgrade process, for example, the system version number of the original module a is 1.0, the module SQL version number is 1.0, the newly added SQL file has 1.1_1.0_ module a.sql, also has 1.0_1.1_ module a.sql, and also has 1.1_1.1_ module a.sql, if there is no certain execution sequence, it may cause that this place is upgraded first and then another place is upgraded, so that the upgrade speed is slow, even the situation that the upgrade cannot be performed normally is caused. Thus, in one embodiment, the executing the pre-executed SQL file comprises:
and executing the pre-execution SQL file from small to large according to the version number of the pre-execution SQL file.
The version number here refers to a module version number and a system version number, and may be a version number formed by combining a module version number and a system version number, or a version number formed by combining a system version number and a module version number, or a version number in other forms, which is not specifically limited in the present invention.
For example, the system version number is 1.1, the module version number is 1.2, and the combined version number may be 1.1_1.2 or 1.2_ 1.1. If there are other version numbers of the SQL file, the SQL file can be executed from small to large according to the mode of firstly judging the system version number and then judging the module version number, or the SQL file can be executed from small to large according to the mode of firstly judging the module version number and then judging the system version number.
In addition, an embodiment of the present invention further provides a system for supporting incremental upgrade of a database, as shown in fig. 2, including:
an analysis device 10, said analysis device 10 is used for analyzing the version information of the executed SQL file in the database;
the analysis device 20 is used for analyzing the SQL file in the designated folder to obtain the version information of the SQL file in the designated folder;
a screening device 30, wherein the screening device 30 is connected to the analysis device 10 and the analysis device 20, and is configured to screen out, as a pre-execution SQL file, an SQL file in the designated folder that is different from version information of an executed SQL file in the database;
and the execution recording device 40 is connected with the screening device 30, and is used for executing the pre-executed SQL file and recording the SQL file execution information of the pre-executed SQL file.
In the present invention, the version information of the executed SQL file in the database includes both the version information of the executed SQL file (version information of the SQL file of the initial system) pre-stored in the system, and the SQL file execution information of the pre-executed SQL file after each database upgrade recorded in the execution recording device 40.
The added SQL file in the designated folder is analyzed to obtain version information of the SQL file in the designated folder, and then the added SQL file is compared with the version information of the executed SQL file in the database analyzed by the analysis device 10, and the SQL file in the designated folder, which is completely different from the version information of the executed SQL file in the database, is found, and is the newly added SQL file of the database upgrade of this time, and then is used as a pre-execution SQL file, and is executed in the process of the database upgrade of this time, and the execution process is recorded by the execution recording device 40, so that the pre-execution SQL file of this time is used as the executed SQL file in the database of the next time. The method and the system realize reasonable and effective management of the database version information, record the SQL files executed by the increment and the SQL file execution results, and can obtain which files are specifically executed by each module according to the recorded information.
In the present invention, the version information generally includes a system version number, a module name, and a module SQL version number.
In order to ensure the normal upgrade of the database at the next time and realize the effective management of the incremental SQL file, the execution recording device 40 executes the newly added SQL file as a pre-execution file, records the whole execution process and result, and provides reference for the next upgrade of the database, where the execution information of the SQL file includes the system version number, the module SQL version number, the module name, the SQL file name, the execution time, and the execution user information.
It should be noted that, in the present invention, the version information and the SQL file execution information include, but are not limited to, the above-mentioned contents, for example, when a small unit in a certain module is subjected to database upgrade, the name or code number of the small unit may be added to the version information, and for the naming of the version number, except for the customization, for example, the previous upgrade is from the 1.0 version to the 1.1 version, and the current upgrade is from the 1.1 version to the 1.2 version. The version information in the upgrading process can be controlled by the user, the version number is named by using other version names, or even the system self-defines the version information according to time, for example, if the time after the last upgrading is 2011, month 11, the version information after the upgrading is 2011.11, and if the time after the upgrading is 2013, month 2, the version information after the upgrading is 2013.02.
Therefore, the naming modes of the system version number and the module version number are not specifically limited, and the naming modes of the system version number and the module version number can be the same or different.
In the process of upgrading the database, besides comparing the added SQL files with the SQL files executed in the database one by one, other comparison and screening methods can be used, for example, to reduce the screening time and improve the screening efficiency, the latest version information of the SQL files in the database is analyzed, and then the lowest version information of the SQL files in the added SQL files is compared with the latest version information, so that invalid comparison and screening are avoided, and the screening efficiency is improved.
Even a latest SQL file version information recording module can be added in the system, and after the database is upgraded every time, the version information of the executed pre-executed SQL file is recorded and replaces the latest SQL file version information in the database last time, so that the added SQL file can be quickly screened out only by comparing with the latest SQL file version information recording module, and the screening efficiency can be improved.
The screening method of the screening apparatus 30 according to the present invention is not particularly limited, and a method capable of improving the screening efficiency is generally selected.
In a specific embodiment, the name format of the SQL file is system version number _ module name. The name format of the SQL file is fixed and unified, so that the management of the SQL file is convenient, and the version information of the executed SQL file in the database can be automatically placed at the initial position by using an automatic sequencing mode, such as a large-to-small version information arrangement mode.
Furthermore, the latest version of the SQL file is listed according to each item in the version information, so that the comparison and screening only need to be performed with the very limited version information of the SQL file (at most, with each item in the version information), and the screening efficiency is improved.
In the present invention, the name format of the SQL file may be other naming manners besides the above manner, or other version information items may be added, which is not specifically limited in the present invention.
In summary, the system and method for supporting incremental upgrading of a database provided in the embodiments of the present invention compare version information of an executed SQL file in the database before executing a newly added SQL file, if the version information does not exist in the executed SQL file in the database, the SQL file is executed as a pre-executed SQL file, otherwise, the version information is not executed, thereby implementing reasonable and effective management of the version information of the database, recording the incrementally executed SQL file, the execution result of the SQL file, and obtaining which files are specifically executed by each module according to the recorded information.
The system and method for supporting incremental upgrading of a database provided by the invention are described in detail above. The principles and embodiments of the present invention are explained herein using specific examples, which are presented only to assist in understanding the method and its core concepts. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
Claims (10)
1. A method for supporting incremental upgrades of a database, comprising:
analyzing the version information of the executed SQL file in the database;
analyzing the SQL file in the appointed folder, and obtaining the version information of the SQL file in the appointed folder;
screening out SQL files in the designated folder, wherein the version information of the SQL files is different from that of the SQL files executed in the database, and using the SQL files as pre-execution SQL files;
and executing the pre-executed SQL file and recording the SQL file execution information of the pre-executed SQL file.
2. The method of supporting incremental upgrades of databases of claim 1, in which the version information comprises a system version number, a module name, and a module SQL version number.
3. The method of supporting incremental upgrades of databases of claim 1, in which the SQL file execution information comprises a system version number, a module SQL version number, a module name, an SQL file name, execution time, and execution user information.
4. The method for supporting incremental upgrade of a database according to any one of claims 1 to 3, wherein the name format of the SQL file is system version number _ module name.
5. The method for supporting incremental upgrading of a database according to claim 4, wherein the screening out, as the pre-execution SQL file, the SQL file in the designated folder whose version information is different from the version information of the SQL file executed in the database comprises:
and screening out SQL files with different system version numbers, different module SQL version numbers or different module names from the SQL files executed in the database in the SQL files in the designated folder as pre-execution SQL files.
6. The method for supporting incremental upgrading of a database according to claim 5, wherein the executing the pre-executed SQL file comprises:
and executing the pre-execution SQL file from small to large according to the version number of the pre-execution SQL file.
7. A system for supporting incremental updating of a database, comprising:
analyzing means for analyzing version information of the executed SQL file in the database;
the analysis device is used for analyzing the SQL file in the specified folder to obtain the version information of the SQL file in the specified folder;
the screening device is connected with the analysis device and is used for screening out the SQL files in the designated folder, which are different from the version information of the executed SQL files in the database, as the pre-executed SQL files;
and the execution recording device is connected with the screening device and is used for executing the pre-executed SQL file and recording the SQL file execution information of the pre-executed SQL file.
8. The system for supporting incremental upgrade of a database according to claim 7, wherein said version information includes a system version number, a module name, and a module SQL version number.
9. The system for supporting incremental upgrading of a database according to claim 7, wherein the SQL file execution information includes a system version number, a module SQL version number, a module name, an SQL file name, an execution time, and execution user information.
10. The system for supporting incremental upgrade of a database according to claim 9, wherein the name format of the SQL file is system version number module name SQL.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611129545.8A CN106599167B (en) | 2016-12-09 | 2016-12-09 | System and method for supporting increment updating of database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611129545.8A CN106599167B (en) | 2016-12-09 | 2016-12-09 | System and method for supporting increment updating of database |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106599167A CN106599167A (en) | 2017-04-26 |
| CN106599167B true CN106599167B (en) | 2020-11-20 |
Family
ID=58598218
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611129545.8A Active CN106599167B (en) | 2016-12-09 | 2016-12-09 | System and method for supporting increment updating of database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106599167B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107357907A (en) * | 2017-07-17 | 2017-11-17 | 郑州云海信息技术有限公司 | A kind of database upgrade method and device for supporting cross-version |
| CN110865828A (en) * | 2018-08-28 | 2020-03-06 | 成都鼎桥通信技术有限公司 | Data upgrading method, device, equipment and computer readable storage medium |
| CN109947457A (en) * | 2018-12-29 | 2019-06-28 | 上海寰创通信科技股份有限公司 | A kind of database upgrade method |
| CN111459887B (en) * | 2020-03-30 | 2023-08-11 | 北京百度网讯科技有限公司 | Resource screening method and device, electronic equipment and storage medium |
| CN112486530A (en) * | 2020-11-20 | 2021-03-12 | 杭州电魂网络科技股份有限公司 | Game database storage table upgrading method and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014060230A1 (en) * | 2012-10-15 | 2014-04-24 | Here Global B.V. | Map update scripts with tree edit operations |
| CN104426924A (en) * | 2013-08-21 | 2015-03-18 | 腾讯科技（深圳）有限公司 | Method, apparatus, client, server and system for updating application software |
| CN104899066A (en) * | 2015-06-19 | 2015-09-09 | 青岛海信移动通信技术股份有限公司 | Method and device for continuous upgrading |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100426291C (en) * | 2005-11-26 | 2008-10-15 | 华为技术有限公司 | System and method to realize database upgrading in background management system |
| CN103294724B (en) * | 2012-03-05 | 2018-11-23 | 百度在线网络技术（北京）有限公司 | A kind of management method and system of database structure |
| CN105808284B (en) * | 2014-12-31 | 2019-10-22 | 广州市动景计算机科技有限公司 | A kind of method for updating increment and the server using it |
| CN105373631A (en) * | 2015-12-18 | 2016-03-02 | 河南思维自动化设备股份有限公司 | SQLSever-based automatic upgrading method for database structure |
| CN106201614A (en) * | 2016-07-11 | 2016-12-07 | 天津中兴智联科技有限公司 | A kind of universal method and system that multiple similar software can be carried out chain type upgrading |
-
2016
- 2016-12-09 CN CN201611129545.8A patent/CN106599167B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014060230A1 (en) * | 2012-10-15 | 2014-04-24 | Here Global B.V. | Map update scripts with tree edit operations |
| CN104426924A (en) * | 2013-08-21 | 2015-03-18 | 腾讯科技（深圳）有限公司 | Method, apparatus, client, server and system for updating application software |
| CN104899066A (en) * | 2015-06-19 | 2015-09-09 | 青岛海信移动通信技术股份有限公司 | Method and device for continuous upgrading |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106599167A (en) | 2017-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106599167B (en) | System and method for supporting increment updating of database | |
| US8010962B2 (en) | Infrastructure for the automation of the assembly of schema maintenance scripts | |
| US10324690B2 (en) | Automated enterprise software development | |
| US7774772B2 (en) | Method and apparatus to perform an application software migration | |
| US9465590B2 (en) | Code generation framework for application program interface for model | |
| US20240045850A1 (en) | Systems and methods for database orientation transformation | |
| EP2562641B1 (en) | Software application porting system | |
| US11651272B2 (en) | Machine-learning-facilitated conversion of database systems | |
| US20220179642A1 (en) | Software code change method and apparatus | |
| CN106991100B (en) | Data import method and device | |
| US8667010B2 (en) | Database table partitioning allowing overlaps used in full text query | |
| US10067750B2 (en) | Whole-program optimization using data from previous compilation runs | |
| CN113297320A (en) | Distributed database system and data processing method | |
| CN113204571A (en) | SQL execution method and device related to write-in operation and storage medium | |
| WO2002046909A1 (en) | Automatically deploy and upgrade an application based on markup language application definition | |
| US7797334B2 (en) | Automated downloading from mainframe to local area network | |
| CN116048609A (en) | Configuration file updating method, device, computer equipment and storage medium | |
| Marchioni | MongoDB for Java developers | |
| CN112817931A (en) | Method and device for generating incremental version file | |
| CN115756554A (en) | Version upgrading method and device | |
| CN115794312A (en) | Container automatic construction and deployment method based on attention point separation | |
| Troelsen et al. | Exploring Entity Framework Core | |
| CN117349258A (en) | Database version management method, device, computing equipment and storage medium | |
| US20210390085A1 (en) | Systems and methods of data migration in multi-layer model-driven applications | |
| CN114840489A (en) | Database version changing method and device, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201102 Address after: 215100 No. 1 Guanpu Road, Guoxiang Street, Wuzhong Economic Development Zone, Suzhou City, Jiangsu Province Applicant after: SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd. Address before: 450018 Henan province Zheng Dong New District of Zhengzhou City Xinyi Road No. 278 16 floor room 1601 Applicant before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |