CN115687292A - Verifiable database upgrading method irrelevant to database technology - Google Patents

Abstract

The invention relates to the technical field of computers, in particular to a database upgrading method which can be verified and is irrelevant to database technology, comprising the following steps: generating a standard upgrading statement and generating a standard verification statement corresponding to the standard upgrading statement; packing the standard upgrading statement and the standard verifying statement as an upgrading packet and sending the upgrading packet to target equipment; unpacking the upgrading packet by the target equipment, analyzing the standard upgrading statement into an upgrading statement conforming to the type of the local database, and analyzing the standard verification statement into a verification statement conforming to the type of the local database; the target equipment executes an upgrade statement; and the target equipment executes the verification statement, if the verification is passed, the upgrade is fed back successfully, otherwise, the upgrade is fed back unsuccessfully and the target equipment is rolled back to the state before the upgrade statement is executed. The beneficial technical effects of the invention are as follows: the method and the system have the advantages that technicians do not need to consider specific database types when making codes, so that the efficiency of the technicians is improved, and the safety of database upgrading is improved.

Description

A Verifiable Database Upgrade Method Independent of Database Technology

technical field

The invention relates to the field of computer technology, in particular to a verifiable database upgrading method independent of database technology.

Background technique

It is a common situation in software projects that the database needs to be upgraded in the project. Upgrading a deployed database is a tedious and careful task. Changes to database table properties, field property changes, and field value changes all belong to the category of database upgrades. For a distributed system, the database is deployed on multiple terminal devices or cloud devices, and the types of local databases on the devices are different, which further increases the workload and difficulty of database upgrades. Seriously affect the work efficiency and project progress of project developers. Therefore, it is necessary to study a database-independent database upgrade method that can break away from the database type.

For example, Chinese patent CN105468717A, published on April 6, 2016, discloses a database operation method and device, the method includes: receiving a database operation request for the target database, the database operation request includes: the type identification of the target database, the target The operation identification of the preset database operation performed by the database, wherein each operation identification is preset to correspond to a plurality of database operations performed by different types of databases respectively; determine the operation identification performed by the type of database indicated by the type identification Corresponding database operation: Execute the determined database operation on the target database. Its technical solution realizes the unification of operation logic, operation interface and operation method for different types of databases, but its technical solution cannot solve the upgrade of irrelevant types of databases.

Contents of the invention

Technical problem to be solved by the present invention: Currently, there is a lack of technical problems that can realize database-independent database upgrade solutions. A verifiable database upgrade method independent of database technology is proposed, which can effectively improve the database upgrade efficiency of distributed projects.

To solve the above-mentioned technical problems, the present invention adopts the following technical solutions: a verifiable database upgrade method that has nothing to do with database technology, including: generating a standard upgrade statement, and generating a standard verification statement corresponding to the standard upgrade statement;

Package the standard upgrade statement and the standard verification statement as an upgrade package and send it to the target device;

The target device unpacks the upgrade package, parses the standard upgrade statement into an upgrade statement that matches the type of the local database, and parses the standard verification statement into a verification statement that matches the type of the local database;

The target device executes the upgrade statement;

The target device executes the verification statement. If the verification is passed, it will report that the upgrade is successful. Otherwise, it will report that the upgrade has failed and roll back to before the execution of the upgrade statement.

Preferably, the method for generating a standard upgrade statement includes:

List the upgrade statements of various databases, and group the upgrade statements with the same function;

Associating a semantic replacement statement for each group of upgrade statements, the semantic replacement statement includes a function identifier for representing a database operation and several parameter placeholders for recording statement parameters;

Associating each upgrade statement in each group with a mapper used to indicate the mapping relationship between the parameter placeholder and the upgrade statement content, forming an upgrade statement comparison table;

Write an upgrade statement for any database according to the upgrade content and then convert it into a corresponding semantic replacement statement, or directly write a semantic replacement statement, which is a standard upgrade statement.

Preferably, the method for generating a standard verification statement includes:

Associating each upgrade statement with a verification execution statement and a verification condition statement, the verification execution statement is a database operation statement, and the verification condition statement judges the upgrade result according to the output of the database;

The verification execution statements associated with the same group of upgrade statements are divided into one group, and each group of verification execution statements is associated with a standard verification execution statement. parameter placeholders;

Associating each standard verification execution statement with a mapper indicating the mapping relationship between the parameter placeholder and the verification execution statement to form a verification statement comparison table;

The verification condition statements associated with the same group of upgrade statements are divided into one group, and standard condition statements are generated for each group of verification condition statements, and the standard condition statements include attribute extraction words, attribute condition words and condition parameter placeholders;

For each standard verification execution statement, associate and record the mapper of the mapping relationship between the condition parameter placeholder and the verification condition statement to form a condition statement comparison table;

According to the verification statement comparison table and the condition statement comparison table, a standard verification execution statement and a standard condition statement corresponding to the upgrade statement are obtained, and the standard verification execution statement and the standard condition statement constitute a standard verification statement.

Preferably, the method further includes: uploading the upgrade statement comparison table, the verification statement comparison table and the condition statement comparison table to the network storage device;

The method for the target device to parse the standard upgrade statement into an upgrade statement that matches the type of the local database is as follows:

Query the upgrade statement comparison table to obtain the upgrade statement that matches the database type of the target device in the group where the standard upgrade statement is located;

Map the parameters in the standard upgrade statement to the upgrade statement according to the mapper, and complete the analysis;

The method of parsing the standard verification statement into a verification statement that matches the type of the local database is:

Query the verification statement comparison table to obtain the verification execution statement and verification condition statement that meet the target number in the group where the standard verification execution statement is located;

The parameters in the standard verification execution statement are mapped to the verification execution statement according to the mapper, and the parameters in the standard conditional statement are mapped to the verification conditional statement according to the mapper to complete the parsing.

Preferably, the method for the target device to execute the upgrade statement includes:

Determine the execution object of the upgrade statement, if the execution object is a database, execute the upgrade statement directly;

If the execution object is a table of the database, create a copy of the table, the copy of the table maintains the structure of the table, and copies the data of several tables;

Replace the execution object of the execution statement with a copy of the table, and execute it on the copy of the table;

Use the verification statement to verify the upgrade result of the copy of the table. If the upgrade is successful, execute the next step. If the upgrade fails, delete the copy of the table and end the database upgrade;

Delete the copy of the table, restore the execution object of the execution statement and execute it;

Use the verify statement to verify the result of the upgrade.

Preferably, the method for associating each upgrade statement with a verification execution statement includes:

Manually create a collection of verification execution statements for each database type;

The database instance created for each database type is recorded as an auxiliary instance, and several instance tables are generated on the auxiliary instance;

Read the upgrade statements in the upgrade statement comparison table in turn, manually fill in the parameters in the semantic replacement statement, so that the parameters point to the auxiliary instance and/or the example table;

Map the parameters in the semantic replacement statement to the upgrade statement to form an executable upgrade statement, and execute the executable upgrade statement on the auxiliary instance;

Try to fill in the parameters in the semantic replacement statement into the verification execution statement in the verification execution statement set, and execute the verification execution statement on the auxiliary instance in turn;

Screen out the verification execution statements that are incorrectly executed, and use the verification execution statements that are successfully executed on the auxiliary instance as suggestions to correlate the verification execution statements for manual selection.

Preferably, the method further includes: for the verification execution statement that can be executed successfully, obtaining the output content of the verification execution statement;

Change the parameters in the executable upgrade statement in turn, and execute the executable upgrade statement again;

After any parameter is changed, a verification execution statement with different output content is obtained as a suggested associated verification execution statement for manual selection.

The beneficial technical effects of the present invention are as follows: standard statements for making database upgrade statements and verification statements, so that technicians do not need to consider specific database types when making codes, improve the efficiency of technicians, and speed up project research and development; Judging whether the database upgrade is successful is helpful for troubleshooting early and improving the security of the database upgrade.

Other features and advantages of the present invention will be disclosed in detail in the following specific embodiments and drawings.

Description of drawings

Below in conjunction with accompanying drawing, the present invention will be further described:

FIG. 1 is a schematic flowchart of a method for upgrading a verifiable database according to an embodiment of the present invention.

FIG. 2 is a schematic flowchart of a method for generating a standard upgrade statement according to Embodiment 1 of the present invention.

FIG. 3 is a schematic flowchart of a method for generating standard verification sentences according to Embodiment 1 of the present invention.

FIG. 4 is a schematic flowchart of a method for parsing a target device according to Embodiment 1 of the present invention.

