CN114153461A - Script processing method and device, electronic equipment and storage medium - Google Patents

Script processing method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN114153461A
CN114153461A CN202111511884.3A CN202111511884A CN114153461A CN 114153461 A CN114153461 A CN 114153461A CN 202111511884 A CN202111511884 A CN 202111511884A CN 114153461 A CN114153461 A CN 114153461A
Authority
CN
China
Prior art keywords
script
verified
execution
execution script
verification
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.)
Pending
Application number
CN202111511884.3A
Other languages
Chinese (zh)
Inventor
杨成
江旻
杨杨
吴磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
WeBank Co Ltd
Original Assignee
WeBank Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by WeBank Co Ltd filed Critical WeBank Co Ltd
Priority to CN202111511884.3A priority Critical patent/CN114153461A/en
Publication of CN114153461A publication Critical patent/CN114153461A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/40Transformation of program code
    • G06F8/41Compilation
    • G06F8/42Syntactic analysis
    • G06F8/427Parsing

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the application provides a script processing method, a script processing device, electronic equipment and a storage medium, wherein the method comprises the following steps: for any execution script to be verified, after analyzing the execution script to be verified, determining the category of the execution script to be verified; generating a verification script of the execution script to be verified in a corresponding target generation mode based on the category of the execution script to be verified; and the verification script is used for verifying the corresponding execution script to be verified. According to the method, the verification script meeting the verification requirements of the execution scripts to be verified is generated, and even if the execution scripts need to be executed repeatedly, whether the execution scripts meet expectations or not can be accurately determined through the corresponding verification scripts based on the execution result of each time; in addition, the checking is carried out through the checking script, so that the influence of stock data and structure on the execution script is avoided; therefore, the embodiment can accurately and flexibly determine whether each execution script to be verified meets the expectation.

Description

