CN109271199B - Method and system for database continuous integration and script file management - Google Patents
Method and system for database continuous integration and script file management Download PDFInfo
- Publication number
- CN109271199B CN109271199B CN201811056204.1A CN201811056204A CN109271199B CN 109271199 B CN109271199 B CN 109271199B CN 201811056204 A CN201811056204 A CN 201811056204A CN 109271199 B CN109271199 B CN 109271199B
- Authority
- CN
- China
- Prior art keywords
- script file
- script
- library
- database
- directory
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The invention discloses a method for database continuous integration and script file management, which comprises the following steps: submitting the script file to a script file collection directory of the current time period under the script file management directory, and executing the script file in a database integration environment; executing the script file and managing the script file summary directory through a script integration tool DBIT, wherein the steps comprise: creating sub-directories under the path of the script file summary directory of each time period; executing a script file in a verification library, judging whether the script file is abnormal or not, and importing the abnormal script file into the subdirectory under the script file summary directory of the current time period; executing the non-abnormal script file in a formal library, and adding the script file after successful execution to a version upgrading script file; and clearing the session control on the verification library, and rebuilding the verification library by using the formal library.
Description
Technical Field
The invention relates to the technical field of database integration, in particular to a method and a system for database continuous integration and script file management.
Background
In the software development process, along with the completion of the requirements, the repair of the Bug of the system and the improvement of the usability of the system are important links except for the addition and modification of codes, and the change of the database is also an important link. The change of software functions and the updating of programs are all premised on the change of a database. The upgrading of software, namely the process of updating from one version to another version, the updating of the database is a continuous process in the software development process, and a complete script management and integration process is required for frequent changes of the database structure and changes of preset data.
Among high-concurrency, high-data-volume transactional databases, the oracle database gives first place to. In the oracle integration process, a large number of scripts need to have the requirements of grammar correctness, various data constraints, the particularity of blob and clob fields and the characteristic of non-rollback property of ddl sentences, so that great difficulty is brought to continuous integration of oracle.
Therefore, a technique is needed to achieve database persistence integration and script file management.
Disclosure of Invention
The technical scheme of the invention provides a method and a system for database continuous integration and script file management, which aim to solve the problem of how to continuously integrate a database and manage a script file.
In order to solve the above problems, the present invention provides a method for database persistent integration and script file management, the method comprising:
submitting the script file to a script file collection directory of the current time period under the script file management directory, and executing the script file in a database integration environment;
executing the script file and managing the script file summary directory through a script integration tool DBIT, wherein the steps comprise:
creating subdirectories under the path of the script file summary directory of each time period;
executing a script file in a verification library, judging whether the script file is abnormal or not, and importing the abnormal script file into the subdirectory under the script file summary directory of the current time period;
executing the non-abnormal script file in a formal library, and adding the script file after successful execution to a version upgrading script file;
and clearing the session control on the verification library, and rebuilding the verification library by using the formal library.
Preferably, the method further comprises the following steps: creating a standard library and a verification library in a database environment, wherein the standard library is a formal library after continuous integration.
Preferably, the method further comprises the following steps:
defining a naming convention for the script file.
Preferably, the naming rule is:
date _ submitter name _ module name _ description txt.
Preferably, the script integration tool DBIT is developed by java language, and includes a preset timing task, and the timing task is executed by a task framework Quartz.
Preferably, the sub-directory further includes a text file, and the text file is used for recording the abnormal reason of the script file.
Preferably, the database integrated environment is an oracle database integrated environment.
Preferably, the database is continuously integrated by means of submitting a script file.
Preferably, the script file includes: script files for different dates, different submitters, and different modules.
Preferably, the submitting the script file to a script file collection directory of the current time period in the script file management directory includes:
the script file summary catalog of the current time period is automatically generated by a script integration tool DBIT according to the date, and the generation time is after the script of the previous day is executed.
According to another aspect of the present invention, there is provided a system for continuous integration of a database with script file management, the system comprising:
the submitting unit is used for submitting the script files to a script file collection directory of the current time period under the script file management directory and executing the script files in a database integration environment;
the integration unit is used for executing the script file and managing the script file under the summary directory through a script integration tool DBIT, and comprises the following steps:
creating sub-directories under the path of the script file summary directory of each time period;
executing a script file in a verification library, judging whether the script file is abnormal or not, and importing the abnormal script file into the subdirectory under the script file summary directory of the current time period;
executing the non-abnormal script file in a formal library, and adding the script file after successful execution to a version upgrading script file;
and clearing the session control on the verification library, and rebuilding the verification library by using the formal library.
Preferably, the system further comprises a building unit for creating a standard library and a verification library in the database environment, wherein the standard library is a formal library after continuous integration.
Preferably, the method further comprises the following steps:
and defining a naming rule of the script file.
Preferably, the naming rule is:
date _ submitter name _ module name _ description txt.
Preferably, the script integration tool DBIT is developed by java language, and includes a preset timing task, and the timing task is executed by a task framework Quartz.
Preferably, the sub-directory further includes a text file, and the text file is used for recording the abnormal reason of the script file.
Preferably, the database integrated environment is an oracle database integrated environment.
Preferably, the database is continuously integrated by submitting a script file.
Preferably, the script file includes: script files for different dates, different submitters, and different modules.
Preferably, the submitting the script file to a script file collection directory of the current time period under the script file management directory includes:
the script file summary catalog of the current time period is automatically generated by a script integration tool DBIT according to the date, and the generation time is after the script of the previous day is executed.
The technical scheme of the invention provides a method and a system for database continuous integration and script file management, wherein the method comprises the following steps: submitting the script file to a script file collection directory of the current time period under the script file management directory, and executing the script file in a database integration environment; the method comprises the following steps of executing a script file and managing a script file summary directory through a script integration tool DBIT, wherein the steps of: creating subdirectories under the path of the script file summary directory of each time period; executing the script file in the verification library, judging whether the script file is abnormal or not, and importing the abnormal script file into the subdirectory under the script file summary directory of the current time period; executing the non-abnormal script file in a formal library, and adding the script file after the execution is successful to the version upgrading script file; and clearing the session control on the verification library, and rebuilding the verification library by using the formal library. The technical scheme of the invention solves the problems of continuous integration of the oracle database and manufacture of the upgrade script file in the software development process, and provides a solution for managing the script file. In the prior art, complicated verification is performed on the script file according to the grammar, and the verification result is not good. The innovation of the invention is that: the script is directly executed, and then error correction is carried out in a mode that an exception is captured by a java program in the execution process. The technical scheme of the invention is converted from the prior judgment into the reverse derivation from the conclusion. No matter the path creation, the script verification, the script execution and the database automatic backup are automatically executed through a script integration tool DBIT without manual intervention. Therefore, in the software development process, the continuous integration of the database can be automated as much as possible, the workload is reduced to the maximum extent, and the stability and the correctness of the database in the integration are improved.
Drawings
Exemplary embodiments of the invention may be more completely understood in consideration of the following drawings:
FIG. 1 is a flowchart of a method for database persistence integration and script file management in accordance with a preferred embodiment of the present invention;
FIG. 2 is a flow diagram of a method for database persistent integration and script file management in accordance with a preferred embodiment of the present invention; and
fig. 3 is a system structural diagram for database persistent integration and script file management according to a preferred embodiment of the present invention.
Detailed Description
The exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, however, the present invention may be embodied in many different forms and is not limited to the embodiments described herein, which are provided for complete and complete disclosure of the present invention and to fully convey the scope of the present invention to those skilled in the art. The terminology used in the exemplary embodiments illustrated in the accompanying drawings is not intended to be limiting of the invention. In the drawings, the same unit/element is denoted by the same reference numeral.
Unless otherwise defined, terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Further, it will be understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense.
FIG. 1 is a flow chart of a method for database persistence integration and script file management in accordance with a preferred embodiment of the present invention. When software is developed, a database version needs to be established first. In the encoding process of actual software development, each designer and development engineer need to design the structure of a database table, database objects such as various constraints, indexes and views, and preset data in advance before encoding. Complex systems all require teams of multiple engineers to work together. For consistency, everyone will face the same database and modify the database every day. This process is submitted to the database for execution in the form of a script file. Therefore, the management of script files and database integration are very important tasks. As shown in fig. 1, a method for database persistent integration and script file management, the method comprising:
preferably, in step 101: and submitting the script file to a script file collection directory of the current time period under the script file management directory, and executing the script file in a database integration environment.
Preferably, at step 102: the method comprises the following steps of executing a script file and managing a script file summary directory through a script integration tool DBIT, wherein the steps of: creating subdirectories under the path of the script file summary directory of each time period; executing the script file in the verification library, judging whether the script file is abnormal or not, and importing the abnormal script file into the subdirectory under the script file summary directory of the current time period; and executing the non-abnormal script file in the formal library, and adding the script file after the execution is successful to the version upgrading script file.
The method comprises the steps of processing a script file in each cycle, respectively extracting commands of DDL and DML operations, executing the DDL operations on a verification library through an ojdbc driver call database execution method, capturing the DDL operations by a java try-catch if any exception is thrown in the execution process, simultaneously moving the file out of a memory, cutting the file per se to a path of ' executing failure script ', and adding an error log to ' description file ' txt '. Here "description document. Txt" is also memory resident for real-time updates. The memory is refreshed and the hard disk is written back at the same time every time the update is carried out. If the operation is successful, the DML operation is continuously executed, and if the operation fails to be executed by the copying DDL, the operation fails to be executed. If the success is successful, the submitted script file is correct, and the statements in the script file are executed on the formal library. And after the execution is successful, adding the script content to the version upgrading script. The steps are to complete the processing of all script files.
Preferably, the method further comprises: and creating a standard library and a verification library in the database environment, wherein the standard library is a formal library after continuous integration.
Preferably, the method further comprises: naming rules for the script file are defined. Preferably, the naming rule is: date _ submitter name _ module name _ description txt.
The application firstly uses Java IO technology to create a subdirectory under a daily script summary path, named as ' failure script execution ', and creates a ' description file. Loading daily submitted script File into memory, storing in List < File > set, checking name specification circularly, removing out memory not conforming to name specification and cutting script File into ' executing failure script ' directory, writing non-conforming reason into ' description File txt
Preferably, the script integration tool DBIT is developed by java language, and includes a preset timing task, and the timing task is executed by the task framework Quartz.
Preferably, the subdirectory further includes a text file for recording the cause of the abnormality of the script file.
Preferably, the database integrated environment is an oracle database integrated environment.
Preferably, the database is continuously integrated by submitting a script file.
Preferably, the script file includes: script files for different dates, different submitters, and different modules.
Preferably, submitting the script file to a script file collection directory of the current time period under the script file management directory includes:
the script file summary directory of the current time period is automatically generated by the script integration tool DBIT according to the date, and the generation time is after the script of the previous day is executed.
Preferably, session control is cleared on the validation library and the validation library is rebuilt using the formal library. In the application, the formal library is automatically backed up, then all sessions on the verification library are cleared and killed, then the verification library is deleted, and the formal library backup file is used for rebuilding the verification library. The series of operations adopt a mode of calling batch processing commands by java. Carrying out oracle exp commands in batch, and exporting the formal library to a backup path in a dmp file format; and then executing an alter system kill session command to kill all sessions connected with the verification library, then executing a drop user to delete the verification library, and finally executing creation user command reconstruction, wherein grant has all related oracle permissions and roles. This ensures that the validation library is always consistent with the formal library, so that the next pre-execution on the validation library can be consistent with the execution effect on the formal library. The embodiment of the invention well omits the complicated script verification, achieves the same effect by adopting a pre-execution mode, is more concise, and also prevents the problem of incomplete verification caused by the script verification.
Fig. 2 is a flowchart of a method for database persistent integration and script file management according to a preferred embodiment of the present invention. And continuously integrating the oracle database in a manner of submitting the script file. On different dates, different submitters and different modules may have script files, and for good management and error location, the naming rules of the submitted script files are as follows: "date _ submitter name _ module name _ description. The application uses the oracle integration environment exclusively to execute scripts. The integration environment includes a database environment, a script integration tool, DBIT, and a script management directory. Each submitter submits the script to a current day script summary directory under a script management directory, the directory is automatically generated by a script integration tool DBIT according to the date, and the generation time is after the script of the previous day is executed. The database environment includes an oracle standard library and a validation library. The standard library is a formal library after continuous integration, and the verification library is an environment for pre-executing the script. The execution of the script and the script management catalog are automatically and uniformly managed by a script integration tool DBIT. The script integration tool DBIT is developed by java language, setting timed tasks, such as starting at 10 nights per time period. Here implemented using a java timed task framework Quartz. As shown in FIG. 2, a method for database persistence integration and script file management includes:
1. first, a subdirectory named "execute failure script" is created under the daily script summary path using Java IO technology, and a "description file. Then loading the script files which are executed and handed over every day into a memory, storing the script files in a List < File > set, circularly checking the name specification in sequence, moving out the memory if the script files are not consistent, cutting the files into an ' execution failure script ' directory, and simultaneously writing the reasons of the non-compliance into an ' instruction File ' txt '.
2. Processing a script file in each cycle, respectively extracting commands of DDL and DML operations, firstly, calling a database execution method on a verification library through ojdbc drive to execute the DDL operations, capturing any exception thrown in the execution process by java try-catch, simultaneously, removing the file from a memory, cutting the file per se to a ' failure script ' path, and adding an error log to an ' instruction file ' txt '. Here "description. Txt" is also memory resident to be updated in real time. The memory is refreshed and written back to the hard disk at the same time each update. If the operation is successful, the DML operation is continuously executed, and if the operation fails to be executed by the copying DDL, the operation fails to be executed. If the script file is successful, the submitted script file is correct, and the statements in the script file are executed on the formal library. And after the execution is successful, the content of the script file is added to the version upgrading script file. The steps are to complete the processing of all script files.
3. And automatically backing up the formal library, then emptying and killing all sessions on the verification library, then deleting the verification library, and rebuilding the verification library by using backup files of the formal library. The series of operations adopt a mode of calling batch processing commands by java. Carrying out oracle exp commands in batch, and exporting the formal library to a backup path in a dmp file format; and then executing an alter system kill session command to kill all sessions connected with the verification library, then executing a drop user to delete the verification library, and finally executing creation user command reconstruction, wherein grant has all related oracle permissions and roles. This ensures that the validation library is always consistent with the formal library, so that the next pre-execution on the validation library can be consistent with the execution effect on the formal library. The implementation mode of the application well omits the heavy and complicated script verification, the same effect is achieved by adopting a pre-execution mode, the operation is more concise, and the problem of incomplete verification caused by the script verification is also prevented.
Because oracle contains field types such as blob, clob, etc., sql scripts are difficult to execute. The integration method of the present invention supports submission of dmp files. This operation is performed above for the last completion of sequence 2. Because the dmp file contents are not visible, more irrelevant tables may be exported due to a submitter's misoperations, which would then override the standard library. The scripting integration tool DBIT needs to read the dmp header information, confirming that it contains only one table and contains a blob, clob-type field.
To ensure correctness of script file submission, sql writing rules are specified, exporting preparation of the dmp file. The correctness of the submitted script needs to be considered in daily life. The designer needs to master the script writing rule of oracle; understanding the service flow and development technology of the system; and finally, the quality of the script submitted by the personnel is checked regularly, so that all members pay attention to the normalization and the correctness of the script all the time.
As everyone should confirm the performability of the script before submitting it to the script integration tool DBIT, it is necessary to have an environment completely consistent with the standard library for testing. The script integration tool is equipped to create a database to the pointing machine. Whenever the script file submitter sends a "request to build a library" command to the integration tool, the integration tool will automatically export the latest standard library backup file to the target machine to create the test library. The method is realized by combining technologies such as java design mode thought, message request and response, database command, batch scheduling and the like.
To ensure correctness of script submission, sql writing rules are specified, exporting the preparation of the dmp file. The daily training and standardized management of developers are also important. For experienced personnel, regular reminding and supervision are needed, so that the whole development team consciously attaches importance to the correctness of the submitted script. For the new member, training and guiding are carried out, so that the new member can master the script compiling rule of oracle; carrying out service training on the system, and enabling the system to know the service flow and development technology of the system; and finally, the quality of the script submitted by the personnel is checked regularly, so that all members pay attention to the normalization and the correctness of the script all the time. As everyone should confirm the performability of the script before submitting it to the script integration tool, it requires a completely consistent environment with the standard library for testing. The scripting integration tool is equipped to create a database function with the pointing machine. Whenever the script submitter sends a "request to build a library" command to the integration tool, the integration tool will automatically export the latest standard library backup files to the target machine to create the test library. The method is realized by combining technologies such as java design mode idea, message request and response, database command, batch processing scheduling and the like.
Fig. 3 is a diagram illustrating a system for database persistent integration and script file management, according to a preferred embodiment of the present invention. As shown in fig. 3, a system for database persistence integration and script file management, the system comprising:
a submitting unit 301, configured to submit the script file to a script file aggregation directory in the current time period under the script file management directory, and execute the script file in a database integration environment;
an integrating unit 302, configured to execute the script file and manage the script file under the summary directory through a script integration tool DBIT, including: creating subdirectories under the path of the script file summary directory of each time period; executing the script file in the verification library, judging whether the script file is abnormal or not, and importing the abnormal script file into the subdirectory under the script file summary directory of the current time period; and executing the non-abnormal script file in the formal library, and adding the script file after the execution is successful to the version upgrading script file.
The method comprises the steps of processing a script file in each cycle, respectively extracting commands of DDL and DML operations, executing the DDL operations on a verification library through an ojdbc driver call database execution method, capturing any exception thrown in the execution process by a java try-catch, simultaneously moving the file out of a memory, cutting the file per se to a path of ' execution failure script ' and adding an error log to ' description file ' txt '. Here "description document. Txt" is also memory resident for real-time updates. The memory is refreshed and written back to the hard disk at the same time each update. If successful, the DML operation continues to be executed, and if failed, the operation fails to be executed by the copy DDL. If the success is successful, the submitted script file is correct, and the statements in the script file are executed on the formal library. And after the execution is successful, the script content is added to the version upgrading script. And the steps are to finish the processing of all script files.
Preferably, the system further comprises: naming rules for the script file are defined. Preferably, the naming rule is: date _ submitter name _ module name _ description txt.
Preferably, the script integration tool DBIT is developed by java language, and includes a preset timing task, and the timing task is executed by the task framework Quartz.
Preferably, the subdirectory further includes a text file for recording the cause of the abnormality of the script file.
Preferably, the database integrated environment is an oracle database integrated environment.
Preferably, the database is continuously integrated by submitting a script file.
Preferably, the script file includes: script files for different dates, different submitters, and different modules.
Preferably, submitting the script file to a script file collection directory of the current time period under the script file management directory includes:
the script file summary directory of the current time period is automatically generated by the script integration tool DBIT according to the date, and the generation time is after the script of the previous day is executed.
Preferably, the system further comprises a building unit for creating a standard library and a verification library in the database environment, wherein the standard library is a formal library after continuous integration.
Preferably, session control on the validation library is cleared and the validation library is rebuilt using the formal library. In the application, the formal library is automatically backed up, then all sessions on the verification library are cleared and killed, then the verification library is deleted, and the formal library backup file is used for rebuilding the verification library. The series of operations adopt a mode of calling batch processing commands by java. Carrying out oracle exp commands in batch processing, and exporting the formal library to a backup path in a dmp file format; and then executing an alter system kill session command to kill all sessions connected with the verification library, then executing a drop user to delete the verification library, and finally executing creation user command reconstruction, wherein grant has all related oracle permissions and roles. This ensures that the validation library is always consistent with the formal library, so that the next pre-execution on the validation library can be consistent with the execution effect on the formal library. The embodiment of the invention well omits the complicated script verification, achieves the same effect by adopting a pre-execution mode, is more concise, and also prevents the problem of incomplete verification caused by the script verification.
The invention has been described with reference to a few embodiments. However, other embodiments of the invention than the one disclosed above are equally possible within the scope of the invention, as would be apparent to a person skilled in the art from the appended patent claims.
Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a/an/the [ device, component, etc ]" are to be interpreted openly as referring to at least one instance of said device, component, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.
Claims (18)
1. A method for database persistence integration and script file management, the method comprising:
submitting the script file to a script file collection directory of the current time period under the script file management directory, and executing the script file in a database integration environment, wherein the steps of:
the script file summarizing directory of the current time period is automatically generated by a script integration tool DBIT according to date, and the generation time is after the script of the previous day is executed;
executing the script file and managing the script file summary directory through a script integration tool DBIT, wherein the steps comprise:
creating sub-directories under the path of the script file summary directory of each time period;
executing a script file in a verification library, judging whether the script file is abnormal or not, and importing the abnormal script file into the subdirectory under the script file summary directory of the current time period;
executing the non-abnormal script file in a formal library, and adding the script file after successful execution to a version upgrading script file;
and clearing the session control on the verification library, and rebuilding the verification library by using the formal library.
2. The method of claim 1, further comprising: creating a standard library and a verification library in a database environment, wherein the standard library is a formal library after continuous integration.
3. The method of claim 1, further comprising:
defining a naming convention for the script file.
4. The method of claim 3, the naming convention being:
date _ submitter name _ module name _ description txt.
5. The method of claim 1, the script integration tool DBIT is developed by java language, comprising a preset timing task, the timing task is executed by a task framework Quartz.
6. The method of claim 1, wherein the sub-directory further comprises a text file for recording the reason for the abnormality of the script file.
7. The method of claim 1, the database integrated environment being an oracle database integrated environment.
8. The method of claim 1, wherein the database is continuously integrated by submitting a script file.
9. The method of claim 1, the script file comprising: script files for different dates, different submitters, and different modules.
10. A system for database persistence integration and script file management, the system comprising:
the submitting unit is used for submitting the script files to a script file collection directory of the current time period under the script file management directory, and executing the script files in a database integration environment, and comprises the following steps:
the script file summarizing directory of the current time period is automatically generated according to the date through a script integration tool DBIT, and the generation time is after the script of the previous day is executed;
the integration unit is used for executing the script file and managing the script file under the summary directory through a script integration tool DBIT, and comprises the following steps:
creating subdirectories under the path of the script file summary directory of each time period;
executing a script file in a verification library, judging whether the script file is abnormal or not, and importing the abnormal script file into the subdirectory under the script file summary directory of the current time period;
executing the non-abnormal script file in a formal library, and adding the script file after successful execution to a version upgrading script file;
and clearing the session control on the verification library, and rebuilding the verification library by using the formal library.
11. The system of claim 10, further comprising a building unit for creating a standards library and a validation library in the database environment, the standards library being a formal library after continued integration.
12. The system of claim 10, further comprising:
defining a naming convention for the script file.
13. The system of claim 12, the naming convention being:
date _ submitter name _ module name _ description txt.
14. The system of claim 10, the scripting integration tool DBIT is developed by java language, including pre-set timing tasks, which are executed by a task framework Quartz.
15. The system of claim 10, the subdirectory further comprising a text file for recording the cause of the abnormality of the script file.
16. The system of claim 10, the database integrated environment being an oracle database integrated environment.
17. The system of claim 10, wherein the database is continuously integrated by submitting a script file.
18. The system of claim 10, the script file comprising: script files for different dates, different submitters, and different modules.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811056204.1A CN109271199B (en) | 2018-09-11 | 2018-09-11 | Method and system for database continuous integration and script file management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811056204.1A CN109271199B (en) | 2018-09-11 | 2018-09-11 | Method and system for database continuous integration and script file management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109271199A CN109271199A (en) | 2019-01-25 |
| CN109271199B true CN109271199B (en) | 2023-01-10 |
Family
ID=65188409
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811056204.1A Active CN109271199B (en) | 2018-09-11 | 2018-09-11 | Method and system for database continuous integration and script file management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109271199B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111104155A (en) * | 2019-11-29 | 2020-05-05 | 北京浪潮数据技术有限公司 | Database script management platform and method, electronic equipment and storage medium |
| CN111209719A (en) * | 2019-12-31 | 2020-05-29 | 西安翔腾微电子科技有限公司 | Method, device, equipment and storage medium for automatically realizing IC design environment |
| CN112685077A (en) * | 2020-12-29 | 2021-04-20 | 平安普惠企业管理有限公司 | Data modification method, system, computer device and computer readable storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2003345594A (en) * | 2002-05-28 | 2003-12-05 | Japan Research Institute Ltd | Script file generating device and method for structuring data base |
| US6985901B1 (en) * | 1999-12-23 | 2006-01-10 | Accenture Llp | Controlling data collection, manipulation and storage on a network with service assurance capabilities |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8943181B2 (en) * | 2005-11-29 | 2015-01-27 | Ebay Inc. | Method and system for reducing connections to a database |
| CA2713247C (en) * | 2009-08-31 | 2015-06-16 | Accenture Global Services Gmbh | Integration environment generator |
| CN101694626B (en) * | 2009-09-30 | 2013-03-20 | 曙光信息产业(北京)有限公司 | Script execution system and method |
| CN101739340B (en) * | 2009-12-17 | 2012-06-06 | 金蝶软件（中国）有限公司 | Method and device for verifying script file |
| CN103279419A (en) * | 2013-06-09 | 2013-09-04 | 浪潮电子信息产业股份有限公司 | Automation version verifying method and system based on B/S structural system |
| CN104239583B (en) * | 2014-10-14 | 2017-08-01 | 北京国双科技有限公司 | Database script issues the processing method and processing device of result |
| CN105094961A (en) * | 2015-08-11 | 2015-11-25 | 北京思特奇信息技术股份有限公司 | Task scheduling management system based on quartz frame and method thereof |
| CN107092557A (en) * | 2017-03-24 | 2017-08-25 | 广东网金控股股份有限公司 | A kind of database schema upgrade script verification method and device |
-
2018
- 2018-09-11 CN CN201811056204.1A patent/CN109271199B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6985901B1 (en) * | 1999-12-23 | 2006-01-10 | Accenture Llp | Controlling data collection, manipulation and storage on a network with service assurance capabilities |
| JP2003345594A (en) * | 2002-05-28 | 2003-12-05 | Japan Research Institute Ltd | Script file generating device and method for structuring data base |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109271199A (en) | 2019-01-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7389104B2 (en) | Upgrading a database from a first version to a second version | |
| US7933869B2 (en) | Method and system for cloning a tenant database in a multi-tenant system | |
| US5778390A (en) | Method and systems for creating duplicating, and archiving database files | |
| US7917607B2 (en) | Software management systems and methods, including use of such systems and methods in a provider-tenant environment | |
| US8191044B1 (en) | System and method for maintaining requirements traceability | |
| US7401085B2 (en) | System and method for controlling the release of updates to a database configuration | |
| CN109271199B (en) | Method and system for database continuous integration and script file management | |
| US20070156849A1 (en) | Systems and methods for delivering software upgrades in a provider-tenant environment | |
| US8010578B2 (en) | Method of refactoring a running database system | |
| EP2194467A1 (en) | Extend CRUD to support lifecycle management and business continuity | |
| US20080162587A1 (en) | Server synchronization for maintenance activities | |
| US9971595B1 (en) | Techniques for automated database deployment | |
| US20050278397A1 (en) | Method and apparatus for automated redundant data storage of data files maintained in diverse file infrastructures | |
| US11960362B2 (en) | Systems and methods for consistent backup of distributed, transactional databases | |
| WO2020244445A1 (en) | Coverage information obtaining method and device | |
| Maymala | PostgreSQL for data architects | |
| CN112463447A (en) | Optimization method for realizing physical backup based on distributed database | |
| US20200117581A1 (en) | Configuration file updating system for use with cloud solutions | |
| US9946534B1 (en) | Techniques for automated database deployment | |
| US20090177705A1 (en) | System and method for using generic utilities to perform database utilities on mainframe operated DB2 databases | |
| CN107634957B (en) | Protocol agent-based real-time data and file operation pre-saving method and system | |
| Lim et al. | D-TAF: test automation framework compatible with various DBMS | |
| CN117149180A (en) | Application replication method, device, equipment and medium for low-code development | |
| Alapati et al. | Oracle Database 11g: New Features for DBAs and Developers | |
| Burns et al. | Oracle Database Upgrade Guide, 10g Release 2 (10.2) B14238-01 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |