CN111159016A - Standard detection method and device - Google Patents

Standard detection method and device Download PDF

Info

Publication number
CN111159016A
CN111159016A CN201911292384.8A CN201911292384A CN111159016A CN 111159016 A CN111159016 A CN 111159016A CN 201911292384 A CN201911292384 A CN 201911292384A CN 111159016 A CN111159016 A CN 111159016A
Authority
CN
China
Prior art keywords
detected
database
file
database file
detection
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
CN201911292384.8A
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 CN201911292384.8A priority Critical patent/CN111159016A/en
Publication of CN111159016A publication Critical patent/CN111159016A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3604—Software analysis for verifying properties of programs
    • G06F11/3608—Software analysis for verifying properties of programs using formal methods, e.g. model checking, abstract interpretation

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The embodiment of the invention discloses a specification detection method and device, which are used for acquiring a database file to be detected, determining the database type of the operation of the database file to be detected according to a script statement of the database file to be detected, and performing specification detection on the database file to be detected by using various specifications corresponding to the database type to obtain a specification detection result corresponding to the database file to be detected. In the embodiment of the invention, the standard detection of the database file to be detected is automatically completed by using each standard, so that manual intervention is not needed, the efficiency and the accuracy of the standard detection are improved, and the standard detection method can be suitable for the database files of various database types by setting the standard corresponding to each database type, so that the flexibility is higher, and the pertinence of the standard detection result is stronger.

Description