Script processing method and device, electronic equipment and storage medium
Technical Field
The embodiment of the application relates to the field of financial technology (Fintech), in particular to a script processing method and device, electronic equipment and a storage medium.
Background
With the development of computer technology, more and more technologies are applied in the financial field, and the traditional financial industry is gradually changing to financial technology, but due to the requirements of the financial industry on safety and real-time performance, higher requirements are also put forward on the technologies. In the financial field, after an execution script is written, it is necessary to determine whether the execution script meets expectations.
In the related art, after execution of an execution script, it is determined whether the execution script meets expectations based on whether the execution was successful. However, in practical applications, many execution scripts are multiplexed, that is, some execution scripts are repeatedly executed, and therefore, it is difficult to accurately and flexibly determine whether the execution scripts meet expectations.
In summary, a script processing method is needed to accurately and flexibly determine whether an execution script meets expectations.
Disclosure of Invention
The embodiment of the application provides a script processing method and device, electronic equipment and a storage medium, which are used for accurately and flexibly determining whether an execution script meets expectations.
In a first aspect, an embodiment of the present application provides a script processing method, where the script processing method includes:
for any execution script to be verified, after analyzing the execution script to be verified, determining the category of the execution script to be verified;
generating a verification script of the execution script to be verified in a corresponding target generation mode based on the category of the execution script to be verified; the verification script is used for verifying the corresponding execution script to be verified;
if the execution script to be verified is the data change script, and the type of the data change script comprises a modification statement, an associated insertion statement and a deletion statement; based on the category of the execution script to be verified, generating a verification script of the execution script to be verified in a corresponding target generation mode, wherein the verification script comprises the following steps:
if the type of the execution script to be verified is a modification statement, determining a first field which accords with a corresponding filtering condition in the analyzed execution script to be verified, and generating a verification script corresponding to field information of the first field;
if the type of the execution script to be verified is the associated insert statement, after all second fields are determined, whether the second fields are successfully matched with the fields in the analyzed execution script to be verified, and a verification script corresponding to the field information of the fields successfully matched with the second fields is generated; and the second field is a second field which is in the category of the deleted statement and accords with the corresponding filtering condition in the execution script to be verified.
According to the scheme, after the execution scripts to be verified are analyzed, the types of the execution scripts to be verified are determined; based on the category of each execution script to be verified, generating a verification script meeting the verification requirement of the execution script to be verified in a corresponding target generation mode, and accurately determining whether the execution script meets the expectation or not based on the execution result of each time through the corresponding verification script even if the execution script needs to be executed repeatedly; in addition, the checking is carried out through the checking script, so that the influence of stock data and structure on the execution script is avoided; therefore, the embodiment can accurately and flexibly determine whether each execution script to be verified meets expectations; aiming at a data change script with changed data, determining whether the type of an execution script to be verified is a modification statement, a deletion statement or an associated insertion statement, if the execution script is the modification statement, only determining which first fields meet corresponding filtering conditions, and only generating a verification script corresponding to each first field; if the result is the associated inserted statement, after all the second fields are determined, the fields which are matched with the second fields in the execution script to be verified and are of the associated inserted statement are further determined, and only the verification scripts corresponding to the fields are generated, so that whether various data change scripts meet expectations or not is accurately and exhaustively determined.
In some optional embodiments, determining whether there is a second field successfully matched with each field in the parsed execution script to be verified includes:
and aiming at any field in the analyzed execution script to be verified, determining whether a second field is the same as the attribute value of the field, and if so, determining that the second field is successfully matched with the field.
In some optional embodiments, if the execution script to be verified is a table structure change script, and the category of the table structure change script includes a table building statement and a table change statement; based on the category of the execution script to be verified, generating a verification script of the execution script to be verified in a corresponding target generation mode, wherein the verification script comprises the following steps:
if the type of the execution script to be verified is a table building statement, generating a verification script corresponding to each item of target information in the analyzed execution script to be verified; the target information comprises table information, field information and index information;
and if the type of the execution script to be verified is a table change statement, generating a corresponding verification script based on the analyzed table change sub-type of the execution script to be verified.
According to the scheme, aiming at the table structure changing script with the changed structure, the type of the executing script to be verified is determined to be a table building statement or a table changing statement, if the executing script is the table building statement, the verifying script corresponding to each item of table information, field information and index information is required to be generated, whether the table to be created exists or not is determined through the verifying script, whether the field related information in the table is consistent with the expectation or not, and whether the index related information in the table is consistent with the expectation or not are determined, so that whether the executing script is in accordance with the expectation or not is accurately determined; if the sentence is the table-changing sentence, which information is changed can be determined based on the table-changing subcategory, and whether the execution script accords with the expectation or not is accurately and efficiently determined by generating the verification script corresponding to the information of the changed item.
In some optional embodiments, the table of variations subcategory includes field variations and index variations; generating a corresponding verification script based on the analyzed variable table subclass of the execution script to be verified, wherein the generation comprises the following steps:
if the sub-category of the variable table of the execution script to be verified is field change after analysis, generating a verification script corresponding to each field information in the execution script to be verified after analysis;
and if the list change sub-category of the execution script to be verified is index change after analysis, generating a verification script corresponding to each index information in the execution script to be verified after analysis.
According to the scheme, whether the table change sub-category of the execution script to be verified is field change or index change is determined, and only the verification script corresponding to the information of the change item is generated, so that whether the execution script to be verified meets expectations or not is accurately and efficiently determined.
In some optional embodiments, if the execution script to be verified is a data change script, and the category of the data change script includes a modification statement and an independent insertion statement; based on the category of the execution script to be verified, generating a verification script of the execution script to be verified in a corresponding target generation mode, wherein the verification script comprises the following steps:
if the type of the execution script to be verified is a modification statement, determining a first field which accords with a corresponding filtering condition in the analyzed execution script to be verified, and generating a verification script corresponding to field information of the first field;
and if the type of the execution script to be verified is an independent insert statement, generating a verification script corresponding to each field information in the analyzed execution script to be verified.
According to the scheme, aiming at the data change script with changed data, the type of the execution script to be verified is determined to be a modified statement or an independent insertion statement, if the execution script is the modified statement, only the first fields meeting the filtering condition need to be determined, and only the verification script corresponding to each first field needs to be generated; if the statement is independently inserted, the check script corresponding to each item of field information needs to be determined, so that whether various data change scripts meet expectations or not is accurately and exhaustively determined.
In some alternative embodiments, the filtering condition includes some or all of an equal condition, an inclusive condition, and a fuzzy condition.
In some optional embodiments, the method further comprises:
sending information containing all generated verification scripts to a preset person in a preset notification mode; and/or
And sending the execution script to be verified which cannot be correctly analyzed to preset personnel in a preset notification mode.
According to the scheme, the information containing all generated verification scripts is sent to the preset personnel, so that the preset personnel execute the received verification scripts and verify the to-be-verified execution scripts in the verification environment; the execution scripts to be verified, which cannot be analyzed correctly, are sent to the preset personnel, so that the preset personnel can modify the execution scripts to be verified.
In a second aspect, an embodiment of the present application further provides a script processing apparatus, including:
the script type determining module is used for determining the type of any execution script to be verified after the execution script to be verified is analyzed;
the verification script generating module is used for generating a verification script of the execution script to be verified in a corresponding target generating mode based on the category of the execution script to be verified; and the verification script is used for verifying the corresponding execution script to be verified.
In a third aspect, an embodiment of the present application provides an electronic device, including at least one processor and at least one memory, where the memory stores a computer program, and when the program is executed by the processor, the processor is caused to execute the script processing method according to any one of the above first aspects.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program executable by an electronic device, and when the program runs on the electronic device, the program causes the electronic device to execute the script processing method according to any one of the above first aspects.
In addition, for technical effects brought by any one implementation manner in the second to fourth aspects, reference may be made to technical effects brought by different implementation manners in the first aspect, and details are not described here.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a first script processing method provided in an embodiment of the present application;
fig. 2 is a schematic flowchart of a second script processing method according to an embodiment of the present application;
fig. 3 is a flowchart illustrating a third script processing method according to an embodiment of the present application;
fig. 4 is a schematic flowchart of a fourth script processing method according to an embodiment of the present application;
fig. 5 is a schematic flowchart of a fifth script processing method according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a script processing apparatus according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the accompanying drawings, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the embodiment of the present application, the term "and/or" describes an association relationship of associated objects, and means that there may be three relationships, for example, a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
The terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present application, "a plurality" means two or more unless otherwise specified.
The term "execution script," is a Structured Query Language (SQL) that implements execution operations;
the term "verification script" is SQL that implements the verification operation.
In the description of the present application, it is to be noted that, unless otherwise explicitly stated or limited, the term "connected" is to be understood broadly, and may for example be directly connected, indirectly connected through an intermediate medium, or be a communication between two devices. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art as appropriate.
After the execution script is written, it needs to be determined whether the execution script meets expectations. In the related art, after execution of an execution script, it is determined whether the execution script meets expectations based on whether the execution was successful. For example, if the execution of the script 1 is successful, the execution of the script 1 is considered to be in accordance with the expectation, but in practical applications, the execution of the script 1 may need to be repeated, and the execution of the script 1 may be missed, so that the successful execution of the script 1 cannot indicate that the execution of the script 1 is in accordance with the expectation. Therefore, it is difficult to accurately and flexibly determine whether the execution script meets the expectation.
In view of this, an embodiment of the present application provides a script processing method, an apparatus, an electronic device, and a storage medium, where the method includes: for any execution script to be verified, after analyzing the execution script to be verified, determining the category of the execution script to be verified; generating a verification script of the execution script to be verified in a corresponding target generation mode based on the category of the execution script to be verified; and the verification script is used for verifying the corresponding execution script to be verified.
According to the scheme, after the execution scripts to be verified are analyzed, the types of the execution scripts to be verified are determined; based on the category of each execution script to be verified, generating a verification script meeting the verification requirement of the execution script to be verified in a corresponding target generation mode, and accurately determining whether the execution script meets the expectation or not based on the execution result of each time through the corresponding verification script even if the execution script needs to be executed repeatedly; in addition, the checking is carried out through the checking script, so that the influence of stock data and structure on the execution script is avoided; therefore, the embodiment can accurately and flexibly determine whether each execution script to be verified meets the expectation.
The following describes the technical solutions of the present application and how to solve the above technical problems in detail with reference to the accompanying drawings and specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments.
The embodiment of the present application provides a first script processing method, as shown in fig. 1, including the following steps:
step S101: and for any execution script to be verified, after analyzing the execution script to be verified, determining the category of the execution script to be verified.
The to-be-verified execution script may have a plurality of implementation manners, and in some embodiments, the to-be-verified execution script is a table structure change script, such as a Data Definition Language (DDL); in some embodiments, the execution script to be verified is a Data change script, such as a Data Management Language (DML).
For example, after the to-be-verified execution script is analyzed, the implementation class of each to-be-verified script is determined, and the category of the to-be-verified execution script can be determined based on the implementation class.
The embodiment does not limit the specific parsing manner, for example, the to-be-verified execution script is parsed by an SQLStatementParser.
Step S102: and generating a verification script of the execution script to be verified in a corresponding target generation mode based on the category of the execution script to be verified.
And the verification script is used for verifying the corresponding execution script to be verified.
In implementation, the data structures of different types of execution scripts to be verified are different, so that the ways of generating the verification scripts are also different, and after the type of the execution script to be verified is determined, the verification script needs to be generated by adopting the target generation way corresponding to the type, so that after the verification script is executed, whether the corresponding execution script to be verified meets expectations or not is accurately verified.
According to the scheme, after the execution scripts to be verified are analyzed, the types of the execution scripts to be verified are determined; based on the category of each execution script to be verified, generating a verification script meeting the verification requirement of the execution script to be verified in a corresponding target generation mode, and accurately determining whether the execution script meets the expectation or not based on the execution result of each time through the corresponding verification script even if the execution script needs to be executed repeatedly; in addition, the checking is carried out through the checking script, so that the influence of stock data and structure on the execution script is avoided; therefore, the embodiment can accurately and flexibly determine whether each execution script to be verified meets the expectation.
As described above, the to-be-verified execution script may have multiple implementation manners, and for the to-be-verified execution script being a table structure change script, the category of the table structure change script includes a table building statement and a table changing statement, an embodiment of the present application provides a second script processing method, as shown in fig. 2, including the following steps:
step S201: and for any execution script to be verified, after analyzing the execution script to be verified, determining the category of the execution script to be verified.
The specific implementation manner of step S201 may refer to the above embodiments, and is not described herein again.
Step S202: if the type of the execution script to be verified is a table building statement, generating a verification script corresponding to each item of target information in the analyzed execution script to be verified; wherein the target information includes table information, field information, and index information.
When the SQLStatementParser is used for analyzing the to-be-checked execution script, the implementation class of the table building statement is MySqlCreateTableStableStatement.
The table building statement represents that a new table file needs to be created, and the execution script to be verified (denoted as the execution script 1) is as follows:
CREATE TABLE IF NOT EXISTS`TABLE_TEMP`(
SIMPLE 1', varchar (32) cold utf8_ bin NOT NULL common ' column 1',
"INDEX 1' varchar (20) COLLATE utf8_ bin NOT NULL COMMENT ' column 2, INDEX field '
KEY`IDX1`(`INDEX1`)
KEY`IDXGROUP`(`SIMPLE1`,`INDEX1`)
) ENGINE ═ InnogB DEFAULT CHARSE ═ utf8 COLLATE ═ utf8_ bin COMMENT ═ order master list'
The above example is only one implementation manner of the to-be-verified execution script whose category is the table building statement, and this embodiment is not specifically limited to this.
In implementation, aiming at a table building statement, a verification script corresponding to each item mark information in an analyzed execution script to be verified is generated, the verification script comprises a verification script corresponding to table information (such as a table identifier), and the verification script verifies whether the table exists after the execution of the execution script; each item of field information (such as field identification, field type, field length and the like) corresponds to a verification script, and the verification script verifies whether the field type, the field length and the like of each field are consistent with expectations after the execution of the execution script; the checking script checks whether the index fields, the index sequence and the like of each single index are consistent with expectations after the execution of the execution script; and the checking script checks whether the index fields, the index sequence and the like of each combined index are consistent with expectations after the execution script is executed.
In this embodiment, a script generator, a split character string, and the like may be used to generate a verification script, and taking the example that the script generator generates a verification script corresponding to each item of target information in the execution script 1, the table verification script generator generates a verification script corresponding to the table information:
SELECT IF(COUNT(1)=1,'YES','700973')FROM information_schema.tables WHERE TABLE_SCHEMA=(SELECT DATABASE())and table_name='TABLE_TEMP';
generating a verification script corresponding to the field information through a field verification script generator:
SELECT IF(COUNT(1)=1,'YES','990005')FROM information_schema.columns WHERE TABLE_SCHEMA=(SELECT DATABASE())and table_name='TABLE_TEMP'AND column_name='SIMPLE1'AND COLUMN_TYPE='varchar(32)'UNION ALL
SELECT IF(COUNT(1)=1,'YES',549802)FROM information_schema.columns WHERE TABLE_SCHEMA=(SELECT DATABASE())and table_name='TABLE_TEMP'AND column_name='INDEX1'AND COLUMN_TYPE='varchar(20)';
generating a check script corresponding to the index information of the single index through an index check script generator:
SELECT IF(COUNT(1)=1,'YES','755409')FROM information_schema.statistics WHERE TABLE_SCHEMA=(SELECT DATABASE())and table_name='TABLE_TEMP'AND index_name='INDEX1'AND COLUMN_NAME='INDEX1'AND SEQ_IN_INDEX='1';
generating a check script corresponding to the index information of the combined index through an index check script generator:
SELECT IF(COUNT(1)=1,'YES','716281')FROM information_schema.statistics WHERE TABLE_SCHEMA=(SELECT DATABASE())and table_name='TABLE_TEMP'AND index_name='IDXGROUP'AND COLUMN_NAME='SIMPLE1'AND SEQ_IN_INDEX='1'UNION ALL
SELECT IF(COUNT(1)=1,'YES','57223')FROM information_schema.statistics WHERE TABLE_SCHEMA=(SELECT DATABASE())and table_name='TABLE_TEMP'AND index_name='IDXGROUP'AND COLUMN_NAME='INDEX1'AND SEQ_IN_INDEX='2'。
the check scripts described above are merely exemplary, and the present application is not limited thereto.
Step S203: and if the type of the execution script to be verified is a table change statement, generating a corresponding verification script based on the analyzed table change sub-type of the execution script to be verified.
When the SQLStatementParser is used for analyzing the to-be-checked execution script, the implementation class of the table building statement is SQLAlterTableStatement. When the implementation class is SQLAlterTableStatement, an implementation subclass is also correspondingly arranged, and the sub-class of the variable table of the execution script to be verified after analysis can be determined based on the implementation subclass.
In some optional embodiments, the table of variations subcategory includes field variations and index variations; correspondingly, based on the table variation subclass of the execution script to be verified after the analysis, the corresponding verification script is generated, which can be realized by but not limited to the following modes:
if the sub-category of the variable table of the execution script to be verified is field change after analysis, generating a verification script corresponding to each field information in the execution script to be verified after analysis;
and if the list change sub-category of the execution script to be verified is index change after analysis, generating a verification script corresponding to each index information in the execution script to be verified after analysis.
Illustratively, the variant table subcategory is a field variant, the implementation subcategories are SQLAlterTableAddColumn (add field) or mysqlaltertablemodifycumn (modify field); the variant-table subclass is index change, and the implementation subclasses are sqlaltertableaddlndex (add index), SQLAlterTableDropIndex (delete index). If the implementation subclass is SQLAlterTableDropIndex, COUNT (1) is 0 in the generated check script.
As described above, in this embodiment, the script generator may be used to generate the verification script, so that the field verification script generator may generate the verification script corresponding to the field information: and generating a check script corresponding to the index information through an index check script generator, which is not described herein again.
In this embodiment, by determining whether the table change sub-category of the execution script to be verified is a field change or an index change, only the verification script corresponding to the information of the change item is generated, so as to accurately and efficiently determine whether the execution script to be verified meets expectations.
According to the scheme, aiming at the table structure changing script with the changed structure, the type of the executing script to be verified is determined to be a table building statement or a table changing statement, if the executing script is the table building statement, the verifying script corresponding to each item of table information, field information and index information is required to be generated, whether the table to be created exists or not is determined through the verifying script, whether the field related information in the table is consistent with the expectation or not, and whether the index related information in the table is consistent with the expectation or not are determined, so that whether the executing script is in accordance with the expectation or not is accurately determined; if the sentence is the table-changing sentence, which information is changed can be determined based on the table-changing subcategory, and whether the execution script accords with the expectation or not is accurately and efficiently determined by generating the verification script corresponding to the information of the changed item.
For an execution script to be verified as a data change script, an embodiment of the present application provides a third script processing method, where a category of the data change script in this embodiment includes a modification statement and an independent insertion statement, as shown in fig. 3, including the following steps:
step S301: and for any execution script to be verified, after analyzing the execution script to be verified, determining the category of the execution script to be verified.
The specific implementation manner of step S301 may refer to the above embodiments, and is not described herein again.
Step S302: if the type of the execution script to be verified is a modification statement, determining a first field which accords with a corresponding filtering condition in the analyzed execution script to be verified, and generating a verification script corresponding to field information of the first field.
When the SQLStatementParser is used for analyzing the to-be-checked execution script, the implementation class of the modification statement is MySqlUpdateStation.
For example, it is determined whether each field in the analyzed execution script to be verified corresponds to a function calculation, and if so, after the objective function value is calculated, the field attribute value of the field is replaced with the objective function value, for example: the calculation of the now () function can be converted into the time longer than the generation of the script on the same day, so that whether the data is updated or not can be effectively checked; the set @ varname function calculation can take a value corresponding to the varname to be placed in the generated check script so as to accurately match data;
determining characters of which the field attribute values in the analyzed execution script to be verified accord with corresponding filtering conditions (namely, where conditions) as first fields;
the specific generation manner of the verification script corresponding to the field information of the first field may refer to the above embodiments, and is not described herein again.
In addition, some execution scripts to be checked are also provided with limit conditions (limit), and the limit of the limit needs to be considered for the execution scripts to be checked.
A specific example is described below, and the execution script to be verified after the parsing is:
Update table_tmp set a=1,LAST_MODIFIED_DATETIME=now()where c=2and d=3limit 2; ①
Update table_tmp set a=4,LAST_MODIFIED_DATETIME=now()where c=5and d=6; ②
taking a case of firstly reading a table name table _ tmp from a script, then reading a where condition c is 2 and d is 3, then reading a set attribute a is 1, converting a now () function corresponding to LAST _ MODIFIED _ date into a date larger than today, taking out a limit 2, and finally generating a corresponding check script through a field check script generator, wherein the check script is as follows:
SELECT IF(COUNT(1)=2,'YES','492192')from table_tmp where a=1 and c=2and d=3 and
LAST_MODIFIED_DATETIME>=’2021-10-10’UNION ALL
SELECT IF(COUNT(1)>=1,'YES','153876')from table_tmp where a=4 and c=5 and d=6 and
LAST_MODIFIED_DATETIME>=’2021-10-10’。
the above example is only to more clearly illustrate how to generate the verification script of the to-be-verified execution script of which the category is the modified statement, but the specific implementation of the to-be-verified execution script and the verification script thereof in the present application is not limited.
In this embodiment, a specific implementation manner of the above-mentioned where condition is not limited, for example, the where condition may be equal to "in", and include "in" or "like" as a fuzzy condition.
Step S303: and if the type of the execution script to be verified is an independent insert statement, generating a verification script corresponding to each field information in the analyzed execution script to be verified.
In the implementation, different processing modes of the insertion statement are preset, and if the independent processing insertion statement mode is selected and the implementation class of the execution script to be verified represents the insertion statement, the type of the execution script to be verified is determined to be the independent insertion statement.
When the SQLStatementParser is used for analyzing the to-be-checked execution script, the implementation class of the inserted statement is MySqlInsertState.
For the to-be-verified execution script whose category is the independent insertion statement, a verification script corresponding to each item of field information needs to be generated, and a specific implementation manner may refer to the above embodiments, which is not described herein again.
In the scheme, aiming at the data change script with changed data, by determining whether the type of the execution script to be verified is a modified statement or an independent insertion statement, if the execution script to be verified is the modified statement, only the first fields meeting the filtering condition need to be determined, and only the verification script corresponding to each first field needs to be generated; if the statement is independently inserted, the check script corresponding to each item of field information needs to be determined, so that whether various data change scripts meet expectations or not is accurately and exhaustively determined.
For an execution script to be verified as a data change script, an embodiment of the present application provides a fourth script processing method, where the category of the data change script in this embodiment includes a modification statement, an associated insertion statement, and a deletion statement, as shown in fig. 4, including the following steps:
step S401: and for any execution script to be verified, after analyzing the execution script to be verified, determining the category of the execution script to be verified.
Step S402: if the type of the execution script to be verified is a modification statement, determining a first field which accords with a corresponding filtering condition in the analyzed execution script to be verified, and generating a verification script corresponding to field information of the first field.
The specific implementation manner of steps S401 to S402 can refer to the above embodiments, and is not described herein again.
Step S403: if the type of the execution script to be verified is the associated insert statement, after all second fields are determined, whether the second fields are successfully matched with the fields in the analyzed execution script to be verified, and a verification script corresponding to the field information of the fields successfully matched with the second fields is generated.
And the second field is a second field which is in the category of the deleted statement and accords with the corresponding filtering condition in the execution script to be verified.
When the SQLStatementParser is used for analyzing the to-be-checked execution script, the implementation class of the deleted statement is MySqlDeleteStation.
As described above, different processing modes of the insertion statement may be preset in the implementation, and if the association processing insertion statement mode is selected and the implementation class of the execution script to be verified represents the insertion statement, the type of the execution script to be verified is determined to be the association insertion statement. The execution script to be verified is associated with the execution script to be verified, the category of which is the deletion statement.
For example, the characters whose field attribute values in the to-be-verified execution script of which the category is the delete statement meet the corresponding filter condition are determined as second fields, and after all the second fields are determined, each field in the to-be-verified execution script of which the category is the associated insert statement can be matched with the second field.
In some optional embodiments, determining whether there is a second field successfully matched with each field in the parsed execution script to be verified may be implemented by, but not limited to, the following manners:
and aiming at any field in the analyzed execution script to be verified, determining whether a second field is the same as the attribute value of the field, and if so, determining that the second field is successfully matched with the field.
The following description takes the field a in the analyzed execution script to be verified as an example:
if the identifier of the field A is the same as the identifier of the table of the second field 1, determining whether the attribute value of the field A is the same as the attribute value of each attribute of the second field 1, and if the attribute value of the field A is completely the same as the attribute value of each attribute of the second field 1, successfully matching the field A with the second field 1;
as long as the attribute value of the field A is not the same as that of at least one attribute in the second field 1, the field A fails to match the second field 1; thereafter, field a is matched to the next second field.
In some optional embodiments, generating a check script corresponding to field information of a field successfully matched with the second field may be implemented by, but not limited to:
for the associated field, generating a corresponding verification script based on the field information association of the associated field; and the associated fields are a plurality of fields which are successfully matched with the same second field in the execution script to be verified after the analysis.
Correspondingly, the number of fields successfully matched with each second field is determined in the field matching process.
According to the scheme, aiming at the data change script with changed data, the types of the execution script to be verified are determined to be a modification statement, a deletion statement or a related insertion statement, if the execution script is the modification statement, only the first fields meeting the corresponding filtering conditions need to be determined, and only the verification script corresponding to each first field needs to be generated; if the result is the associated inserted statement, after all the second fields are determined, the fields which are matched with the second fields in the execution script to be verified and are of the associated inserted statement are further determined, and only the verification scripts corresponding to the fields are generated, so that whether various data change scripts meet expectations or not is accurately and exhaustively determined.
In some optional implementations, with respect to the above embodiment of fig. 4, it may be determined that the category that does not match the second field is a field in the to-be-verified execution script of the associated inserted statement, and the category that does not match the second field is a second field in the to-be-verified execution script of the associated inserted statement; the execution scripts corresponding to the fields are sent to the presetting personnel, so that the presetting personnel can determine whether the deleted fields are mistaken and the inserted fields are mistaken based on the execution scripts, and therefore gray level verification is achieved.
An embodiment of the present application provides a fifth script processing method, as shown in fig. 5, including the following steps:
step S501: and for any execution script to be verified, after analyzing the execution script to be verified, determining the category of the execution script to be verified.
Step S502: and generating a verification script of the execution script to be verified in a corresponding target generation mode based on the category of the execution script to be verified.
The specific implementation manner of steps S501 to S502 can refer to the above embodiments, and is not described herein again.
Step S503: sending information containing all generated verification scripts to a preset person in a preset notification mode; and/or sending the execution script to be verified which cannot be correctly analyzed to preset personnel in a preset notification mode.
In this embodiment, after the verification scripts of various execution scripts to be verified are generated in steps S501 to S502, information including all generated verification scripts is sent to a preset person, so that the preset person executes the received verification scripts, and the execution scripts are verified in a verification environment.
In the implementation, in order to more accurately position the execution script which fails to pass the verification, the verification script can be encoded (by using different encoding results to identify each verification script) by a preset encoding mode (for example, by using a 6-bit random encoding mode with a low repetition rate), and the corresponding relationship between the verification script and the execution script is determined, so that the execution script which fails to pass the verification can be quickly and accurately positioned.
In addition, some execution scripts which cannot be analyzed or are analyzed incorrectly may exist in the execution scripts to be verified, the verification scripts corresponding to the execution scripts cannot be generated in the implementation, and based on this, the execution scripts are sent to a preset person, so that the preset person can modify the execution scripts.
In some optional embodiments, the reason why the execution scripts cannot be correctly analyzed may also be determined, and the reason is sent to the preset personnel together with the corresponding execution scripts.
The embodiment does not specifically limit the manner of determining the reason that the script cannot be correctly analyzed, for example, the reason that the script to be checked cannot be analyzed is determined as a syntax error; and determining the reason of the execution script to be verified, which can be analyzed but cannot identify the category, as the category error.
Taking the embodiment of fig. 2 as an example, if the to-be-verified execution script still cannot be analyzed through format compatibility conversion, it indicates that the corresponding statement cannot be executed or the execution result is abnormal, and it is determined that the statement is a syntax error; and if the category of the execution script to be verified is not identified to be a table building statement or a table changing statement, determining that the category is wrong.
Taking the embodiment of fig. 4 as an example, if the to-be-verified execution script still cannot be analyzed through format compatibility conversion, it indicates that the corresponding statement cannot be executed or the execution result is abnormal, and it is determined that the statement is a syntax error; if the type of the execution script to be verified is not identified to be a modification statement, an associated insertion statement or a deletion statement, the type is determined to be an error.
The above-mentioned manner for determining the reason that cannot be correctly analyzed is only an exemplary illustration, and the present application is not limited thereto.
According to the scheme, the information containing all generated verification scripts is sent to the preset personnel, so that the preset personnel execute the received verification scripts and verify the to-be-verified execution scripts in the verification environment; the execution scripts to be verified, which cannot be analyzed correctly, are sent to the preset personnel, so that the preset personnel can modify the execution scripts to be verified.
Based on the same inventive concept, an embodiment of the present application provides a script processing apparatus, and referring to fig. 6, a script processing apparatus 600 includes:
the script type determining module 601 is configured to, for any one to-be-verified execution script, determine a type of the to-be-verified execution script after analyzing the to-be-verified execution script;
a verification script generating module 602, configured to generate a verification script of the execution script to be verified in a corresponding target generating manner based on the type of the execution script to be verified; the verification script is used for verifying the corresponding execution script to be verified;
if the execution script to be verified is the data change script, and the type of the data change script comprises a modification statement, an associated insertion statement and a deletion statement; the verification script generating module 602 is specifically configured to:
if the type of the execution script to be verified is a modification statement, determining a first field which accords with a corresponding filtering condition in the analyzed execution script to be verified, and generating a verification script corresponding to field information of the first field;
if the type of the execution script to be verified is the associated insert statement, after all second fields are determined, whether the second fields are successfully matched with the fields in the analyzed execution script to be verified, and a verification script corresponding to the field information of the fields successfully matched with the second fields is generated; and the second field is a second field which is in the category of the deleted statement and accords with the corresponding filtering condition in the execution script to be verified.
In some optional embodiments, the verification script generating module 602 is specifically configured to:
and aiming at any field in the analyzed execution script to be verified, determining whether a second field is the same as the attribute value of the field, and if so, determining that the second field is successfully matched with the field.
In some optional embodiments, if the execution script to be verified is a table structure change script, and the category of the table structure change script includes a table building statement and a table change statement; the verification script generating module 602 is specifically configured to:
if the type of the execution script to be verified is a table building statement, generating a verification script corresponding to each item of target information in the analyzed execution script to be verified; the target information comprises table information, field information and index information;
and if the type of the execution script to be verified is a table change statement, generating a corresponding verification script based on the analyzed table change sub-type of the execution script to be verified.
In some optional embodiments, the table of variations subcategory includes field variations and index variations; the verification script generating module 602 is specifically configured to:
if the sub-category of the variable table of the execution script to be verified is field change after analysis, generating a verification script corresponding to each field information in the execution script to be verified after analysis;
and if the list change sub-category of the execution script to be verified is index change after analysis, generating a verification script corresponding to each index information in the execution script to be verified after analysis.
In some optional embodiments, if the execution script to be verified is a data change script, and the category of the data change script includes a modification statement and an independent insertion statement; the verification script generating module 602 is specifically configured to:
if the type of the execution script to be verified is a modification statement, determining a first field which accords with a corresponding filtering condition in the analyzed execution script to be verified, and generating a verification script corresponding to field information of the first field;
and if the type of the execution script to be verified is an independent insert statement, generating a verification script corresponding to each field information in the analyzed execution script to be verified.
In some alternative embodiments, the filtering condition includes some or all of an equal condition, an inclusive condition, and a fuzzy condition.
In some optional embodiments, a notification module 603 is further included, configured to:
sending information containing all generated verification scripts to a preset person in a preset notification mode; and/or sending the execution script to be verified which cannot be correctly analyzed to preset personnel in a preset notification mode.
Since the apparatus is the apparatus in the method in the embodiment of the present application, and the principle of the apparatus for solving the problem is similar to that of the method, the implementation of the apparatus may refer to the implementation of the method, and repeated details are not repeated.
Based on the same technical concept, an electronic device 700 is further provided in the embodiments of the present application, as shown in fig. 7, and includes at least one processor 701 and a memory 702 connected to the at least one processor, and a specific connection medium between the processor 701 and the memory 702 is not limited in the embodiments of the present application, and the processor 701 and the memory 702 are connected through a bus 703 in fig. 7 as an example. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 7, but this is not intended to represent only one bus or type of bus.
The processor 701 is a control center of the electronic device, and may be connected to various parts of the electronic device through various interfaces and lines, and implement data processing by executing or executing instructions stored in the memory 702 and calling data stored in the memory 702. Optionally, the processor 701 may include one or more processing units, and the processor 701 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application program, and the like, and the modem processor mainly processes an issued instruction. It will be appreciated that the modem processor described above may not be integrated into the processor 701. In some embodiments, processor 701 and memory 702 may be implemented on the same chip, or in some embodiments, they may be implemented separately on separate chips.
The processor 701 may be a general-purpose processor, such as a Central Processing Unit (CPU), a digital signal processor, an Application Specific Integrated Circuit (ASIC), a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present Application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the disclosed methods in connection with the script processing method embodiments may be embodied directly in a hardware processor, or in a combination of hardware and software modules within a processor.
Memory 702, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 702 may include at least one type of storage medium, and may include, for example, a flash Memory, a hard disk, a multimedia card, a card-type Memory, a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Programmable Read Only Memory (PROM), a Read Only Memory (ROM), a charge Erasable Programmable Read Only Memory (EEPROM), a magnetic Memory, a magnetic disk, an optical disk, and so on. The memory 702 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 702 in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.
In the embodiment of the present application, the memory 702 stores a computer program, which, when executed by the processor 701, causes the processor 701 to perform:
for any execution script to be verified, after analyzing the execution script to be verified, determining the category of the execution script to be verified;
generating a verification script of the execution script to be verified in a corresponding target generation mode based on the category of the execution script to be verified; the verification script is used for verifying the corresponding execution script to be verified;
if the execution script to be verified is the data change script, and the type of the data change script comprises a modification statement, an associated insertion statement and a deletion statement;
the processor 701 specifically executes:
if the type of the execution script to be verified is a modification statement, determining a first field which accords with a corresponding filtering condition in the analyzed execution script to be verified, and generating a verification script corresponding to field information of the first field;
if the type of the execution script to be verified is the associated insert statement, after all second fields are determined, whether the second fields are successfully matched with the fields in the analyzed execution script to be verified, and a verification script corresponding to the field information of the fields successfully matched with the second fields is generated; and the second field is a second field which is in the category of the deleted statement and accords with the corresponding filtering condition in the execution script to be verified.
In some optional embodiments, the processor 701 specifically performs:
and aiming at any field in the analyzed execution script to be verified, determining whether a second field is the same as the attribute value of the field, and if so, determining that the second field is successfully matched with the field.
In some optional embodiments, the execution script to be verified is a table structure change script, and the category of the table structure change script includes a table building statement and a table change statement;
the processor 701 specifically executes:
if the type of the execution script to be verified is a table building statement, generating a verification script corresponding to each item of target information in the analyzed execution script to be verified; the target information comprises table information, field information and index information;
and if the type of the execution script to be verified is a table change statement, generating a corresponding verification script based on the analyzed table change sub-type of the execution script to be verified.
In some optional embodiments, the table of variations subcategory includes field variations and index variations;
the processor 701 specifically executes:
if the sub-category of the variable table of the execution script to be verified is field change after analysis, generating a verification script corresponding to each field information in the execution script to be verified after analysis;
and if the list change sub-category of the execution script to be verified is index change after analysis, generating a verification script corresponding to each index information in the execution script to be verified after analysis.
In some optional embodiments, the execution script to be verified is a data change script, and the category of the data change script includes a modification statement and an independent insertion statement;
the processor 701 specifically executes:
if the type of the execution script to be verified is a modification statement, determining a first field which accords with a corresponding filtering condition in the analyzed execution script to be verified, and generating a verification script corresponding to field information of the first field;
and if the type of the execution script to be verified is an independent insert statement, generating a verification script corresponding to each field information in the analyzed execution script to be verified.
In some alternative embodiments, the filtering condition includes some or all of an equal condition, an inclusive condition, and a fuzzy condition.
In some optional embodiments, the processor 701 further performs:
sending information containing all generated verification scripts to a preset person in a preset notification mode; and/or sending the execution script to be verified which cannot be correctly analyzed to preset personnel in a preset notification mode.
Since the electronic device is the electronic device in the method in the embodiment of the present application, and the principle of the electronic device for solving the problem is similar to that of the method, reference may be made to implementation of the method for the electronic device, and repeated details are not described again.
Based on the same technical concept, embodiments of the present application also provide a computer-readable storage medium storing a computer program executable by an electronic device, wherein when the program runs on the electronic device, the electronic device is caused to execute the steps of the script processing method.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (10)

1. A method for processing a script, the method comprising:
for any execution script to be verified, after analyzing the execution script to be verified, determining the category of the execution script to be verified;
generating a verification script of the execution script to be verified in a corresponding target generation mode based on the category of the execution script to be verified; the verification script is used for verifying the corresponding execution script to be verified;
if the execution script to be verified is the data change script, and the type of the data change script comprises a modification statement, an associated insertion statement and a deletion statement; based on the category of the execution script to be verified, generating a verification script of the execution script to be verified in a corresponding target generation mode, wherein the verification script comprises the following steps:
if the type of the execution script to be verified is a modification statement, determining a first field which accords with a corresponding filtering condition in the analyzed execution script to be verified, and generating a verification script corresponding to field information of the first field;
if the type of the execution script to be verified is the associated insert statement, after all second fields are determined, whether the second fields are successfully matched with the fields in the analyzed execution script to be verified, and a verification script corresponding to the field information of the fields successfully matched with the second fields is generated; and the second field is a second field which is in the category of the deleted statement and accords with the corresponding filtering condition in the execution script to be verified.
2. The method of claim 1, wherein determining whether a second field matches successfully with each field in the parsed execution script to be verified comprises:
and aiming at any field in the analyzed execution script to be verified, determining whether a second field is the same as the attribute value of the field, and if so, determining that the second field is successfully matched with the field.
3. The method according to claim 1, wherein if the execution script to be verified is a table structure change script, and the category of the table structure change script comprises a table building statement and a table changing statement; based on the category of the execution script to be verified, generating a verification script of the execution script to be verified in a corresponding target generation mode, wherein the verification script comprises the following steps:
if the type of the execution script to be verified is a table building statement, generating a verification script corresponding to each item of target information in the analyzed execution script to be verified; the target information comprises table information, field information and index information;
and if the type of the execution script to be verified is a table change statement, generating a corresponding verification script based on the analyzed table change sub-type of the execution script to be verified.
4. The method of claim 3, wherein the table-of-variables subcategory includes field changes and index changes; generating a corresponding verification script based on the analyzed variable table subclass of the execution script to be verified, wherein the generation comprises the following steps:
if the sub-category of the variable table of the execution script to be verified is field change after analysis, generating a verification script corresponding to each field information in the execution script to be verified after analysis;
and if the list change sub-category of the execution script to be verified is index change after analysis, generating a verification script corresponding to each index information in the execution script to be verified after analysis.
5. The method of claim 1, wherein if the execution script to be verified is a data change script, and the category of the data change script comprises a modification statement and an independent insertion statement; based on the category of the execution script to be verified, generating a verification script of the execution script to be verified in a corresponding target generation mode, wherein the verification script comprises the following steps:
if the type of the execution script to be verified is a modification statement, determining a first field which accords with a corresponding filtering condition in the analyzed execution script to be verified, and generating a verification script corresponding to field information of the first field;
and if the type of the execution script to be verified is an independent insert statement, generating a verification script corresponding to each field information in the analyzed execution script to be verified.
6. The method according to any one of claims 1 to 5, wherein the filtering condition includes a part or all of an equal condition, an inclusive condition, and a fuzzy condition.
7. The method of any of claims 1 to 5, further comprising:
sending information containing all generated verification scripts to a preset person in a preset notification mode; and/or
And sending the execution script to be verified which cannot be correctly analyzed to preset personnel in a preset notification mode.
8. A script processing apparatus, comprising:
the script type determining module is used for determining the type of any execution script to be verified after the execution script to be verified is analyzed;
the verification script generating module is used for generating a verification script of the execution script to be verified in a corresponding target generating mode based on the category of the execution script to be verified; the verification script is used for verifying the corresponding execution script to be verified;
if the execution script to be verified is the data change script, and the type of the data change script comprises a modification statement, an associated insertion statement and a deletion statement; the verification script generation module is specifically configured to:
if the type of the execution script to be verified is a modification statement, determining a first field which accords with a corresponding filtering condition in the analyzed execution script to be verified, and generating a verification script corresponding to field information of the first field;
if the type of the execution script to be verified is the associated insert statement, after all second fields are determined, whether the second fields are successfully matched with the fields in the analyzed execution script to be verified, and a verification script corresponding to the field information of the fields successfully matched with the second fields is generated; and the second field is a second field which is in the category of the deleted statement and accords with the corresponding filtering condition in the execution script to be verified.
9. An electronic device comprising at least one processor and at least one memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform the method of any of claims 1 to 7.
10. A computer-readable storage medium, characterized in that it stores a computer program executable by an electronic device, which program, when run on the electronic device, causes the electronic device to carry out the method of any one of claims 1 to 7.
CN202111511884.3A 2021-12-07 2021-12-07 Script processing method and device, electronic equipment and storage medium Pending CN114153461A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111511884.3A CN114153461A (en) 2021-12-07 2021-12-07 Script processing method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111511884.3A CN114153461A (en) 2021-12-07 2021-12-07 Script processing method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN114153461A true CN114153461A (en) 2022-03-08