FIG. 5 is a schematic flowchart of a method for executing a statement associated with an upgrade statement in Embodiment 2 of the present invention.

Detailed ways

The technical solutions of the embodiments of the present invention will be explained and described below in conjunction with the accompanying drawings of the embodiments of the present invention, but the following embodiments are only preferred embodiments of the present invention, not all of them. Based on the examples in the implementation manners, other examples obtained by those skilled in the art without making creative efforts all belong to the protection scope of the present invention.

In the following description, terms such as "inner", "outer", "upper", "lower", "left", "right" etc. appearing to indicate orientation or positional relationship are only for the convenience of describing the embodiment and simplifying the description, rather than Nothing indicating or implying that a referenced device or element must have a particular orientation, be constructed, and operate in a particular orientation should therefore not be construed as limiting the invention.

Embodiment one:

A verifiable database upgrade method that has nothing to do with database technology, please refer to Figure 1, including:

Step A01) generating a standard upgrade statement, and generating a standard verification statement corresponding to the standard upgrade statement;

Step A02) Packing the standard upgrade statement and the standard verification statement as an upgrade package and sending it to the target device;

Step A03) The target device unpacks the upgrade package, parses the standard upgrade statement into an upgrade statement consistent with the type of the local database, and parses the standard verification statement into a verification statement consistent with the type of the local database;

Step A04) The target device executes the upgrade statement;

Step A05) The target device executes the verification statement. If the verification is passed, it will report that the upgrade is successful; otherwise, it will report that the upgrade has failed and roll back to before the execution of the upgrade statement.

For a distributed system, there are multiple server devices and terminal devices in the system, and the server devices and terminal devices are all connected to the Internet, but the types of databases on the devices are different. For the project management system, the same system has multiple enterprise users, and the same system will be deployed on the devices of multiple enterprise users to support the business of each enterprise user. Different enterprise users' devices support different database types. However, when the system is upgraded, sometimes the database needs to be adjusted. At this time, the same upgrade content is involved, and it needs to be executed on multiple databases of different types. When developing upgrade content, technicians need to consider the upgrade statement and verification statement of each database, which will lead to bloated code for project development, seriously affect development efficiency, and affect the stability and reliability of the database.

As shown in Table 1, some standard upgrade statements supported by this embodiment are listed. A standard upgrade statement is an expression expressed in a high-level language. Each standard upgrade statement is associated with a standard verification statement. The standard upgrade statements shown in Table 1 are respectively adding a field in a table, setting or changing attributes of a field, and deleting a field. The corresponding standard verification statement is to check whether the corresponding field exists in the table, and whether the attribute of the field is the specified attribute. If it exists and the attributes match, the output of the standard verification statement is true, otherwise, the output is false. For adding fields and setting field attributes, when the output of the standard verification statement is true, it indicates that the database upgrade is successful. For deleted fields, when the output of the standard validation statement is false, it indicates that the database upgrade was successful. When developing a project, technicians only need to write standard upgrade statements and standard verification statements. There is no need to consider different database types.

Table 1 Standard upgrade statement and standard verification statement established in this embodiment

Please refer to accompanying drawing 2, the method of generating standard upgrade statement includes:

Step B01) List the upgrade statements of various databases, and group the upgrade statements with the same function;

Step B02) associating a semantic replacement statement for each group of upgrade statements, the semantic replacement statement includes a function identifier for representing database operations and several parameter placeholders for recording statement parameters;

Step B03) Associating each upgrade statement in each group with a mapping symbol for indicating the mapping relationship between the parameter placeholder and the upgrade statement content, forming an upgrade statement comparison table;

Step B04) Write an upgrade statement of any type of database according to the upgrade content and then convert it into a corresponding semantic replacement statement, or directly write a semantic replacement statement, which is a standard upgrade statement.

Table 2 Comparison table of partial upgrade statements established in this embodiment