Standard detection method and device
Technical Field
The invention relates to the technical field of financial technology (Fintech), in particular to a standard detection method and device.
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 (Fintech), but because of the requirements of security and real-time performance of the financial industry, the financial industry also puts higher demands on the technologies.
Before an application is on-line, various detections, such as a script specification detection, a script quality detection, a script accuracy detection, and the like, are generally required for a file to be issued of the application. The script specification detection is used for determining the non-specification sentences in the script file and is the basis of script quality detection and script accuracy detection.
At the present stage, manual detection is a commonly used script specification detection method, and after a file to be issued is obtained, a detector can perform manual review on the script file by referring to preset specification check items, so as to judge script statements in the script file, which do not meet the specification check items. However, the manual detection method takes a long time, which results in low efficiency of the standard detection, and the manual detection may cause the standard error check and the omission check due to the human error, which results in low accuracy of the standard detection.
In summary, there is a need for a specification detection method to solve the technical problems of low efficiency and poor accuracy of specification detection caused by performing script specification detection in a manual detection manner in the prior art.
Disclosure of Invention
The embodiment of the invention provides a specification detection method and device, which are used for solving the technical problems of low specification detection efficiency and poor accuracy caused by adopting a manual detection mode to carry out script specification detection in the prior art.
In a first aspect, a specification detection method provided in an embodiment of the present invention includes:
the method comprises the steps of obtaining a database file to be detected, determining the database type of the operation of the database file to be detected according to script statements of the database file to be detected, and carrying out standard detection on the database file to be detected by using various standards corresponding to the database type to obtain a standard detection result corresponding to the database file to be detected.
In the embodiment of the invention, the standard detection of the database file to be detected is automatically completed by using each standard, so that manual intervention is not needed, the efficiency and the accuracy of the standard detection are improved, and the standard detection method can be suitable for the database files of various database types by setting the standard corresponding to each database type, so that the flexibility is higher, and the pertinence of the standard detection result is stronger.
In a possible implementation manner, the acquiring a database file to be tested includes: receiving identifiers of a file to be published and a database file to be tested, and acquiring the database file to be tested from the file to be published according to the identifier of the database file to be tested.
In the implementation mode, the standard detection method can only carry out standard detection on the database files to be detected in the files to be issued, and does not need to carry out standard detection on the full amount of files to be issued, so that the detection data volume can be reduced, the time for standard detection is saved, and the efficiency for standard detection is improved; in addition, the implementation mode supports the user to define the database file to be detected, so that the flexibility of standard detection can be improved.
In a possible implementation manner, the performing specification detection on the database file to be detected by using each specification corresponding to the database type includes: aiming at any script statement in the database file to be detected, dividing the script statement according to a preset division rule corresponding to the database type to obtain each word in the script statement; determining a syntax tree corresponding to the script statement according to the statement type of the script statement, and performing semantic analysis on each word by using the syntax tree to determine key words in each word and an operation object corresponding to each key word; and aiming at any key word, determining a specification matched with an operation object corresponding to the key word from various specifications corresponding to the database type, performing specification detection on the key word by using the matched specification, and determining whether the key word violates the specification.
In the implementation mode, the lexical analysis and the syntactic analysis are used for determining the key words and the operation objects corresponding to the key words from the script sentences, so that the matching relation between the key words and the specifications can be accurately determined based on the operation objects, the matched specifications are used for carrying out the specification detection on the key words, and the specifications are not required to be used for carrying out the test on the key words one by one, so that the meaningless operation can be avoided, and the efficiency of the specification detection is improved.
In a possible implementation manner, the obtaining a standard detection result corresponding to the database file to be detected includes: and generating a specification detection result file corresponding to the database file to be detected according to each key word which does not meet the specification in the script sentence of the database file to be detected, the position of each key word, the specification violated by each key word and the risk level of the violated specification.
In the implementation mode, the rule detection result file is generated by using the information of each key word violating the rule, so that various violation information can be comprehensively contained in the rule detection result file, the information is more comprehensive, and the readability of a user is better.
In a possible implementation manner, after the standard detection result corresponding to the database file to be detected is obtained, whether the standard detection result file corresponding to the database file to be detected meets a set rule is further determined, if yes, the file to be published corresponding to the database file to be detected is sent to a test node for online, and if not, the standard detection result corresponding to the database file to be detected is sent to a development node for correction; wherein the setting rule comprises: the highest risk level violating the specification is less than or equal to the highest allowable risk level, the number of key words violating the specification is less than or equal to a first set number, and the number of key words violating the specification of the set level is less than or equal to a second set number.
In the implementation manner, whether the standard detection result file corresponding to the database file to be detected is matched with the set rule or not can be used for identifying the standard degree of the database file to be detected, and the subsequent execution flow (such as online or correction) of the database file to be detected is determined based on the standard degree of the database file to be detected, so that a user does not need to determine the subsequent execution flow, the working pressure of the user is reduced, and the satisfaction degree of the user is improved.
In a possible implementation manner, before the database file to be detected is subjected to the specification detection by using the specifications corresponding to the database types, syntax detection is further performed on the database file to be detected by using a syntax detection model corresponding to the database types, so that it is determined that no script statement with a syntax error exists in the database file to be detected.
In the implementation mode, the grammar detection is carried out on the database file to be detected firstly, and then the standard detection is carried out on the database file to be detected when the fact that no grammar error exists in the database file to be detected is determined, so that the standard detection of the database file to be detected with obvious errors can be avoided, useless operation is avoided being executed, and the efficiency of the standard detection is improved.
In a second aspect, an embodiment of the present invention provides a specification detecting apparatus, where the apparatus includes:
the acquisition module is used for acquiring a database file to be detected;
the determining module is used for determining the database type of the database file operation to be detected according to the script statement of the database file to be detected;
and the detection module is used for carrying out standard detection on the database file to be detected by using each standard corresponding to the database type to obtain a standard detection result corresponding to the database file to be detected.
In a possible implementation manner, the obtaining module is specifically configured to: receiving identifiers of a file to be published and a database file to be tested, and acquiring the database file to be tested from the file to be published according to the identifier of the database file to be tested.
In a possible implementation manner, the detection module is specifically configured to: aiming at any script statement in the database file to be detected, dividing the script statement according to a preset division rule corresponding to the database type to obtain each word in the script statement; determining a syntax tree corresponding to the script statement according to the statement type of the script statement, and performing semantic analysis on each word by using the syntax tree to determine key words in each word and an operation object corresponding to each key word; and aiming at any key word, determining a specification matched with an operation object corresponding to the key word from various specifications corresponding to the database type, performing specification detection on the key word by using the matched specification, and determining whether the key word violates the specification.
In a possible implementation manner, the detection module is specifically configured to: and generating a specification detection result file corresponding to the database file to be detected according to each key word which does not meet the specification in the script sentence of the database file to be detected, the position of each key word, the specification violated by each key word and the risk level of the violated specification.
In a possible implementation manner, after the detection module obtains the standard detection result corresponding to the database file to be detected, the detection module is further configured to: determining whether a standard detection result file corresponding to the database file to be detected meets a set rule, if so, sending a file to be published corresponding to the database file to be detected to a test node for online, and if not, sending the standard detection result corresponding to the database file to be detected to a development node for correction; wherein the setting rule comprises: the highest risk level violating the specification is less than or equal to the highest allowable risk level, the number of key words violating the specification is less than or equal to a first set number, and the number of key words violating the specification of the set level is less than or equal to a second set number.
In a possible implementation manner, before the detection module performs the specification detection on the database file to be detected by using each specification corresponding to the database type, the detection module is further configured to: and carrying out grammar detection on the database file to be detected by using a grammar detection model corresponding to the database type, and determining that no script statement with grammar errors exists in the database file to be detected.
In a third aspect, an embodiment of the present invention provides a computing 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 specification detection method according to any of the first aspect.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, which stores a computer program executable by a computing device, and when the program runs on the computing device, the program causes the computing device to execute the specification detection method according to any of the first aspects.
These and other implementations of the present application will be more readily understood from the following description of the embodiments.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a schematic diagram of a possible system architecture according to an embodiment of the present invention;
fig. 2 is a schematic flowchart corresponding to a specification detection method according to an embodiment of the present invention;
fig. 3 is a schematic interface display diagram of a service interface according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating a syntax checking method according to an embodiment of the present invention;
FIG. 5 is a diagram illustrating a syntax tree corresponding to a table building statement according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating a syntax parsing result according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a specification detecting apparatus according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a computing device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a schematic diagram of a possible system architecture provided by an embodiment of the present invention, where the system may be any business system in the field of financial technology, such as an order system, a payment system, a shopping cart system, and the like. As shown in fig. 1, the system architecture may be provided with a development node 110, a test node 120, and a service node 130, where the development node 110 may be connected to the test node 120 and the service node 130 respectively, for example, through a wired connection, or through a wireless connection, and is not limited in particular.
In a specific implementation, after a developer develops an application to be online on the development node 110, a file to be published may be sent to the test node 120 for testing. During testing, the test node 120 may perform script specification detection on the file to be published first, and if the script specification detection fails, the test node 120 may transmit a test failure message back to the development node 110, so that a developer on the development node 110 side corrects the file to be published; correspondingly, if the script specification detection passes, the test node 120 may execute the file to be published to complete script quality detection and/or script accuracy detection, and if all the detections pass, the test node 120 may transmit a message of successful test back to the development node 110, so that a developer on the development node 110 side sends the file to be published to the service node 130 to complete application online.
Each node described above may be a server or a process in the server, and is not particularly limited.
Based on the system architecture illustrated in fig. 1, fig. 2 is a schematic flowchart corresponding to a specification detection method provided in an embodiment of the present invention, where the method is applied to a test node 120, and the method includes:
step 201, obtaining a database file to be tested.
In an example, when the development node 110 has an online application requirement, a test request may be sent to the test node 120, where the test request carries an identifier of the file to be published and an identifier of the database file to be tested, and thus, the test node 120 may obtain the database file to be tested from the file to be published according to the identifier of the database file to be tested. The file to be published is a script file of an application to be online, the file to be published can comprise a multi-level file list deployed in a directory form, and each level of file list can contain a plurality of parallel files; accordingly, the database file to be tested may be defined by the development node 110, for example, the database file to be tested may be a database file updated by a new version application with respect to an old version application, or may be any database file in the file to be released, without limitation.
It should be noted that the identifier of the database file to be tested may be a name of the database file to be tested, or may be a directory path of the database file to be tested in the file to be issued, which is not limited specifically.
In the embodiment of the present invention, there may be many ways for the development node 110 to send the test request to the test node 120, as an example, the test node 120 is a World Wide Web (Web) server, the development node 110 is any client with an interface display function, such as a mobile phone, a notebook computer, an Ipad, and the like, and a Web browser is deployed on the development node 110. In a specific implementation, when a developer has an online application requirement, the web browser of the development node 110 may acquire a service interface provided by the test node 120, and then operate the service interface to trigger the development node 110 to send a test request to the test node 120, for example, a mouse may click a setting icon on the service interface to trigger the development node 110 to send the test request to the test node 120, or a preset key (such as a single key or a combined key) on a keyboard may be pressed in a setting area of the service interface to trigger the development node 110 to send the test request to the test node 120, or a preset voice or a preset text may be input in a setting input box of the service interface to trigger the development node 110 to send the test request to the test node 120, or a preset brain wave signal may be acquired to trigger the development node 110 to send the test request to the test node 120, and the like, without limitation.
For example, fig. 3 is an interface schematic diagram of a service interface according to an embodiment of the present invention, as shown in fig. 3, a to-be-published file input box and a configuration button of a to-be-published database file are arranged in the middle of the service interface, where the to-be-published file input box is used for a developer to input full data of the to-be-published file, or is used for the developer to input a storage location of the to-be-published file, where the development node 110 opens a data read-write right item of the storage location to the test node 120 in advance; correspondingly, the configuration button of the database file to be tested is used for a developer to obtain a configuration interface of the database file to be tested.
As shown in fig. 3, in the configuration interface of the database file to be tested, the database file to be tested is configured in a directory manner, and a developer may click the "add directory configuration option" button to add a new directory configuration, and may input a directory path of the database file to be tested in the specified directory input box. And, the developer may configure one database file to be tested in the configuration interface of the database file to be tested, or may configure a plurality of database files to be tested, and after the configuration is completed, the developer may click the "execute directory configuration option" button, so that the development node 110 generates the test request according to the file to be issued input by the developer on the service interface and the database file to be tested configured on the configuration interface of the database file to be tested.
It should be noted that the above is only an exemplary and simple description, the interface layout form is only for convenience of description and does not constitute a limitation to the solution, and in a specific implementation, the interface layout form may be set by a person skilled in the art according to experience, and is not specifically limited.
In the above example, the specification detection method can perform specification detection only on the database file to be detected in the file to be published, and does not need to perform specification detection on the full amount of files to be published, so that the detection data amount can be reduced, the specification detection time can be saved, and the specification detection efficiency can be improved; moreover, the example supports the user to self-define the database file to be detected, so that the flexibility of standard detection can be improved. For example, if the file to be released is a script file of a new version application, the database file to be detected may be a database file updated by the new version application with respect to an old version application, so that the method may only detect the updated database file without detecting an un-updated database file.
Step 202, determining the database type of the database file operation to be detected according to the script statement of the database file to be detected.
In a specific implementation, the test node 120 may determine the database type of the database file operation to be tested in multiple ways, for example, the database type of the database file operation to be tested may be determined based on whether a script statement of the database file to be tested includes a standard script statement of each database type, the database type of the database file operation to be tested may also be determined based on a suffix name of the database file to be tested, the database type of the database file operation to be tested may also be determined based on field information of the database file to be tested at a set position, the set position is predetermined by the development node 110 and the test node 120, and a developer may add a database type field of the database file operation to be tested at the set position during development, which is not particularly limited.
And 203, performing standard detection on the database file to be detected by using each standard corresponding to the database type to obtain a standard detection result corresponding to the database file to be detected.
In a possible implementation manner, before performing the standard detection on the script statement of the database file to be detected, the test node 120 may further perform syntax detection on the database file to be detected, and an implementation flow of the syntax detection method may be as shown in fig. 4, where the method includes:
step 401, according to the database type of the database file operation to be detected, determining a grammar detection model corresponding to the database type.
In the embodiment of the present invention, the test node 120 integrates syntax detection models corresponding to each database type in advance, and each database type may include each database in a relational database, a non-relational database, and/or a key-value-pair database, for example, may include a TDSQL database, a MySQL database, and/or a Sybase database in the relational database, and may also include a CouchDB database, a Cassandra database, and/or a MongoDB database in the non-relational database, and may also include a Dynamo database, a LevelDB database, and/or the like in the key-value-pair database, and may also include a HIVE database, and the like.
And 402, using a grammar detection model corresponding to the database type to carry out grammar detection on the script statement in the database file to be detected.
For example, if it is determined that the database type of the operation of the database file to be tested is the HIVE database, the test node 120 may input the database file to be tested into the syntax detection model corresponding to the HIVE database, so as to call the syntax detection model corresponding to the HIVE database to simulate and execute each script statement in the database file to be tested, so as to determine the script statement with the syntax error in each script statement; if the database type of the file operation of the database to be tested is determined to be the TDSQL database, the test node 120 may input the file of the database to be tested into the syntax detection model corresponding to the TDSQL database, so as to invoke the syntax detection model corresponding to the TDSQL database to simulate and execute each script statement in the file of the database to be tested, so as to determine the script statement with a syntax error in each script statement.
In the embodiment of the present invention, the syntax error refers to an error that may affect the running of the database file to be tested, and the syntax error may be set by a person skilled in the art according to experience, for example, the syntax error may be set to any one or more of missing operation objects, containing illegal characters, incomplete fields, and character type mismatch, which is not limited specifically.
Step 403, determining whether a script statement with a syntax error exists in the database file to be tested, if not, executing step 404, and if so, executing step 405.
And 404, performing specification detection on the script statement of the database file to be detected by using each specification corresponding to the database type.
And 405, generating a grammar detection result file corresponding to the database file to be detected, and sending the grammar detection result file to a development node.
In specific implementation, if at least one script statement in the database file to be tested has a syntax error, it is determined that the database file to be tested does not conform to the syntax rule, so the test node 120 can generate a syntax detection result file according to the script statement with the syntax error and the syntax error of the script statement, and send the syntax detection result file to the development node 110, and after receiving the syntax detection result file, the development node 110 can display the syntax detection result file on a service interface, so that developers can correct the database file to be tested. Correspondingly, if all script statements in the database file to be tested have no syntax error, it is determined that the data file to be tested conforms to the syntax rule, and thus, the test node 120 can perform standard detection on the database file to be tested.
In the implementation mode, the grammar detection is carried out on the database file to be detected firstly, and then the standard detection is carried out on the database file to be detected when no grammar error exists in the database file to be detected, so that the standard detection on the database file to be detected with obvious errors can be avoided, useless operation is avoided being executed, and the efficiency of the standard detection is improved.
In the embodiment of the present invention, each specification corresponding to each database type may be obtained by summarizing a plurality of database files for operating the database type, or may be set by a user according to actual needs, and the specifications corresponding to the various database types may be uniformly stored in a preset specification library, so that the test node 120 is managed. Moreover, the preset specification library can also support a user to operate each specification in the preset specification library according to service needs, such as adding a new specification in the preset specification library, deleting an existing specification in the preset specification library, modifying an existing specification in the preset specification library, inquiring which existing specifications exist in the preset specification library, and the like.
The preset specification library may be stored in a table form, a database form, or a queue form, and is not limited specifically.
Taking the preset specification library stored in a table form as an example, table 1 is a schematic table of the preset specification library provided in the embodiment of the present invention:
table 1: schematic of preset specification library
Figure BDA0002319540350000111
As shown in table 1, each specification corresponding to each database type is stored in the preset specification library, and for any database type, each specification corresponding to the database type may be stored in the preset specification library in a row form, and an identifier of each specification, an applicable database type, a belonging specification type, a specification check item, an applicable object, and a risk level may be stored in the preset specification library. For example, the second row of Table 1 stores the specification R1Each item of information of (1), specification R1The method is applicable to TDSQL database types, and belongs to a grammar specification type, the content of a specification check item is 'whether a check list has a main key', the applicable operation object is a list, and the risk level is a high-level risk.
It should be noted that table 1 is only an exemplary and simple illustration, and the listed preset specification library is only for convenience of describing the scheme and does not constitute a limitation to the scheme, and in a specific implementation, the preset specification library may be set by a person skilled in the art according to experience, for example, only a database type, a specification check item, and an applicable operation object for the specification may also be stored, or only a database type, a specification check item, an applicable object for the specification, and a risk level for the specification may be stored, and is not particularly limited.
In a possible implementation manner, the following manner may be adopted to perform the standard detection on any script statement in the database file to be detected:
step a, dividing the script sentence according to a preset division rule corresponding to the database type of the database file to be detected to obtain each word in the script sentence.
In an example, before performing specification detection on any script statement, the type of the script statement may be further determined, where the type of the script statement may be a Data Manipulation Language (DML) script type or a Data Definition Language (DDL) script type, where the script statement of the DDL script type is used to create or modify a related object in a database, such as a database, a Data table, a Data field, a Data index, and the like, and the script statement of the DDL script type needs to perform specification detection; accordingly, the script statement of the DML script type is used for operating on data in the database, such as adding new data in the database, modifying existing data, deleting existing data, viewing existing data, and the like, and the script statement of the DML script type does not need to perform specification detection.
In a specific implementation, if the type of the script statement is a DML script type, the script statement may not be subjected to the standard detection, and if the type of the script statement is a DDL script type, the script statement may be subjected to the standard detection.
And b, determining a syntax tree corresponding to the script statement according to the statement type of the script statement.
In the embodiment of the present invention, syntax trees corresponding to script statements of various statement types, such as syntax trees corresponding to table building statements, syntax trees corresponding to library building statements, syntax trees corresponding to newly added index statements, and the like, may be encapsulated in the test node 120.
Fig. 5 is a schematic structural diagram of a syntax tree corresponding to a table building statement according to an embodiment of the present invention, where as shown in fig. 5, the syntax tree may include 1 st to nth syntax layers arranged according to a hierarchical structure, where the nth syntax layer is located at a topmost layer of the syntax tree, and a root syntax node is arranged in the nth syntax layer and is used to identify a statement type of a script statement corresponding to the syntax tree; each grammar node in the ith grammar layer is provided with corresponding word semantics and word categories, and the grammar nodes in the ith grammar layer can be connected with a plurality of grammar nodes in the (i-1) th grammar layer.
In one example, the category of the word may include a key word and a non-key word, the key word may be identified by a "Litrerals" character, if the category of the word is the key word, the "Litrerals" character may be included in the grammar node corresponding to the word, and if the category of the word is the non-key word, the "Litrerals" character may not be included in the grammar node corresponding to the word. For example, as shown in fig. 5, for the 1 st grammar node in the 3 rd level grammar layer (i.e., the third level grammar layer from bottom to top in fig. 5), the word semantic of the word corresponding to the grammar node is "sentence type", and since the grammar node does not include the "characters of" Litrerals ", the category of the word is a non-key word; correspondingly, for the 3 rd grammar node in the 3 rd grammar layer, the word semantic of the word corresponding to the grammar node is "table name", and the category of the word is a key word because the grammar node comprises the "characters of" Litrerals ".
In specific implementation, the test node 120 may match the script statement with each set statement type to obtain a matching value between the script statement and each set statement type, and then use the set statement type with the highest matching value in each set statement type as the statement type of the script statement; further, the corresponding relation between the statement type and the syntax tree is inquired, the syntax tree corresponding to the statement type of the script statement is determined, and the syntax tree is used as the syntax tree corresponding to the script statement.
And c, performing semantic analysis on each word in the script sentence by using the grammar tree to determine key words in each word and operation objects corresponding to the key words.
And d, aiming at any key word, determining a specification matched with an operation object corresponding to the key word from each rule corresponding to the database type, and performing specification detection on the key word by using the matched specification to determine whether the key word meets the specification.
According to the steps a to d, the whole standard detection of the script sentence comprises a lexical analysis stage and a syntactic analysis stage, wherein the lexical analysis stage is used for dividing the continuous script sentence into a plurality of words according to a preset division rule, the syntactic analysis is used for performing semantic analysis on each word to determine the category of each word, the category of each word comprises a key word and a non-key word, the key word comprises any one or more of a table name, a column length and a main key, and the non-key word comprises any one or more of a symbol, a sentence type and a description.
For the convenience of understanding, the following specific example is used to perform a specific implementation process of rule detection.
In specific implementation, when the database type of the file operation of the database to be tested is TDSQL database, if a script statement in the file of the database to be tested is:
create table 'cut _ info' (cut _ id varchar (10) 'customer encodes' Primary Key);
the test node 120 may scan the script statements in a left-to-right (or right-to-left) order, and during the scanning, if it is determined that a certain character string conforms to a preset division rule corresponding to the TDSQL database, the certain character string may be used as a word obtained by division. If a certain preset dividing rule is "symbol as a word", the preset dividing rule may be divided into "'", "(", ")," ",") in sequence from the script file.
In one example, a built-in lexical rule base is provided in the test node 120, and the built-in lexical rule base is used for storing each preset division rule and word attributes obtained by dividing each preset division rule. The word attribute may be any one of a key word, a symbol word and a content word, the key word is used to identify the word as a functional word, such as creating a table, creating a column, etc., the symbol word is used to identify the word as a nonsense word, and the content word is used to identify the word as an object corresponding to the key word, such as creating a table name of the table, creating a column name of the column, etc.
Based on this example, table 2 is a schematic table of a division result of a script statement provided in the embodiment of the present invention:
table 2: an indication of each word obtained by dividing a script statement
Word Properties Word meaning Position of
Create Key word Create 6
Table Key word Table 12
‘ Symbolic word Quote 14
cust_info Content word IDENTIFIER 23
‘ Symbolic word Quote 24
( Symbolic word Leftparenthesis 26
Cust_id Content word IDENTIFIER 33
varchar Key word varchar 41
( Symbolic word LeftParenthesis 42
10 Content word IDENTIFIER 44
) Symbolic word RightParenthesis 45
‘ Symbolic word Quote 47
Client coding Content word IDENTIFIER 51
‘ Symbolic word Quote 52
primary Key word primary 60
key Key word key 64
) Symbolic word RightParenthesis 65
； Symbolic word semicolon 66
As shown in table 2, in addition to each word and the attribute of each word in the script sentence, the division result may also include the starting position of each word in the script sentence and the word sense of each word, such as the word "(" the starting position in the script sentence is the 26 th character, and the word sense of "is the left bracket) in the 7 th line.
In the embodiment of the present invention, after each word in the script sentence is obtained by dividing, since the script sentence is matched with the table building sentence, the syntax tree corresponding to the script sentence is the syntax tree corresponding to the table building sentence, as shown in fig. 5. Thus, each word in the script sentence can be matched with a grammar node in a grammar tree corresponding to the table building sentence, the grammar node corresponding to the word in the grammar tree is determined, then the corresponding grammar node is used for carrying out semantic analysis on the word, and the semantic meaning of the word and the category of the word are determined.
Based on each word illustrated in table 2 and the syntax tree illustrated in fig. 5, fig. 6 is a schematic structural diagram of a syntax parsing result provided in the embodiment of the present invention, as illustrated in fig. 5, a word "cus _ info", a word "cut _ id", a word "vacur", a word "10", a word "client code", and a word "Primary Key" in a script sentence "Create table 'cut _ info' (cut _ idvarchar (10) 'client code' Primary Key)" are Key words, and other words are non-Key words.
Correspondingly, the test node 120 may further determine an operation object corresponding to each keyword according to the word sense of each keyword in the syntax parsing result to create a keyword object table, where the format of the keyword object table may be as shown in table 3:
table 3: schematic of a key word object table
Statement type Operation object Key word Attributes of key words
Table building statement Table name cus_info Lower case of table name
Table building statement Column name Cust_id Capital letters of column names
Table building statement Column(s) of Client coding Content providing method and apparatus
Table building statement Column(s) of vachar Type (B)
Table building statement Column(s) of 10 Length of
Table building statement Watch main key Primary Key Main key
As shown in table 3, the attribute of the key word may also be included in the key word object table, and the attribute of the key word may be defined based on the format of the key word and the operation object of the key word, for example, each character in the key word "cus _ info" is a lower case, and the operation object thereof is a table, and the semantic is a table name, so the attribute of the key word "cus _ info" may be a table name lower case.
Further, for each keyword in the keyword object table, the test node 120 may determine, according to the operation object applicable to each specification in the preset specification library, a specification matched with the operation object corresponding to the keyword, and then call the matched specification to perform specification detection on the keyword, so as to determine whether the keyword meets the specification.
For example, based on the specification R in the pre-set specification library illustrated in Table 11And norm R2And a key word object table as shown in Table 3, the operation object corresponding to the key word "cus _ info" is a table name, the operation object corresponding to the key word "Cust _ id" is a column name, and the specification R2The corresponding operation objects are table names and column names, so the key word "cus _ info" and the key word "cut _ id" are in accordance with the specification R2Matching; norm R2The table name and column name are required to be lowercase, and the keyword "cus _ info" conforms to the specification R2And the key word "Cust _ id" does not conform to the specification R2. Accordingly, the Key word "Primary Key" corresponds to an operation object that is a table Primary Key, and the Specification R1The applicable operation object is a table Primary Key, therefore, the Key word "Primary Key" is in accordance with the specification R1Matching; norm R1The requirement that the table must have a Primary Key and the Key word "Primary Key" is the Primary Key of table cus _ info, so the Key word "Primary Key" conforms to Specification R1。
In the implementation mode, the lexical analysis and the syntactic analysis are used for determining the key words and the operation objects corresponding to the key words from the script sentences, so that the matching relation between the key words and the specifications can be accurately determined based on the operation objects, the matched specifications are used for carrying out the specification detection on the key words, and the specifications are not required to be used for carrying out the test on the key words one by one, so that the meaningless operation can be avoided, and the efficiency of the specification detection is improved.
In one example, after determining each key word that does not meet the specification in the database file to be tested, a specification detection result corresponding to each key word that does not meet the specification may be generated according to any one or more of each key word that does not meet the specification, a position of each key word that does not meet the specification in the database file to be tested, a specification violated by each key word that does not meet the specification, and a risk level that violates the specification, and then a specification detection result file corresponding to the database file to be tested may be assembled according to the specification detection results corresponding to each key word that does not meet the specification. The positions of the key words in the database file to be tested can be set by the lines of the script sentences in the database file to be tested where the key words are located and the lines of the key words in the script sentences, and the standard marks can be standard check items or standard numbers without limitation.
As an example, the test node 120 may further send the specification test result file corresponding to the database file to be tested to the development node 110, so that the development node 110 displays the specification test result file corresponding to the database file to be tested to a developer through a service interface, so that the developer determines whether to go online to the file to be published.
As another example, as shown in fig. 1, the test node 120 may be further connected to the service node 130, and if it is determined that the specification test result file corresponding to the database file to be tested satisfies the set rule, the test node 120 may directly send the file to be published to the service node 130 for online, and if it is determined that the specification test result file corresponding to the database file to be tested does not satisfy the set rule, the test node 120 may send the specification test result file corresponding to the database file to be tested to the development node 110, so that the development node 110 displays the specification test result file corresponding to the database file to be tested to the developer through the service interface, so that the developer corrects the database file to be tested.
Wherein the setting rules can be set by those skilled in the art based on experience, three possible setting rules are described below:
setting a rule I: the setting rule is set such that the number of key words violating the specification is less than or equal to a first set number.
For example, when the first set number is 3, if the number of the key words violating the specification in the specification test result file corresponding to the database file to be tested is 2, the database file to be tested satisfies the set rule, and if the number of the key words violating the specification in the specification test result file corresponding to the database file to be tested is 5, the database file to be tested does not satisfy the set rule.
Setting a rule II: the rule is set such that the highest risk level for violation of the specification is less than or equal to the highest allowable risk level.
For example, when the highest allowable risk level is a medium level, if the highest risk level of the rule violated by each key word that does not meet the specification in the specification detection result file corresponding to the database file to be detected is a low level, the database file to be detected satisfies the set rule, and if the highest risk level of the rule violated by each key word that does not meet the specification in the specification detection result file corresponding to the database file to be detected is a high level, the database file to be detected does not satisfy the set rule.
Setting a rule three: the setting rule is set such that the number of key words violating the specification of the set level is less than or equal to a second set number.
For example, when the second set number is the high-level number 1 and/or the medium-level number 3, if the risk level number of the key word violating the specification in the specification detection result file corresponding to the database file to be detected is the high-level number 1 and the low-level number 4, the database file to be detected satisfies the set rule, and if the risk level number of the key word violating the specification in the specification detection result file corresponding to the database file to be detected is the high-level number 1 and the medium-level number 5, the database file to be detected does not satisfy the set rule.
It should be noted that the preset rules are only exemplary and simple descriptions, and do not constitute a limitation on the solution, and in a specific implementation, the preset rules may be set by a person skilled in the art according to experience, for example, the preset rules may also be set in a combination form of the above setting rules, and are not limited.
In the above example, whether the specification detection result file corresponding to the database file to be detected is matched with the setting rule or not can be used for identifying the specification degree of the database file to be detected, and the subsequent execution process (such as online or correction) of the database file to be detected is determined based on the specification degree of the database file to be detected, so that a user does not need to determine the subsequent execution process, the working pressure of the user is reduced, and the satisfaction degree of the user is improved.
In the above embodiment of the present invention, a database file to be detected is obtained, a database type of operation of the database file to be detected is determined according to a script statement of the database file to be detected, and each specification corresponding to the database type is used to perform specification detection on the database file to be detected, so as to obtain a specification detection result corresponding to the database file to be detected. In the embodiment of the invention, the standard detection of the database file to be detected is automatically completed by using each standard, so that manual intervention is not needed, the efficiency and the accuracy of the standard detection are improved, and the standard detection method can be suitable for the database files of various database types by setting the standard corresponding to each database type, so that the flexibility is higher, and the pertinence of the standard detection result is stronger.
In view of the above method flow, an embodiment of the present invention further provides a specification detection apparatus, and specific contents of the apparatus may be implemented with reference to the above method.
Fig. 7 is a schematic structural diagram of a specification detecting apparatus according to an embodiment of the present invention, including:
an obtaining module 701, configured to obtain a database file to be tested;
a determining module 702, configured to determine, according to the script statement of the database file to be tested, a database type of the database file to be tested;
the detection module 703 is configured to perform standard detection on the database file to be detected by using each standard corresponding to the database type, so as to obtain a standard detection result corresponding to the database file to be detected.
Optionally, the obtaining module 701 is specifically configured to:
receiving the identifications of the file to be issued and the database file to be detected;
and acquiring the database file to be detected from the file to be issued according to the identifier of the database file to be detected.
Optionally, the detection module 703 is specifically configured to:
aiming at any script statement in the database file to be detected, dividing the script statement according to a preset division rule corresponding to the database type to obtain each word in the script statement; determining a syntax tree corresponding to the script statement according to the statement type of the script statement, and performing semantic analysis on each word by using the syntax tree to determine key words in each word and an operation object corresponding to each key word; and aiming at any key word, determining a specification matched with an operation object corresponding to the key word from various specifications corresponding to the database type, performing specification detection on the key word by using the matched specification, and determining whether the key word violates the specification.
Optionally, the detection module 703 is specifically configured to:
and generating a specification detection result file corresponding to the database file to be detected according to each key word which does not meet the specification in the script sentence of the database file to be detected, the position of each key word, the specification violated by each key word and the risk level of the violated specification.
Optionally, after the detection module 703 obtains the standard detection result corresponding to the database file to be detected, the detection module is further configured to:
determining whether a standard detection result file corresponding to the database file to be detected meets a set rule, if so, sending a file to be published corresponding to the database file to be detected to a test node for online, and if not, sending the standard detection result corresponding to the database file to be detected to a development node for correction;
wherein the setting rule comprises: the highest risk level violating the specification is less than or equal to the highest allowable risk level, the number of key words violating the specification is less than or equal to a first set number, and the number of key words violating the specification of the set level is less than or equal to a second set number.
Optionally, before the detection module 703 uses each specification corresponding to the database type to perform specification detection on the database file to be detected, the detection module is further configured to:
and carrying out grammar detection on the database file to be detected by using a grammar detection model corresponding to the database type, and determining that no script statement with grammar errors exists in the database file to be detected.
From the above, it can be seen that: in the above embodiment of the present invention, a database file to be detected is obtained, a database type of operation of the database file to be detected is determined according to a script statement of the database file to be detected, and each specification corresponding to the database type is used to perform specification detection on the database file to be detected, so as to obtain a specification detection result corresponding to the database file to be detected. In the embodiment of the invention, the standard detection of the database file to be detected is automatically completed by using each standard, so that manual intervention is not needed, the efficiency and the accuracy of the standard detection are improved, and the standard detection method can be suitable for the database files of various database types by setting the standard corresponding to each database type, so that the flexibility is higher, and the pertinence of the standard detection result is stronger.
Based on the same inventive concept, an embodiment of the present invention further provides a computing device, as shown in fig. 8, including at least one processor 801 and a memory 802 connected to the at least one processor, where a specific connection medium between the processor 801 and the memory 802 is not limited in the embodiment of the present invention, and the processor 801 and the memory 802 are connected through a bus in fig. 8 as an example. The bus may be divided into an address bus, a data bus, a control bus, etc.
In the embodiment of the present invention, the memory 802 stores instructions executable by the at least one processor 801, and the at least one processor 801 may execute the steps included in the script specification evaluation method by executing the instructions stored in the memory 802.
The processor 801 is a control center of the computing device, and may connect various parts of the computing device by using various interfaces and lines, and implement data processing by executing or executing instructions stored in the memory 802 and calling up data stored in the memory 802. Optionally, the processor 801 may include one or more processing units, and the processor 801 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 801. In some embodiments, the processor 801 and the memory 802 may be implemented on the same chip, or in some embodiments, they may be implemented separately on separate chips.
The processor 801 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 embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments for evaluating in conjunction with the script specification can be directly implemented by a hardware processor, or can be implemented by a combination of hardware and software modules in the processor.
Memory 802, 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 802 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 charged Erasable Programmable Read Only Memory (EEPROM), a magnetic Memory, a magnetic disk, an optical disk, and so on. The memory 802 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 802 of embodiments of the present invention may also be circuitry or any other device capable of performing a storage function to store program instructions and/or data.
Based on the same inventive concept, an embodiment of the present invention further provides a computer-readable storage medium, which stores a computer program executable by a computing device, and when the program runs on the computing device, the computer program causes the computing device to execute the script specification evaluation method described in any of fig. 2 above.
It should be apparent to those skilled in the art that embodiments of the present invention may be provided as a method, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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 invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. 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 preferred embodiments of the present invention 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 such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (14)

