CN111142899B - Database script execution method and device, storage medium and electronic equipment - Google Patents
Database script execution method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN111142899B CN111142899B CN201911288895.2A CN201911288895A CN111142899B CN 111142899 B CN111142899 B CN 111142899B CN 201911288895 A CN201911288895 A CN 201911288895A CN 111142899 B CN111142899 B CN 111142899B
- Authority
- CN
- China
- Prior art keywords
- script
- database
- executed
- version
- module
- 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
- 238000013515 script Methods 0.000 title claims abstract description 245
- 238000000034 method Methods 0.000 title claims abstract description 35
- 238000003860 storage Methods 0.000 title claims abstract description 10
- 230000010354 integration Effects 0.000 claims abstract description 36
- 238000012360 testing method Methods 0.000 claims abstract description 20
- 238000004519 manufacturing process Methods 0.000 claims abstract description 14
- 238000011161 development Methods 0.000 claims abstract description 13
- 230000002085 persistent effect Effects 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012423 maintenance Methods 0.000 abstract description 10
- 238000004891 communication Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 230000005236 sound signal Effects 0.000 description 4
- 238000007405 data analysis Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 238000005457 optimization Methods 0.000 description 2
- 238000012552 review Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- KLDZYURQCUYZBL-UHFFFAOYSA-N 2-[3-[(2-hydroxyphenyl)methylideneamino]propyliminomethyl]phenol Chemical compound OC1=CC=CC=C1C=NCCCN=CC1=CC=CC=C1O KLDZYURQCUYZBL-UHFFFAOYSA-N 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 201000001098 delayed sleep phase syndrome Diseases 0.000 description 1
- 208000033921 delayed sleep phase type circadian rhythm sleep disease Diseases 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000001066 destructive effect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1433—Saving, restoring, recovering or retrying at system level during software upgrading
Abstract
The disclosure relates to a method and a device for executing a database script, a storage medium and electronic equipment, which can realize automatic update and upgrade of a database in a DevOps, improve delivery efficiency, avoid error occurrence and reduce operation and maintenance cost. The method comprises the following steps: obtaining at least one database script from a version control module through a continuous integration module, wherein the continuous integration module is positioned in a development environment, a testing environment or a production environment of a DevOps; determining a script to be executed from the at least one database script according to the script version of the current running environment; and executing the script to be executed.
Description
Technical Field
The disclosure relates to the technical field of computers, and in particular relates to a database script execution method, a database script execution device, a storage medium and electronic equipment.
Background
The Development and Operations combination is a culture, movement or convention that pays attention to the communication cooperation between "software developer (Dev)" and "IT operation and maintenance technician (Ops)". The software can be built, tested and released more quickly, frequently and reliably through the processes of automatic software delivery and architecture change. The source code applied in the DevOps can realize the maintenance of the code version through a code management tool (such as Git), the effective maintenance of the code version can accelerate the delivery speed, the effective backtracking problem and the convenience of the upgrading and rollback of the application.
However, the updating and updating of the database usually adopts a manual mode, after a developer submits a database script, a notification is sent, after receiving the notification, a tester manually updates the script, and after the tester completes the test, the tester is notified to manually update in the production environment. Such a manner is inefficient, costly to operate and maintain, and prone to errors.
The rapid version iteration needs to be continuously integrated and issued, and the updating and updating of the SQL script also needs to have a new mode and method, so that the delivery efficiency is improved, errors are avoided, and the operation and maintenance cost is reduced.
Disclosure of Invention
The purpose of the present disclosure is to provide a method, an apparatus, a storage medium, and an electronic device for executing a database script, which can realize automatic update and upgrade of a database in a DevOps, improve delivery efficiency, avoid occurrence of errors, and reduce operation and maintenance costs.
According to a first aspect of embodiments of the present disclosure, there is provided a data analysis method, including:
obtaining at least one database script from a version control module through a continuous integration module, wherein the continuous integration module is positioned in a development environment, a testing environment or a production environment of a DevOps;
determining a script to be executed from the at least one database script according to the script version of the current running environment;
and executing the script to be executed.
Optionally, after determining the script to be executed from the at least one database script, the method further includes:
generating a rollback script according to the script to be executed, wherein the rollback script is used for rollback the running environment to a state before script execution when the script to be executed fails to execute;
and storing the rollback script.
Optionally, after executing the script to be executed, the method further includes:
if the script to be executed is successfully executed, recording a script version of the running environment after the execution is completed;
and if the script to be executed fails to execute, terminating a script executing program or executing the rollback script.
Optionally, the method further comprises:
generating a version fingerprint for the database script when the version control module receives the submitted database script;
determining a script to be executed from the at least one database script according to the script version of the current running environment, including:
and determining the unexecuted database script as the script to be executed according to the script version of the current running environment and the version fingerprint of each database script in the at least one database script.
Optionally, the database script submitted to the version control module is stored in a corresponding date folder according to the date of submission; obtaining, by the persistent integration module, at least one database script from the version control module, comprising:
and acquiring the at least one database script from the date folder corresponding to the version control module according to the current date through the continuous integration module.
Optionally, after the at least one database script is obtained from the version control module by the persistent integration module, the method further includes:
and carrying out grammar checking on the at least one database script.
Optionally, after determining the script to be executed from the at least one database script, the method further includes:
and outputting the script to be executed for manual auditing.
According to a second aspect of the embodiments of the present disclosure, there is provided a database script execution apparatus, including:
the system comprises an acquisition module, a version control module and a production environment, wherein the acquisition module is used for acquiring at least one database script from the version control module through a continuous integration module, wherein the continuous integration module is positioned in a development environment, a test environment or a production environment of the DevOps;
the determining module is used for determining a script to be executed from the at least one database script according to the script version of the current running environment;
and the execution module is used for executing the script to be executed.
According to a third aspect of embodiments of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the steps of the method of any of the first aspects.
According to a fourth aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:
a memory having a computer program stored thereon;
a processor for executing the computer program in the memory to implement the steps of the method of any of the first aspects.
In the disclosure, the persistent integration module in the development environment, the test environment or the production environment of the DevOps may acquire at least one database script from the version control module, and then determine, according to the script version of the current operating environment, a script to be executed, which needs to be executed in the current environment, from the at least one database script, so as to execute the script to be executed. Through the mode, the database script can be automatically updated and updated from development to operation and maintenance, the delivery efficiency is improved, meanwhile, manual intervention is not needed, errors are avoided, and the operation and maintenance cost is reduced.
Additional features and advantages of the present disclosure will be set forth in the detailed description which follows.
Drawings
The accompanying drawings are included to provide a further understanding of the disclosure, and are incorporated in and constitute a part of this specification, illustrate the disclosure and together with the description serve to explain, but do not limit the disclosure. In the drawings:
FIG. 1 is a flowchart illustrating database script execution according to an exemplary embodiment;
FIG. 2 is a schematic diagram of a DevOps environment, shown in accordance with an exemplary embodiment;
FIG. 3 is a schematic diagram illustrating a manner of generating rollback scripts in accordance with an exemplary embodiment;
FIG. 4 is a block diagram of a database script execution device, shown in accordance with an exemplary embodiment;
fig. 5 is a block diagram of an electronic device, according to an example embodiment.
Detailed Description
Specific embodiments of the present disclosure are described in detail below with reference to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating and illustrating the disclosure, are not intended to limit the disclosure.
Fig. 1 is a flowchart illustrating a data analysis method according to an exemplary embodiment, which may be applied to an electronic device, as shown in fig. 1, including the following steps.
Step S11: at least one database script is obtained from the version control module by the persistent integration module.
Step S12: and determining the script to be executed from at least one database script according to the script version of the current running environment.
Step S13: executing the script to be executed.
In the embodiment of the disclosure, the DevOps has a development environment, a test environment, and a production environment, and as shown in fig. 2, each environment includes a version control module and a persistent integration module, where the version control module may be, for example, a Git (distributed version control system) or other version control tools, and the persistent integration module may be, for example, jenkins (persistent integration tools). The environments may share the same version control module, so that different environments may acquire the database script from the same version control module, or the version control modules of the environments may be independent, so long as they can perform data synchronization.
The database script may be an incremental script, and executing the script may implement upgrading and updating of the database, or the database script may be a full-scale script, and executing the script may implement installation of a new program. The database script may be, for example, an SQL (Structured Query Language ) script, or may be other database scripts, as well, as the embodiments of the disclosure are not limited in this respect.
After the developer writes the database script, the database script can be submitted to the version control module, so that when the database is to be updated or updated, the continuous integration module can pull the database script from the version control module, then compare the version of the current database script, and further determine the script to be executed from the pulled script to execute, so as to realize automatic updating or updating of the database. In practical applications, the frequency of automatically updating the database may be set, and then, for example, the persistent integration module may be set to pull the script from the version control module once a day, or once every two days, and so on.
It should be understood that the continuously integrated modules of the DevOps environments are serially performing database updates in the order of development, testing, and production. Please continue to refer to fig. 2: (1) When the service requirement changes, a developer submits a new database script to a version control module (such as Git), and the application version is updated by a continuous integration module (such as Jenkins), so that the developer can manually update the database script and perform unit test and integration test; if the test fails, returning to the developer for modification; if the test is successful, the code is merged from the development stream to the test stream. (2) And (3) testing the environment, wherein a tester performs black box testing on the testing environment according to the version submitted by the developer and subjected to white box testing, and the database script is automatically updated. (3) And in the production environment, the operation and maintenance personnel perform online testing on the production environment according to the black box tested version submitted by the tester, and the database script is automatically updated at the moment. Therefore, the method for executing the database script from development to operation and maintenance is provided, and the delivery efficiency is improved.
In one possible implementation manner, after determining the script to be executed from the at least one database script, a rollback script may also be generated and stored according to the script to be executed, where the rollback script is used to rollback the running environment to a state before script execution when the script to be executed fails.
Referring to fig. 3, the database script is exemplified by an SQL script. The SQL update script (script to be executed) generally includes two parts, namely a table update including creation, modification, destruction, etc. of a table, and a data update including insertion, modification, deletion, etc. of table data. Corresponding to the update script, the SQL event type parsing finds the inverse logic (rollback logic) according to the SQL syntax dictionary table to generate the rollback script, which requires reading the database to obtain all information for rollback due to the loss of the database table or table record caused by the destructive update operation.
The embodiment of the disclosure can generate and store the rollback script so as to restore to the previous version when the database update fails, thereby improving the data reliability.
In one possible implementation manner, after executing the script to be executed, if the script to be executed is executed successfully, recording a script version of the running environment after the execution is completed; if the script to be executed fails to execute, the script executing program is terminated or the rollback script is executed.
That is, after the script to be executed is executed and the database is updated or updated successfully, the updated script version can be recorded, so that the comparison of the scripts can be performed when the database is updated next time, and whether to execute the new database script and which database scripts are executed can be confirmed. If the database is updated or fails to be updated, the execution of the program can be directly terminated, an error is returned, manual intervention is performed, or a rollback script can be directly executed to return to the version before the update. In this way, the reliability of the database can be improved.
In one possible implementation, when the version control module receives a submitted database script, a version fingerprint for the database script may be generated; the unexecuted database script may be determined as a script to be executed according to the script version of the current operating environment and the version fingerprint of each database script in the at least one database script.
The version fingerprints may be used to identify database scripts, one for each database script, and the embodiments of the present disclosure are not limited to representations of version fingerprints, such as unique serial code data generated using a full path based on MD5 (message digest algorithm), and so on. After the continuous integration module pulls the database scripts, the version fingerprints of the scripts running in the current environment can be compared with the version fingerprints of the pulled database scripts, so that the scripts needing to be executed are obtained, and the automatic database updating is facilitated.
In one possible implementation, the database scripts submitted to the version control module are stored in the corresponding date folder according to the date of submission, and then at least one database script can be obtained from the date folder corresponding to the version control module according to the current date through the persistent integration module.
In the version control module, scripts may be managed in a manner of creating a date folder, for example, a date format may be yyyymmd (e.g., 20190301), one date folder may contain one or more database scripts, and the naming of the database scripts may be customized by a programmer, such as naming based on functions, etc., but each database script corresponds to only one version fingerprint. When the continuous integration module acquires at least one database script, the continuous integration module may acquire the database script in a folder manner, for example, the continuous integration module is set to acquire the database script once a day, and then the continuous integration module may directly pull all database scripts in a date folder corresponding to the date of the present day. It should be understood that if there are a plurality of scripts to be executed that need to be executed, the scripts may be executed in the order of names of the scripts. Through the mode, the continuous integrated module does not need to pull all database scripts in the version control module, so that the operation amount is saved, and the efficiency is improved.
In one possible implementation, the at least one database script may be grammar checked after the at least one database script is obtained from the version control module by the persistence integration module.
The database script is, for example, an SQL script, and then, for example, based on an SQLAdvisor (an SQL optimization tool), the verification and optimization suggestion of the SQL grammar can be implemented, and at the same time, whether the script meets the format requirements can be checked. It should be understood that the grammar checking may also be performed after step S12, and that it is the script to be executed that is checked. The script can be checked and optimized in advance through grammar checking, which is beneficial to reducing error rate of script execution.
In one possible implementation, after determining the script to be executed from the at least one database script, the script to be executed may also be output for manual review.
Because in practical applications, a programmer may desire to check a script to be executed and then execute the script, the present disclosure may output the script after confirming the script to be executed, for example, output in a manner of printing a list of scripts to be executed for manual review by the programmer.
Referring to fig. 4, based on the same inventive concept, an embodiment of the present disclosure provides a database script execution apparatus 200, the apparatus 200 may include:
an obtaining module 201, configured to obtain at least one database script from a version control module through a persistent integration module, where the persistent integration module is located in a development environment, a testing environment, or a production environment of a DevOps;
a determining module 202, configured to determine, according to a script version of a current running environment, a script to be executed from the at least one database script;
and the execution module 203 is configured to execute the script to be executed.
Optionally, the apparatus 200 further includes:
the script generation module is used for generating a rollback script according to the script to be executed after determining the script to be executed from the at least one database script, wherein the rollback script is used for rollback the running environment to a state before script execution when the script to be executed fails to execute;
and the storage module is used for storing the rollback script.
Optionally, the apparatus 200 further includes:
the recording module is used for recording the script version of the running environment after the execution is completed if the execution of the script to be executed is successful after the script to be executed is executed;
and the processing module is used for terminating the script execution program or executing the rollback script if the execution of the script to be executed fails after the script to be executed is executed.
Optionally, the apparatus 200 further includes:
the version fingerprint generation module is used for generating a version fingerprint aiming at the database script when the version control module receives the submitted database script;
the determining module 202 is configured to:
and determining the unexecuted database script as the script to be executed according to the script version of the current running environment and the version fingerprint of each database script in the at least one database script.
Optionally, the database script submitted to the version control module is stored in a corresponding date folder according to the date of submission; the acquisition module 201 is configured to:
and acquiring the at least one database script from the date folder corresponding to the version control module according to the current date through the continuous integration module.
Optionally, the apparatus 200 further includes:
and the verification module is used for carrying out grammar verification on the at least one database script after the at least one database script is acquired from the version control module through the continuous integration module.
Optionally, the apparatus 200 further includes:
and the output module is used for outputting the script to be executed for manual auditing after determining the script to be executed from the at least one database script.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein. It should be understood that, while the foregoing modules of the disclosure are illustrated in a computer, in practical application, the modules may be distributed in different manners, such as, for example, each module being distributed in a computer, and embodiments of the disclosure are not limited thereto.
Fig. 5 is a block diagram of an electronic device 300, according to an example embodiment. As shown in fig. 5, the electronic device 300 may include: a processor 301, a memory 302. The electronic device 300 may also include one or more of a multimedia component 303, an input/output (I/O) interface 304, and a communication component 305.
The processor 301 is configured to control the overall operation of the electronic device 300 to perform all or part of the steps in the database script execution method described above. The memory 302 is used to store various types of data to support operation at the electronic device 300, which may include, for example, instructions for any application or method operating on the electronic device 300, as well as application-related data, such as contact data, transceived messages, pictures, audio, video, and the like. The Memory 302 may be implemented by any type or combination of volatile or non-volatile Memory devices, such as static random access Memory (Static Random Access Memory, SRAM for short), electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM for short), erasable programmable Read-Only Memory (Erasable Programmable Read-Only Memory, EPROM for short), programmable Read-Only Memory (Programmable Read-Only Memory, PROM for short), read-Only Memory (ROM for short), magnetic Memory, flash Memory, magnetic disk, or optical disk. The multimedia component 303 may include a screen and an audio component. Wherein the screen may be, for example, a touch screen, the audio component being for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signals may be further stored in the memory 302 or transmitted through the communication component 305. The audio assembly further comprises at least one speaker for outputting audio signals. The I/O interface 304 provides an interface between the processor 301 and other interface modules, which may be a keyboard, mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 305 is used for wired or wireless communication between the electronic device 300 and other devices. Wireless communication, such as Wi-Fi, bluetooth, near field communication (Near Field Communication, NFC for short), 2G, 3G or 4G, or a combination of one or more thereof, the corresponding communication component 305 may thus comprise: wi-Fi module, bluetooth module, NFC module.
In an exemplary embodiment, the electronic device 300 may be implemented by one or more application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASIC), digital signal processors (Digital Signal Processor, abbreviated as DSP), digital signal processing devices (Digital Signal Processing Device, abbreviated as DSPD), programmable logic devices (Programmable Logic Device, abbreviated as PLD), field programmable gate arrays (Field Programmable Gate Array, abbreviated as FPGA), controllers, microcontrollers, microprocessors, or other electronic components for executing the database script execution method described above.
In another exemplary embodiment, a computer readable storage medium is also provided, comprising program instructions which, when executed by a processor, implement the steps of the database script execution method described above. For example, the computer readable storage medium may be the memory 302 described above including program instructions executable by the processor 301 of the electronic device 300 to perform the data analysis method described above.
The preferred embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings, but the present disclosure is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solutions of the present disclosure within the scope of the technical concept of the present disclosure, and all the simple modifications belong to the protection scope of the present disclosure.
In addition, the specific features described in the foregoing embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, the present disclosure does not further describe various possible combinations.
Moreover, any combination between the various embodiments of the present disclosure is possible as long as it does not depart from the spirit of the present disclosure, which should also be construed as the disclosure of the present disclosure.
Claims (10)
1. A method of database script execution, the method comprising:
obtaining at least one database script from a version control module through a continuous integration module, wherein the continuous integration module is positioned in a development environment, a testing environment or a production environment of a DevOps;
determining a script to be executed from the at least one database script according to the script version of the current running environment;
and executing the script to be executed.
2. The method of claim 1, further comprising, after determining a script to be executed from the at least one database script:
generating a rollback script according to the script to be executed, wherein the rollback script is used for rollback the running environment to a state before script execution when the script to be executed fails to execute;
and storing the rollback script.
3. The method of claim 2, further comprising, after executing the script to be executed:
if the script to be executed is successfully executed, recording a script version of the running environment after the execution is completed;
and if the script to be executed fails to execute, terminating a script executing program or executing the rollback script.
4. A method according to any one of claims 1-3, wherein the method further comprises:
generating a version fingerprint for the database script when the version control module receives the submitted database script;
determining a script to be executed from the at least one database script according to the script version of the current running environment, including:
and determining the unexecuted database script as the script to be executed according to the script version of the current running environment and the version fingerprint of each database script in the at least one database script.
5. A method according to any one of claims 1-3, wherein database scripts submitted to the version control module are stored in corresponding date folders according to date of submission; obtaining, by the persistent integration module, at least one database script from the version control module, comprising:
and acquiring the at least one database script from the date folder corresponding to the version control module according to the current date through the continuous integration module.
6. A method according to any one of claims 1-3, further comprising, after retrieving at least one database script from the version control module by the persistent integration module:
and carrying out grammar checking on the at least one database script.
7. A method according to any one of claims 1-3, further comprising, after determining a script to be executed from the at least one database script:
and outputting the script to be executed for manual auditing.
8. A database script execution apparatus, the apparatus comprising:
the system comprises an acquisition module, a version control module and a production environment, wherein the acquisition module is used for acquiring at least one database script from the version control module through a continuous integration module, wherein the continuous integration module is positioned in a development environment, a test environment or a production environment of the DevOps;
the determining module is used for determining a script to be executed from the at least one database script according to the script version of the current running environment;
and the execution module is used for executing the script to be executed.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the steps of the method according to any one of claims 1-7.
10. An electronic device, comprising:
a memory having a computer program stored thereon;
a processor for executing the computer program in the memory to implement the steps of the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911288895.2A CN111142899B (en) | 2019-12-12 | 2019-12-12 | Database script execution method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911288895.2A CN111142899B (en) | 2019-12-12 | 2019-12-12 | Database script execution method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111142899A CN111142899A (en) | 2020-05-12 |
| CN111142899B true CN111142899B (en) | 2024-03-22 |
Family
ID=70518273
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911288895.2A Active CN111142899B (en) | 2019-12-12 | 2019-12-12 | Database script execution method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111142899B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111736865B (en) * | 2020-05-28 | 2023-07-14 | 苏州浪潮智能科技有限公司 | Database upgrading method and system |
| CN112130891B (en) * | 2020-09-23 | 2021-06-29 | 上海逸迅信息科技有限公司 | Method and equipment for continuously deploying database |
| CN112181485B (en) * | 2020-10-20 | 2024-03-15 | 平安银行股份有限公司 | Script execution method and device, electronic equipment and storage medium |
| CN112099806A (en) * | 2020-11-05 | 2020-12-18 | 四川新网银行股份有限公司 | CICD-based sql automatic auditing online and executing method |
| CN112632159B (en) * | 2020-12-01 | 2021-09-28 | 腾讯科技（深圳）有限公司 | Database access control method and device, electronic equipment and storage medium |
| CN113297028A (en) * | 2021-03-18 | 2021-08-24 | 中国平安人寿保险股份有限公司 | Script execution method and device, computer equipment and storage medium |
| CN113420010B (en) * | 2021-06-23 | 2023-05-26 | 中国建设银行股份有限公司 | Database management method, device, electronic equipment and storage medium |
| CN117348916B (en) * | 2023-12-06 | 2024-03-26 | 中邮消费金融有限公司 | Script generation method, device, equipment and storage medium |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106126679A (en) * | 2016-06-29 | 2016-11-16 | 江苏电力信息技术有限公司 | A kind of exploitation O&M application process of cloud service-oriented |
| CN106873975A (en) * | 2016-12-30 | 2017-06-20 | 武汉默联股份有限公司 | Devops based on Docker persistently pays and automated system and method |
| CN106997297A (en) * | 2017-03-31 | 2017-08-01 | 广东亿迅科技有限公司 | A kind of software development management platform and method based on DevOps |
| CN107621944A (en) * | 2017-09-22 | 2018-01-23 | 天翼电子商务有限公司 | Continuous integrating pipeline system and its method based on automation O＆M |
| CN108874650A (en) * | 2017-05-09 | 2018-11-23 | 上海秦苍信息科技有限公司 | A kind of continuous integrating automated testing method |
| CN109189680A (en) * | 2018-08-24 | 2019-01-11 | 苏州玩友时代科技股份有限公司 | A kind of system and method for application publication and configuration |
| CN110196731A (en) * | 2018-10-29 | 2019-09-03 | 腾讯科技（深圳）有限公司 | A kind of operational system, method and storage medium |
| CN110209421A (en) * | 2019-05-23 | 2019-09-06 | 北京奥鹏远程教育中心有限公司 | For educating the automation continuous integrating management method of cloud platform |
| CN110262806A (en) * | 2019-06-20 | 2019-09-20 | 杭州泰然鲸数云计算有限公司 | A kind of DevOps system for supporting automation services layout |
| CN110321152A (en) * | 2019-07-04 | 2019-10-11 | 青岛华正信息技术股份有限公司 | A kind of Software Development Platform |
-
2019
- 2019-12-12 CN CN201911288895.2A patent/CN111142899B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106126679A (en) * | 2016-06-29 | 2016-11-16 | 江苏电力信息技术有限公司 | A kind of exploitation O&M application process of cloud service-oriented |
| CN106873975A (en) * | 2016-12-30 | 2017-06-20 | 武汉默联股份有限公司 | Devops based on Docker persistently pays and automated system and method |
| CN106997297A (en) * | 2017-03-31 | 2017-08-01 | 广东亿迅科技有限公司 | A kind of software development management platform and method based on DevOps |
| CN108874650A (en) * | 2017-05-09 | 2018-11-23 | 上海秦苍信息科技有限公司 | A kind of continuous integrating automated testing method |
| CN107621944A (en) * | 2017-09-22 | 2018-01-23 | 天翼电子商务有限公司 | Continuous integrating pipeline system and its method based on automation O＆M |
| CN109189680A (en) * | 2018-08-24 | 2019-01-11 | 苏州玩友时代科技股份有限公司 | A kind of system and method for application publication and configuration |
| CN110196731A (en) * | 2018-10-29 | 2019-09-03 | 腾讯科技（深圳）有限公司 | A kind of operational system, method and storage medium |
| CN110209421A (en) * | 2019-05-23 | 2019-09-06 | 北京奥鹏远程教育中心有限公司 | For educating the automation continuous integrating management method of cloud platform |
| CN110262806A (en) * | 2019-06-20 | 2019-09-20 | 杭州泰然鲸数云计算有限公司 | A kind of DevOps system for supporting automation services layout |
| CN110321152A (en) * | 2019-07-04 | 2019-10-11 | 青岛华正信息技术股份有限公司 | A kind of Software Development Platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111142899A (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111142899B (en) | Database script execution method and device, storage medium and electronic equipment | |
| CN115039084A (en) | Unit testing of components of a dataflow graph | |
| US11573780B2 (en) | Automated generation of status chains for software updates | |
| CN113515297B (en) | Version updating method and device, electronic equipment and storage medium | |
| CN112379940B (en) | Executable file processing method and device, electronic equipment and storage medium | |
| CN112463303A (en) | JAVA virtual machine class loading method and system | |
| US20140359077A1 (en) | Method and apparatus for transmitting symbol files | |
| CN110968339B (en) | Method and device for front-end building tool and electronic equipment | |
| US7921417B2 (en) | Method and computer system for activation of source files | |
| CN112711602B (en) | Method and device for running stored procedure, database system and storage medium | |
| CN113901025A (en) | Database management method, device, equipment and storage medium | |
| CN113220586A (en) | Automatic interface pressure test execution method, device and system | |
| CN112612474A (en) | Product transplanting method and device, storage medium and electronic equipment | |
| CN111142965A (en) | Language configuration method and device, electronic equipment and storage medium | |
| CN106681914B (en) | Television picture quality debugging method and device | |
| CN116680171B (en) | Test method, device, storage medium and electronic equipment | |
| CN112256554B (en) | Method and equipment for testing based on scene test cases | |
| CN110990475B (en) | Batch task inserting method and device, computer equipment and storage medium | |
| CN113448825A (en) | Method, device, equipment and storage medium for determining newly added software defect | |
| CN112035374A (en) | Regression testing method and system and electronic equipment | |
| CN111915279A (en) | Method, device and system for auditing job data flow | |
| CN113377400A (en) | Software upgrading method and device, storage medium and electronic equipment | |
| CN116501631A (en) | Test method, test device, electronic equipment and computer readable storage medium | |
| CN116150758A (en) | Vulnerability detection method, vulnerability detection device, communication equipment and computer readable storage medium | |
| CN117493159A (en) | Application testing method and device, electronic equipment and readable storage medium |
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 |