As shown in Table 2, it is an upgrade statement comparison table of the standard upgrade statement UpgradeAdd() established in this embodiment. The corresponding execution statements of different database types are recorded in the table. The table name, C1, T1, L1, B1, C2, T2, L2, and B2 are parameter placeholders. At the same time, the name of the parameter placeholder also indicates the mapping relationship between the parameter placeholder and the content of the upgrade statement, that is, it also serves as a mapper. For example, UpgradeAdd(op,A,x1,int) corresponds to the MySQL database, and the corresponding upgrade statement is ALTERTABLEAADDCOLUMNx1int, and it is AltertableAaddx1int for the SQLServer database. The upgrade statement comparison table records the corresponding execution statements of all supported standard upgrade statements under various database types. As long as it is the database type recorded in the upgrade statement comparison table, the standard upgrade statement can be converted into the execution statement of the corresponding database type. Complete the database upgrade. In order to improve the stability of the database upgrade, it is recommended to operate only one field or one table at a time.

Please refer to accompanying drawing 3, the method of generating standard verification statement includes:

Step C01) Associating a verification execution statement and a verification condition statement for each upgrade statement, the verification execution statement is a database operation statement, and the verification condition statement judges the upgrade result according to the output of the database;

Step C02) The verification execution statements associated with the same group of upgrade statements are divided into one group, and each group of verification execution statements is associated with a standard verification execution statement. The standard verification execution statement includes a function identifier for representing a database operation and an identifier for recording statement parameters. Several parameter placeholders;

Step C03) Associating each verification execution statement with a mapper indicating the mapping relationship between the parameter placeholder and the standard verification execution statement, forming a comparison table of verification statements, as shown in Table 4;

Step C04) The verification condition statements associated with the same group of upgrade statements are divided into one group, and a standard condition statement is generated for each group of verification condition statements. The standard condition statement includes attribute extraction words, attribute condition words and condition parameter placeholders;

Step C05) For each standard verification execution statement, associate and record the mapper of the mapping relationship between the condition parameter placeholder and the verification condition statement to form a condition statement comparison table, as shown in Table 5;

Step C06) According to the verification statement comparison table and the conditional statement comparison table, the standard verification execution statement and the standard conditional statement corresponding to the upgrade statement are obtained, and the standard verification execution statement and the standard conditional statement constitute the standard verification statement.

Table 3 This embodiment establishes the association table of upgrade statement, verification execution statement and verification condition statement

As shown in Table 3, the verification execution statement and the conditional statement of the upgrade statement that adds fields to the table in the same group are recorded. The verification execution statement and conditional statement recorded in Table 3 are respectively the verification execution statement and conditional statement of the same group. Associate the standard verification execution statement and the standard condition statement for the same group of verification execution statements and conditional statements. Table 3 shows that the standard verification execution statement is the same in form as the verification execution statement of the example database type, because various database types use exactly the same statement.

Wherein, OUT represents the output that the standard verification execution statement executes, and the attribute extraction word in the standard condition statement OUT= R is OUT, promptly extracts the whole output of the standard verification execution statement, and the attribute condition word is =, that is, the condition is equal to, and the condition parameter accounts for The bit symbol is R. The standard conditional statement OUT! = The attribute condition word of R is! =, and the rest are the same as the standard conditional statement OUT= R . When writing the standard condition statement of the standard upgrade statement UpgradeAdd(), R should be assigned a value of true at the same time.

Table 4 Part of the verification statement comparison table established in this embodiment

Table 5 The comparison table of some conditional statements established in this embodiment

Upload the upgrade statement comparison table, verification statement comparison table, and condition statement comparison table to the network storage device. Please refer to Figure 4, the method for the target device to parse the standard upgrade statement into an upgrade statement that matches the type of the local database is as follows:

Step D01) Query the upgrade statement comparison table, and obtain the upgrade statement that meets the target device database type in the group where the standard upgrade statement is located;

Step D02) The parameters in the standard upgrade statement are mapped to the upgrade statement according to the mapping symbols, and the analysis is completed;

The method of parsing the standard verification statement into a verification statement that matches the type of the local database is:

Step D03) Query the verification statement comparison table, and obtain the verification execution statement and the verification condition statement that meet the target number in the group where the standard verification execution statement is located;

Step D04) The parameters in the standard verification execution statement are mapped to the verification execution statement according to the mapping symbols, and the parameters in the standard condition statement are mapped to the verification condition statements according to the mapping symbols to complete the parsing. Send the upgrade statement comparison table and verification statement comparison table to each terminal, or upload it to the network storage device, and read the upgrade statement comparison table and verification statement comparison table through the access link. The cloud device or terminal device can query the upgrade statement comparison table and the verification statement comparison table to obtain the upgrade statement, verification execution statement and verification condition statement corresponding to the local database type.

Methods for target devices to execute upgrade statements include:

Determine the execution object of the upgrade statement, if the execution object is a database, execute the upgrade statement directly;

If the execution object is a table of the database, create a copy of the table, the copy of the table maintains the structure of the table, and copies the data of several tables;

Replace the execution object of the execution statement with a copy of the table, and execute it on the copy of the table;

Use the verification statement to verify the upgrade result of the copy of the table. If the upgrade is successful, execute the next step. If the upgrade fails, delete the copy of the table and end the database upgrade;

Delete the copy of the table, restore the execution object of the execution statement and execute it;

Use the verify statement to verify the result of the upgrade.

If the execution object is a table of the database, make a copy of the table, the copy has the same table structure, and copy several rows of data to the copy. Perform the upgrade on the replica first, and if the upgrade is successful, perform the upgrade on the original table. If the execution is unsuccessful, the database upgrade operation is terminated.

The beneficial technical effects of this embodiment are: making standard statements for database upgrade statements and verification statements, so that technicians do not need to consider specific database types when making codes, improve the efficiency of technicians, and speed up the progress of project research and development; Timely judging whether the database upgrade is successful will help to troubleshoot early and improve the security of the database upgrade.

Embodiment two:

A verifiable database upgrade method independent of database technology, this embodiment provides a technical solution to speed up the efficiency of association verification execution statements on the basis of the first embodiment. Please refer to accompanying drawing 5, the method for associating verification execution statement with each upgrade statement includes:

Step E01) manually making a set of verification execution statements for each database type;

Step E02) Create a database instance of each database type as an auxiliary instance, and generate several example tables on the auxiliary instance;

Step E03) sequentially read the upgrade statements in the upgrade statement comparison table, manually fill in the parameters in the semantic replacement statement, so that the parameters point to the auxiliary instance and/or the example table;

Step E04) Map the parameters in the semantic replacement statement to the upgrade statement to form an executable upgrade statement, and execute the executable upgrade statement on the auxiliary instance;

Step E05) Attempt to fill in the parameters in the semantic replacement statement into the verification execution statement in the verification execution statement set, and execute the verification execution statement on the auxiliary instance in turn;

Step E06) Screening out the wrong verification execution statements, and using the verification execution statements successfully executed on the auxiliary instance as suggested associated verification execution statements for manual selection.

More advantageously, for the verification execution statement that can be successfully executed, the output content of the verification execution statement is obtained; the parameters in the executable upgrade statement are changed in turn, and the executable upgrade statement is executed again; after any parameter is changed, the output Verification execution sentences with different content are used as suggestions to associate verification execution sentences for manual selection.

Compared with Embodiment 1, this embodiment can provide manuals with recommended sentences for associated verification execution sentences and verification condition sentences, making it more convenient and quicker to manually associate verification execution sentences, improve the efficiency of manual verification execution sentences, and further improve the efficiency of project research and development .

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto, and those skilled in the art should understand that the present invention includes but is not limited to the accompanying drawings and the description in the above specific embodiments content. Any modifications that do not depart from the functional and structural principles of the present invention will be included in the scope of the claims.

Claims (7)