1. A specification detection method, the method comprising:
acquiring a database file to be tested;
determining the database type of the operation of the database file to be detected according to the script statement of the database file to be detected;
and carrying out standard detection on the database file to be detected by using each standard corresponding to the database type to obtain a standard detection result corresponding to the database file to be detected.
2. The method of claim 1, wherein the obtaining the database file under test comprises:
receiving the identifications of the file to be issued and the database file to be detected;
and acquiring the database file to be detected from the file to be issued according to the identifier of the database file to be detected.
3. The method according to claim 1, wherein the performing specification detection on the database file to be detected by using the specifications corresponding to the database types comprises:
aiming at any script statement in the database file to be detected, dividing the script statement according to a preset division rule corresponding to the database type to obtain each word in the script statement; determining a syntax tree corresponding to the script statement according to the statement type of the script statement, and performing semantic analysis on each word by using the syntax tree to determine key words in each word and an operation object corresponding to each key word; and aiming at any key word, determining a specification matched with an operation object corresponding to the key word from various specifications corresponding to the database type, performing specification detection on the key word by using the matched specification, and determining whether the key word violates the specification.
4. The method according to claim 3, wherein the obtaining of the standard detection result corresponding to the database file to be detected comprises:
and generating a specification detection result file corresponding to the database file to be detected according to each key word which does not meet the specification in the script sentence of the database file to be detected, the position of each key word, the specification violated by each key word and the risk level of the violated specification.
5. The method according to claim 4, wherein after obtaining the standard detection result corresponding to the database file to be detected, the method further comprises:
determining whether a standard detection result file corresponding to the database file to be detected meets a set rule, if so, sending a file to be published corresponding to the database file to be detected to a test node for online, and if not, sending the standard detection result corresponding to the database file to be detected to a development node for correction;
wherein the setting rule comprises: the highest risk level violating the specification is less than or equal to the highest allowable risk level, the number of key words violating the specification is less than or equal to a first set number, and the number of key words violating the specification of the set level is less than or equal to a second set number.
6. The method according to any one of claims 1 to 5, wherein before performing specification test on the database file to be tested by using the specifications corresponding to the database types, the method further comprises:
and carrying out grammar detection on the database file to be detected by using a grammar detection model corresponding to the database type, and determining that no script statement with grammar errors exists in the database file to be detected.
7. A specification detection apparatus, characterized in that the apparatus comprises:
the acquisition module is used for acquiring a database file to be detected;
the determining module is used for determining the database type of the database file operation to be detected according to the script statement of the database file to be detected;
and the detection module is used for carrying out standard detection on the database file to be detected by using each standard corresponding to the database type to obtain a standard detection result corresponding to the database file to be detected.
8. The apparatus of claim 7, wherein the obtaining module is specifically configured to:
receiving the identifications of the file to be issued and the database file to be detected;
and acquiring the database file to be detected from the file to be issued according to the identifier of the database file to be detected.
9. The apparatus of claim 7, wherein the detection module is specifically configured to:
aiming at any script statement in the database file to be detected, dividing the script statement according to a preset division rule corresponding to the database type to obtain each word in the script statement; determining a syntax tree corresponding to the script statement according to the statement type of the script statement, and performing semantic analysis on each word by using the syntax tree to determine key words in each word and an operation object corresponding to each key word; and aiming at any key word, determining a specification matched with an operation object corresponding to the key word from various specifications corresponding to the database type, performing specification detection on the key word by using the matched specification, and determining whether the key word violates the specification.
10. The apparatus of claim 9, wherein the detection module is specifically configured to:
and generating a specification detection result file corresponding to the database file to be detected according to each key word which does not meet the specification in the script sentence of the database file to be detected, the position of each key word, the specification violated by each key word and the risk level of the violated specification.
11. The apparatus according to claim 10, wherein after the detection module obtains the standard detection result corresponding to the database file to be detected, the detection module is further configured to:
determining whether a standard detection result file corresponding to the database file to be detected meets a set rule, if so, sending a file to be published corresponding to the database file to be detected to a test node for online, and if not, sending the standard detection result corresponding to the database file to be detected to a development node for correction;
wherein the setting rule comprises: the highest risk level violating the specification is less than or equal to the highest allowable risk level, the number of key words violating the specification is less than or equal to a first set number, and the number of key words violating the specification of the set level is less than or equal to a second set number.
12. The apparatus according to any one of claims 7 to 11, wherein before the detecting module performs specification detection on the database file to be detected by using the specifications corresponding to the database types, the detecting module is further configured to:
and carrying out grammar detection on the database file to be detected by using a grammar detection model corresponding to the database type, and determining that no script statement with grammar errors exists in the database file to be detected.
13. A computing 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 6.
14. A computer-readable storage medium storing a computer program executable by a computing device, the program, when run on the computing device, causing the computing device to perform the method of any of claims 1 to 6.
CN201911292384.8A 2019-12-16 2019-12-16 Standard detection method and device Pending CN111159016A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911292384.8A CN111159016A (en) 2019-12-16 2019-12-16 Standard detection method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911292384.8A CN111159016A (en) 2019-12-16 2019-12-16 Standard detection method and device