Family

ID=80450549

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111511884.3A Pending CN114153461A (en) 2021-12-07 2021-12-07 Script processing method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114153461A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116401177A (en) * 2023-06-09 2023-07-07 瀚高基础软件股份有限公司 DDL correctness detection method, device and medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116401177A (en) * 2023-06-09 2023-07-07 瀚高基础软件股份有限公司 DDL correctness detection method, device and medium
CN116401177B (en) * 2023-06-09 2023-08-15 瀚高基础软件股份有限公司 DDL correctness detection method, device and medium

Similar Documents

Publication Publication Date Title
CN110795455B (en) Dependency analysis method, electronic device, computer apparatus, and readable storage medium
CN108647357B (en) Data query method and device
CN109062925A (en) Automatically generate the method, apparatus, computer equipment and storage medium of insert sentence
CN108319711A (en) Transaction consistency test method, device, storage medium and the equipment of database
CN111159016A (en) Standard detection method and device
CN114090671A (en) Data import method and device, electronic equipment and storage medium
CN113326283A (en) Method and device for calculating service index
CN114153461A (en) Script processing method and device, electronic equipment and storage medium
CN106708897B (en) Data warehouse quality guarantee method, device and system
CN100527131C (en) Interdynamic access method and tool of IMS data base
CN111444208B (en) Data updating method and related equipment
CN111984674A (en) Method and system for generating structured query language
US11182375B2 (en) Metadata validation tool
CN111522881A (en) Service data processing method, device, server and storage medium
CN111796907A (en) Data checking method and device based on checking script, electronic equipment and medium
CN111857721B (en) SQL statement verification method, data acquisition method, equipment and storage device
CN114153460A (en) Verification method, verification device, electronic equipment and storage medium
CN111639478B (en) Automatic data auditing method and system based on EXCEL document
CN112817931B (en) Incremental version file generation method and device
US8856166B2 (en) Query validator
CN111625586A (en) Method and system for importing general service data
CN115826928B (en) Program generating method, system, electronic device and computer readable storage medium
CN117472958A (en) Verification method, device, equipment and medium for SQL statement execution result
CN108304430B (en) Method for modifying database
CN114489590A (en) Automatic document generation method and system based on swagger interface

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