1. A verifiable database upgrade method independent of database technology, characterized in that, include: Generate a standard upgrade statement and generate a standard verification statement corresponding to the standard upgrade statement; Package the standard upgrade statement and the standard verification statement as an upgrade package and send it to the target device; The target device unpacks the upgrade package, parses the standard upgrade statement into an upgrade statement that matches the type of the local database, and parses the standard verification statement into a verification statement that matches the type of the local database; The target device executes the upgrade statement; The target device executes the verification statement. If the verification is passed, it will report that the upgrade is successful. Otherwise, it will report that the upgrade has failed and roll back to before the execution of the upgrade statement. 2. A verifiable database upgrade method independent of database technology according to claim 1, wherein the method for generating a standard upgrade statement comprises: List the upgrade statements of various databases, and group the upgrade statements with the same function; Associating a semantic replacement statement for each group of upgrade statements, the semantic replacement statement includes a function identifier for representing a database operation and several parameter placeholders for recording statement parameters; Associating each upgrade statement in each group with a mapper used to indicate the mapping relationship between the parameter placeholder and the upgrade statement content, forming an upgrade statement comparison table; Write an upgrade statement for any database according to the upgrade content and then convert it into a corresponding semantic replacement statement, or directly write a semantic replacement statement, which is a standard upgrade statement. 3. A verifiable database upgrade method independent of database technology according to claim 2, wherein the method for generating a standard verification statement comprises: Associating each upgrade statement with a verification execution statement and a verification condition statement, the verification execution statement is a database operation statement, and the verification condition statement judges the upgrade result according to the output of the database; The verification execution statements associated with the same group of upgrade statements are divided into one group, and each group of verification execution statements is associated with a standard verification execution statement. parameter placeholders; Associating each verification execution statement with a mapper indicating the mapping relationship between the parameter placeholder and the standard verification execution statement to form a verification statement comparison table; The verification condition statements associated with the same group of upgrade statements are divided into one group, and standard condition statements are generated for each group of verification condition statements, and the standard condition statements include attribute extraction words, attribute condition words and condition parameter placeholders; For each standard verification execution statement, associate and record the mapper of the mapping relationship between the condition parameter placeholder and the verification condition statement to form a condition statement comparison table; According to the verification statement comparison table and the condition statement comparison table, a standard verification execution statement and a standard condition statement corresponding to the upgrade statement are obtained, and the standard verification execution statement and the standard condition statement constitute a standard verification statement. 4. A verifiable database upgrade method independent of database technology according to claim 3, characterized in that said method further comprises: Upload the upgrade statement comparison table, verification statement comparison table and condition statement comparison table to the network storage device; The method for the target device to parse the standard upgrade statement into an upgrade statement that matches the type of the local database is as follows: Query the upgrade statement comparison table to obtain the upgrade statement that matches the database type of the target device in the group where the standard upgrade statement is located; Map the parameters in the standard upgrade statement to the upgrade statement according to the mapper, and complete the analysis; The method of parsing the standard verification statement into a verification statement that matches the type of the local database is: Query the verification statement comparison table to obtain the verification execution statement and verification condition statement that meet the target number in the group where the standard verification execution statement is located; The parameters in the standard verification execution statement are mapped to the verification execution statement according to the mapper, and the parameters in the standard conditional statement are mapped to the verification conditional statement according to the mapper to complete the parsing. 5. A verifiable database upgrade method independent of database technology according to any one of claims 1 to 4, characterized in that, Methods for target devices to execute upgrade statements include: Determine the execution object of the upgrade statement, if the execution object is a database, execute the upgrade statement directly; If the execution object is a table of the database, create a copy of the table, the copy of the table maintains the structure of the table, and copies the data of several tables; Replace the execution object of the execution statement with a copy of the table, and execute it on the copy of the table; Use the verification statement to verify the upgrade result of the copy of the table. If the upgrade is successful, execute the next step. If the upgrade fails, delete the copy of the table and end the database upgrade; Delete the copy of the table, restore the execution object of the execution statement and execute it; Use the verify statement to verify the result of the upgrade. 6. A verifiable database upgrade method independent of database technology according to any one of claims 1 to 4, characterized in that, Methods for associating a validation execution statement with each upgrade statement include: Manually create a collection of verification execution statements for each database type; The database instance created for each database type is recorded as an auxiliary instance, and several instance tables are generated on the auxiliary instance; Read the upgrade statements in the upgrade statement comparison table in turn, manually fill in the parameters in the semantic replacement statement, so that the parameters point to the auxiliary instance and/or the example table; Map the parameters in the semantic replacement statement to the upgrade statement to form an executable upgrade statement, and execute the executable upgrade statement on the auxiliary instance; Try to fill in the parameters in the semantic replacement statement into the verification execution statement in the verification execution statement set, and execute the verification execution statement on the auxiliary instance in turn; Screen out the verification execution statements that are incorrectly executed, and use the verification execution statements that are successfully executed on the auxiliary instance as suggestions to correlate the verification execution statements for manual selection. 7. A verifiable database upgrade method independent of database technology according to claim 6, characterized in that the method further comprises: For the verification execution statement that can be successfully executed, the output content of the verification execution statement is obtained; Change the parameters in the executable upgrade statement in turn, and execute the executable upgrade statement again; After any parameter is changed, a verification execution statement with different content is output as a suggested associated verification execution statement for manual selection.

Images