Publications (1)

Publication Number Publication Date
CN111159016A true CN111159016A (en) 2020-05-15

Family

ID=70557231

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911292384.8A Pending CN111159016A (en) 2019-12-16 2019-12-16 Standard detection method and device

Country Status (1)

Country Link
CN (1) CN111159016A (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111752923A (en) * 2020-06-28 2020-10-09 中国银行股份有限公司 Script monitoring method and device
CN111881017A (en) * 2020-06-24 2020-11-03 北京极简智能科技有限公司 Method and device for automatically evaluating SQL target code segment
CN113010421A (en) * 2021-03-16 2021-06-22 北京奇艺世纪科技有限公司 Data processing method and device, electronic equipment and storage medium
CN113138974A (en) * 2021-04-23 2021-07-20 建信金融科技有限责任公司 Database compliance detection method and device
CN115186650A (en) * 2022-09-07 2022-10-14 中国中金财富证券有限公司 Data detection method and related device
CN116467178A (en) * 2023-03-21 2023-07-21 北京飞轮数据科技有限公司 Database detection method, apparatus, electronic device and computer readable medium

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111881017A (en) * 2020-06-24 2020-11-03 北京极简智能科技有限公司 Method and device for automatically evaluating SQL target code segment
CN111752923A (en) * 2020-06-28 2020-10-09 中国银行股份有限公司 Script monitoring method and device
CN113010421A (en) * 2021-03-16 2021-06-22 北京奇艺世纪科技有限公司 Data processing method and device, electronic equipment and storage medium
CN113010421B (en) * 2021-03-16 2023-09-01 北京奇艺世纪科技有限公司 Data processing method, device, electronic equipment and storage medium
CN113138974A (en) * 2021-04-23 2021-07-20 建信金融科技有限责任公司 Database compliance detection method and device
CN113138974B (en) * 2021-04-23 2023-08-22 建信金融科技有限责任公司 Method and device for detecting database compliance
CN115186650A (en) * 2022-09-07 2022-10-14 中国中金财富证券有限公司 Data detection method and related device
CN115186650B (en) * 2022-09-07 2022-12-09 中国中金财富证券有限公司 Data detection method and related device
CN116467178A (en) * 2023-03-21 2023-07-21 北京飞轮数据科技有限公司 Database detection method, apparatus, electronic device and computer readable medium
CN116467178B (en) * 2023-03-21 2024-02-20 北京飞轮数据科技有限公司 Database detection method, apparatus, electronic device and computer readable medium

Similar Documents

Publication Publication Date Title
US11755466B1 (en) Systems and methods for testing a software application
CN111159016A (en) Standard detection method and device
AU2018272840B2 (en) Automated dependency analyzer for heterogeneously programmed data processing system
US11341116B2 (en) Techniques for automated data analysis
CN106796585B (en) Conditional validation rules
US10445309B2 (en) Managing record format information
US8949166B2 (en) Creating and processing a data rule for data quality
US8904352B2 (en) Systems and methods for processing source code during debugging operations
US10810009B2 (en) Visualizations of software project and contributor activity
CN111176996A (en) Test case generation method and device, computer equipment and storage medium
US20150261507A1 (en) Validating sql queries in a report
CN115827895A (en) Vulnerability knowledge graph processing method, device, equipment and medium
US20170109697A1 (en) Document verification
CN111367530A (en) Code auditing method, terminal and server based on self-defined auditing rule
CN111309586A (en) Command testing method, device and storage medium thereof
US6853963B1 (en) Analyzing an extended finite state machine system model
CN101727451B (en) Method and device for extracting information
CN112363814A (en) Task scheduling method and device, computer equipment and storage medium
CN114116773A (en) Structured Query Language (SQL) text auditing method and device
CN112130838A (en) Transaction data processing method and device
CN109697141B (en) Method and device for visual testing
CN108255802B (en) Universal text parsing architecture and method and device for parsing text based on architecture
CN116860356A (en) Plug-in generation method, plug-in generation device, electronic equipment and computer readable storage medium
CN114185797A (en) Front-end code checking method and device, electronic equipment and readable storage medium
CN115826928A (en) Program generation method, system, electronic device, and computer-readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination