CN110659293B

CN110659293B - Data table determining method and device based on change codes

Info

Publication number: CN110659293B
Application number: CN201910906315.5A
Authority: CN
Inventors: 常旭亮
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2019-09-24
Filing date: 2019-09-24
Publication date: 2022-02-11
Anticipated expiration: 2039-09-24
Also published as: CN110659293A

Abstract

The embodiment of the specification provides a data table determining method and device based on change codes, wherein the data table determining method based on the change codes comprises the following steps: acquiring a change code submitted by an application under the condition of receiving an update request submitted by the application; determining a change database layer interface called by a change method to which the change code belongs according to a change line number corresponding to the change code in a change file; and searching a data table mapped by the changed database layer interface in the acquired mapping relation between the database layer interface and the data table analyzed according to the target code file of the application, wherein the data table is used as a changed data table corresponding to the changed code in the application.

Description

Data table determining method and device based on change codes

Technical Field

The embodiment of the specification relates to the technical field of data processing, in particular to a data table determining method based on change codes. One or more embodiments of the present specification also relate to a change code-based data table determining apparatus, a computing device, and a computer-readable storage medium.

Background

With the development of the internet, the data volume is increased rapidly, and in order not to affect the read-write efficiency of data, the storage of data is more and more diversified and has more and more hierarchy, for example, there are online data tables which can be interacted facing to services and offline data storage tables facing to storage. Sometimes, when a developer updates codes for an application, the structure of an online data table is changed, but when the developer makes such a change, the developer is not aware that the change causes data errors of an offline data table corresponding to the data, and finally causes a fault after the application is online, so that a faster or more reliable scheme needs to be provided for determining the influence of the change codes submitted by the developer on the data table.

Disclosure of Invention

In view of this, the present specification provides a data table determination method based on change codes. One or more embodiments of the present specification also relate to a data table determining apparatus based on change codes, a computing device, and a computer-readable storage medium to address technical deficiencies in the prior art.

According to a first aspect of embodiments of the present specification, there is provided a data table determination method based on change codes, including:

Acquiring a change code submitted by an application under the condition of receiving an update request submitted by the application;

determining a change database layer interface called by a change method to which the change code belongs according to a change line number corresponding to the change code in a change file;

and searching a data table mapped by the changed database layer interface in the acquired mapping relation between the database layer interface and the data table analyzed according to the target code file of the application, wherein the data table is used as a changed data table corresponding to the changed code in the application.

Optionally, the determining, according to the change line number corresponding to the change code in the change file, a change database layer interface called by the change method to which the change code belongs includes:

dividing the change codes into code types and non-code types according to change types;

acquiring a code change line number list corresponding to the code in the code change file;

determining a code change method list to which the code belongs based on the code change file where the code is located and the code change line number list;

assembling the code change line number list, the code change method list and the change information corresponding to the non-code type to generate a change structure;

And matching the change structure with a call relation structure between the application methods of the application obtained by analyzing the target code file to obtain the change database layer interface corresponding to the change code.

Optionally, the mapping relationship between the database layer interface and the data table is determined in the following manner:

analyzing the object code file to obtain a database layer interface in the object code file and an SQL identifier corresponding to the database layer interface;

traversing an abstract syntax tree generated by SQL sentences analyzed based on the SQL configuration files in the target code files to obtain SQL sentence marks and data tables corresponding to the SQL sentences;

and associating the database layer interface with the data table corresponding to the SQL statement through the SQL identification and the SQL statement identification, and establishing a mapping relation between the database layer interface and the data table.

Optionally, before the steps of analyzing the object code file to obtain a database layer interface in the object code file and executing the SQL identifier corresponding to the database layer interface, the method further includes:

Under the condition that a registration request for the application is received, completing registration in a mode of writing application information of the application into a registry;

monitoring a trigger message of an analysis task for analyzing the mapping relation through a message monitor;

based on the trigger message, pulling the target code file to a target server according to the application name in the registry.

Optionally, after the step of associating the database layer interface with the data table corresponding to the SQL statement through the SQL flag and the SQL statement flag and establishing the mapping relationship between the database layer interface and the data table is executed, the method further includes:

storing the mapping relation in a database in a form of a mapping relation table;

and searching a data table mapped by the changed database layer interface in the acquired mapping relation between the database layer interface and the data table analyzed according to the target code file of the application, and reading the mapping relation table in the database before executing a step of changing the corresponding data table in the application as the changed code.

Optionally, the change request includes: the application name, code repository address, start code version, object code version of the application;

The obtaining change code submitted for the application includes:

and acquiring a change code corresponding to the application name between the target code version and the start code version in the code warehouse pointed by the code warehouse address.

According to a second aspect of embodiments of the present specification, there is provided a change code-based data table determination apparatus including:

an obtaining module configured to obtain a change code submitted for an application in a case where an update request submitted for the application is received;

the determining module is configured to determine a change database layer interface called by a change method to which the change code belongs according to a change line number corresponding to the change code in a change file;

and the searching module is configured to search the data table mapped by the changed database layer interface in the acquired mapping relation between the database layer interface and the data table analyzed according to the target code file of the application, and the data table is used as a changed data table corresponding to the changed code in the application.

Optionally, the determining module includes:

a classification submodule configured to classify the change code into a code type and a non-code type according to a change type;

The code changing sub-module is configured to obtain a code changing line number list corresponding to the code in the code changing file;

a determining method list submodule configured to determine a code change method list to which the code belongs based on the code change file in which the code is located and the code change line number list;

the assembling submodule is configured to assemble the code change line number list, the code change method list and the change information corresponding to the non-code type to generate a change structure;

and the obtaining interface sub-module is configured to match the change structure with a call relation structure between the application methods of the applications obtained by analyzing the target code file, and obtain the change database layer interface corresponding to the change code.

Optionally, the mapping relationship between the database layer interface and the data table is determined by operating the following modules:

the reflection module is configured to analyze the object code file to obtain a database layer interface in the object code file and an SQL identifier corresponding to the database layer interface;

The analysis module is configured to traverse an abstract syntax tree generated by an SQL statement analyzed based on an SQL configuration file in the target code file to obtain an SQL statement identifier and a data table corresponding to the SQL statement;

and the mapping module is configured to associate the database layer interface with the data table corresponding to the SQL statement through the SQL identification and the SQL statement identification, and establish a mapping relation between the database layer interface and the data table.

Optionally, the apparatus for determining a data table based on a change code further includes:

the registration module is configured to complete registration in a mode of writing application information of the application into a registry under the condition of receiving a registration request aiming at the application;

the monitoring module is configured to monitor a trigger message for analyzing an analysis task of the mapping relation through a message monitor;

and the pulling module is configured to pull the target code file to a target server according to the application name in the registry based on the trigger message.

the storage module is configured to store the mapping relation in a database in the form of a mapping relation table;

And the reading module is configured to search the data table mapped by the changed database layer interface in the acquired mapping relationship between the database layer interface and the data table analyzed according to the target code file of the application, and read the mapping relationship table in the database before executing a step of changing the data table corresponding to the changed code in the application.

the obtaining module is further configured to obtain, in the code repository pointed by the code repository address, a change code corresponding to the application name between the target code version and the start code version.

According to a third aspect of embodiments herein, there is provided a computing device comprising:

a memory and a processor;

the memory is to store computer-executable instructions, and the processor is to execute the computer-executable instructions to:

According to a fourth aspect of embodiments herein, there is provided a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement any one of the steps of the change code based data table determining method.

The present specification provides a data table determination method based on change codes, including: acquiring a change code submitted by an application under the condition of receiving an update request submitted by the application; determining a change database layer interface called by a change method to which the change code belongs according to a change line number corresponding to the change code in a change file; and searching a data table mapped by the changed database layer interface in the acquired mapping relation between the database layer interface and the data table analyzed according to the target code file of the application, wherein the data table is used as a changed data table corresponding to the changed code in the application.

An embodiment of the present specification realizes that, after a change code for an application is determined, a change database layer interface corresponding to the change code is further determined, and in an obtained mapping relationship between a database layer interface and a data table parsed according to a target code file of the application, a data table mapped by the change database layer interface is searched as a change data table corresponding to the change code in the application, so that the determination of the change data table corresponding to the change code is realized, a data table affected by the change code can be known in a targeted manner before the change code is online, and a data table with an error can be quickly located after the change code is online.

Drawings

FIG. 1 is a flow diagram of a change code based data table determination method provided by one embodiment of the present description;

FIG. 2 is a process flow diagram of a change code-based data table determination method applied to a Java application according to an embodiment of the present specification;

FIG. 3 is a schematic structural diagram of an apparatus for determining a data table based on change codes according to an embodiment of the present disclosure;

fig. 4 is a block diagram of a computing device according to an embodiment of the present disclosure.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, as those skilled in the art will be able to make and use the present disclosure without departing from the spirit and scope of the present disclosure.

The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first can also be referred to as a second and, similarly, a second can also be referred to as a first without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

In this specification, a change code-based data table determining method is provided, and one or more embodiments of the specification relate to a change code-based data table determining apparatus, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments one by one.

An embodiment of a method for determining a data table based on a change code provided by the present specification is as follows:

fig. 1 is a flowchart illustrating a data table determination method based on change codes according to an embodiment of the present disclosure, including steps S102 to S106.

Step S102, when receiving an update request submitted by an application, acquiring a change code submitted by the application.

The application refers to an application that can be run on an electronic device, the application has corresponding code files, the code files store codes written by a programming language, and codes in the code files realize functions in the application corresponding to the code files, specifically, the application can be a Java application, a C language application, a C + + language application, and the like.

The update request may be an update request for updating a code in a code file corresponding to an application, or a completion phase request for completing code update in an iteration cycle, in an actual application, after an application is online, a research and development worker needs to repair some defects existing in the application, or research and development of new functions are performed based on new requirements of the application, the repair or the online new functions need to update the code of the application, and the updates are usually not completed online at one time, but need to be divided into multiple times, or continuously and periodically update the code of the application online, and the process is a code iteration process; generally, after a code update of an iteration stage is completed, a completion stage request is submitted for the iteration stage, and in the case of receiving the completion stage request, an update code for the application in the iteration stage is obtained based on the completion stage request.

Optionally, the change request includes: the application name, code repository address, start code version, object code version of the application.

The code warehouse address refers to an address for storing a code file of an application, and the code file of the application can be obtained through the address; the version of the start code may be a version identifier corresponding to an application code at the beginning of the current iteration stage; the version identifier corresponding to the application code when the update request is submitted by the target code version, specifically, the change code submitted for the application can be obtained through the request information carried by the update request.

In practical application, when a developer finishes the code development of an iteration stage for a certain application, the developer submits the codes developed by the developer in the iteration stage through an iteration life cycle management platform, and the developed codes, namely the change codes, can be the addition of the codes, the modification of the codes or the deletion of the codes on the basis of the original codes in the application;

specifically, the iterative lifecycle management platform is responsible for research, development, management and release processes of each iteration, and initiates a change notification for the iteration of the application accessed to the data change management and control platform; the data change control platform is responsible for connecting change requests initiated by the iterative life cycle management platform and result query of the code configuration operation and maintenance asset management platform and finally displaying the result to a user; the code configuration operation and maintenance asset management platform is responsible for managing and controlling codes, configuration and operation and maintenance changes which may cause faults; in addition, the SQL parsing module is used for parsing the mapping relation between the database layer interface at the application rear end and the corresponding data table aiming at the application, and when the SQL parsing module is specifically implemented, the platforms and the modules are matched with each other through request or call, and the data table influenced by the change codes in the application is further determined.

Further, the updating request includes: on the basis of the application name, the code repository address, the start code version, and the target code version of the application, in an optional implementation manner provided in this embodiment of the present specification, the obtaining of the change code submitted for the application is specifically implemented in the following manner:

and obtaining a change code of the application code version, which corresponds to the application name between the target code version and the starting code version, in the code warehouse pointed by the code warehouse address.

In specific implementation, code modification is submitted for an application for multiple times in an iteration stage, and each code modification corresponds to an application code version number, so that the change code of the application code version between the target code version and the start code version is obtained, namely the change code submitted for the application corresponding to the change request.

Taking a Java application as an example, the application name of the Java application is App03, and the update request for the application includes the following information: application name App03, code repository address: server01/Build, the version of the start code is: and the Version0005, the target code Version is Version0008, and under the condition of receiving the updating request, under the condition that the code repository address Server01/Build points to the Build directory under the Server01, the change code submitted by the code of the Java application App03 between the target code Version0008 and the start code Version0005 is obtained.

In the embodiment of the present specification, the change code of the application code version corresponding to the application name between the target code version and the start code version is obtained in the code repository to which the address of the code repository points, so that a data basis is provided for subsequently determining the change data table corresponding to the change code.

And step S106, determining a change database layer interface called by the change method to which the change code belongs according to the change line number corresponding to the change code in the change file.

In specific implementation, on the basis of obtaining the change code, the change line number corresponding to the change code in the change file is determined, the change method to which the change line number belongs is further determined, and then the database layer interface called by the change method is searched from the analyzed calling relationship between the application method and the database layer interface to serve as the change database layer interface.

Specifically, the change database layer interface refers to a method of a data layer called by a change code corresponding to a change method, the method can directly operate a data table, in practical application, the change database layer interface can be a Dao layer interface, calling relations exist between an upstream method and a downstream method in application, some methods are called directly, and some methods are called indirectly, that is, a plurality of layers of method calls exist between the methods with the calling relations, for example, a calling relation exists between a method a and a calling database layer interface D, but instead of the method a calling the database layer interface D directly, the method a calls a method B, the method B calls a method C, and the method C calls the database layer interface D.

In an optional implementation manner provided by the embodiment of this specification, the determining, according to the change line number corresponding to the change code in the change file, a change database layer interface called by the change method to which the change code belongs is specifically implemented by the following method:

The change type may be specifically classified into a code type or a non-code type, where a code corresponding to the code type may be a Java code, a C language code, and the like in a code file in the application, and the information corresponding to the non-code type is not limited herein, and may be configuration information in a configuration file other than the code type in the application or change information in another file.

The code change file can be a code file in which a code with a change type corresponding to the code type in the change code is located; the code change line number list may be a set of line numbers of the codes in the code change file, where the line number set is shown in a list form, for example, to add a code, the added line number list corresponding to the added code in the code change file05 is addLineList {3, 6, 17}, to delete a code, the deleted line number list corresponding to the deleted code in the code change file05 is delelinelist {4, 9}, and to modify a code, and the modified line number list corresponding to the modified code in the code change file05 is modifiedLineList {2, 10 }.

In addition, there is a change method list, which may be a set of change methods determined by a code change line number list and a code change file list, and this method set is presented in a method of an object list, for example, the change method of the code corresponding to the add line number 3 in the code change line number list may be determined to be function11 in the code change file05 by the add line number 3 and the code change file05 in the code change line number list, and the change method of the code corresponding to the delete line number 9 in the code change line number list may be determined to be function23 in the code change file05 by the delete line number 9 in the code change line number list and the code change file05, and there are other determined change methods, and the change method list is assembled together as { function11, function23, … … };

Furthermore, the change method list may also include other attributes, such as a function list ═ tone

Name＝function11，Parameters＝0；

Name＝function23，Parameters＝5；

……

}

The object code file may be a part of or all of the code file of the application, and is not limited herein, and taking a Java application as an example, the object code file may be a service interface layer (core) and a dependency (lib) JAR (Java Archive) package of the application.

In practical application, because the database layer interface corresponding to the update method needs to be searched in the call relationship between the method obtained by analysis and the database layer interface according to the change method corresponding to the change code, that is, the generated change structure needs to be matched with the call relationship structure obtained by analysis to obtain the change database layer interface corresponding to the change code, after the change information corresponding to the code change line number list, the code change method list and the non-code type is determined, the information needs to be assembled according to the structure composition of the call relationship structure analyzed in advance to make the structures of the two matching parties consistent so as to obtain the matching result.

In specific implementation, the calling relationship structure between the application methods of the application obtained by analyzing the object Code file can be analyzed through a Byte Code Engineering Library (BCEL), the calling relationship structure of the application methods in the object Code file is obtained, the calling relationship structure is stored in a database, and periodic analysis is triggered through a timing task so that the calling relationship is continuously updated.

In the embodiment of the specification, the change codes are divided into code types and non-code types, a change line number list of the codes in a code update file is obtained for the codes corresponding to the code types, a code change method list to which the codes belong is determined by combining the change line number list and the change method list, and change information corresponding to the code change line number list, the code change method list and the non-code types is assembled to generate a change structure; and further matching the change structure with a call relation structure between the application methods of the application obtained by analyzing the target code file to obtain a change database layer interface corresponding to the change code, thereby providing a basis for further determining a change data table corresponding to the change database layer interface.

And step S108, searching a data table mapped by the changed database layer interface in the acquired mapping relation between the database layer interface and the data table analyzed according to the target code file of the application, and taking the data table as a changed data table corresponding to the changed code in the application.

The change data table refers to a data table which is possibly influenced by a change code, and in practical application, errors of an offline data table corresponding to the data table caused by modification of the change code on the data table structure can be prevented through determination of the data table corresponding to the change code, so that the application is prevented from being trapped in faults due to the modification.

Specifically, the mapping between the analyzed database layer interface and the data table is obtained by analyzing an applied target code file, and in practical application, since the applied code file is iteratively updated, the applied target code file is also updated, the updated target code file needs to be analyzed, and further, the mapping between the updated database layer interface and the data table is obtained.

In specific implementation, the mapping relationship may be obtained by analyzing the target code file in the application through the timing task, after the analysis is completed, the original mapping relationship may be updated by the mapping relationship obtained after the latest timing task is completed, the mapping relationship may also be obtained by manually triggering the analysis of the target code file in the application, and in addition, other triggering manners are also available, which are not limited herein.

In an optional implementation manner provided by the embodiment of this specification, a mapping relationship between the database layer interface and the data table is determined in the following manner:

The analyzing of the object code file may be, for example, by using Java application, acquiring a method and an attribute in the object code file through a reflection mechanism in Java, where the specific method may be to inherit a database layer interface of the Java class in the object code file, and the attribute may be an SQL identification attribute associated with the database layer interface.

The SQL configuration file refers to a corresponding SQL configuration file in an object code file in an application, SQL statements in the SQL configuration file can be obtained through parsing of the SQL configuration file, an abstract syntax tree of the SQL statements is generated, and an SQL statement identifier and a data table corresponding to the SQL statements in the SQL configuration file can be obtained through traversing the abstract syntax tree.

Specifically, the SQL identifier corresponding to the database layer interface and the SQL statement identifier corresponding to the SQL statement may uniquely identify one SQL statement in the application, match the SQL identifier and the SQL statement identifier, associate the database layer interface with the data table corresponding to the SQL statement, and establish a mapping relationship between the database layer interface and the data table.

Taking the Java application as an example, in one of the object code files file05, through a reflection mechanism of Java, a database layer interface corresponding to file05 is obtained as data function2, an SQL identifier corresponding to the database layer interface is SQL005, an abstract syntax tree generated by an SQL statement parsed from an SQL configuration file in the object code file is traversed, the SQL statement is "select from table a", the SQL statement identifier corresponding to the SQL statement is SQL005, the data table is tableA, the SQL identifier SQL005 corresponding to the database layer interface is associated with the SQL statement identifier SQL005 corresponding to the SQL statement, and an established mapping relationship between the database layer interface and the data table is a mapping relationship between database layer interface data function2 and data table tableA.

In the embodiment of the specification, a database layer interface in the target code file and an SQL identifier corresponding to the database layer interface are obtained by reflecting the target code file, and an abstract syntax tree generated by an SQL statement analyzed based on an SQL configuration file in the target code file is traversed to obtain the SQL statement identifier and a data table corresponding to the SQL statement; and correlating the database layer interface with the data table corresponding to the SQL statement through the SQL identification and the SQL statement identification, establishing a mapping relation between the database layer interface and the data table, and providing a comparison basis for subsequently determining a changed data table corresponding to a changed database layer interface corresponding to the changed code.

In an optional implementation manner provided by the embodiment of this specification, before the steps of obtaining a database layer interface in the object code file by parsing the object code file and executing an SQL identifier corresponding to the database layer interface, the method further includes:

The analysis task is an analysis task for analyzing the mapping relation between the database layer interface and the data table according to the target code file.

In practical application, before the mapping relationship between the database layer interface and the data table is analyzed according to the target code file of the application, registration needs to be performed for the application, and the target code file of the application is pulled to a target server according to application information contained in the registration, specifically, the application information may be an application name, a code warehouse address and the like, so that the mapping relationship between the database layer interface and the data table is analyzed according to the target code file on the basis of the pulled target code file.

The trigger message refers to a trigger message for triggering the step of pulling the target code file to the target server according to the application name in the registry and a parsing task of a mapping relationship between a database layer interface and a data table parsed according to the target code file of the application after the target code file is pulled, and the parsing task may be a timing task or a conditional trigger task based on some conditions, which is not limited herein.

In the embodiment of the present specification, in a case where a registration request for the application is received, registration is completed first by writing application information of the application into a registry, and on the basis of completing registration, a message listener monitors a trigger message for an analysis task that analyzes a mapping relationship between a database layer interface and a data table according to an object code file, and based on the trigger message, pulls the object code file to a target server according to the application name in the registry, completes preparation work of the analysis task, and can set a trigger condition for the analysis task according to a service requirement through the trigger message.

In an optional implementation manner provided by the embodiment of this specification, after the step of associating the database layer interface and the data table corresponding to the SQL statement through the SQL identifier and the SQL statement identifier and establishing a mapping relationship between the database layer interface and the data table is executed, the method further includes:

In practical application, the mapping relationship between the database layer interface analyzed according to the target code file of the application and the data table needs to be stored, so that the mapping relationship can be obtained when the data table mapped by the database layer interface is searched in the obtained mapping relationship between the database layer interface analyzed according to the target code file of the application and the data table, and the mapping relationship is used as the corresponding step of changing the data table of the change code in the application.

In the embodiment of the present specification, the mapping relationship between the database layer interface and the data table, which is analyzed according to the target code file of the application, is stored in the database in the form of a mapping relationship table, so that the mapping relationship can be obtained at any time when the mapping relationship is needed.

The following describes the data table determination method based on change codes further by taking the application of the data table determination method based on change codes provided in this specification in Java applications as an example, with reference to fig. 2. Fig. 2 shows a processing flow chart of a data table determination method based on change codes applied to a Java application according to an embodiment of the present specification, and specific steps include step S202 to step S214.

Step S202, when receiving an update request submitted by a Java application, acquiring a change code submitted by the Java application.

And step S204, dividing the change codes into Java code types and non-Java code types according to the change types.

Step S206, acquiring a code change line number list corresponding to the Java code in the code change file.

Step S208, determining a code change method list to which the code belongs based on the code change file in which the Java code is located and the code change line number list.

Step S210, assembling the code change line number list, the code change method list, and the change information corresponding to the non-code type to generate a change structure.

Step S212, matching the change structure with a call relation structure between the application methods of the application obtained by analyzing the object code file, and obtaining the change database layer interface corresponding to the change code.

Step S214, searching the data table mapped by the changed database layer interface in the mapping relation between the database layer interface and the data table analyzed according to the target code file of the application, and using the data table as the changed data table corresponding to the changed code in the Java application.

Specifically, the object code file may be a service interface layer (core) and a dependency (lib) JAR package of an application.

In summary, an embodiment of the present specification realizes that, after a change code for an application is determined, a change database layer interface corresponding to the change code is further determined, and a data table mapped by the change database layer interface is searched in an obtained mapping relationship between a database layer interface and a data table parsed according to a target code file of the application, so as to serve as a change data table corresponding to the change code in the application, and the determination of the change data table corresponding to the change code is realized.

An embodiment of a data table determining apparatus based on change codes provided in this specification is as follows:

corresponding to the above method embodiment, the present specification further provides an embodiment of a data table determining apparatus based on a change code, and fig. 3 shows a schematic structural diagram of a data table determining apparatus based on a change code provided in an embodiment of the present specification. As shown in fig. 3, the apparatus includes:

An obtaining module 302 configured to obtain a change code submitted for an application in a case where an update request submitted for the application is received;

a determining module 304, configured to determine, according to a change line number corresponding to the change code in a change file, a change database layer interface called by a change method to which the change code belongs;

the searching module 306 is configured to search the data table mapped by the changed database layer interface in the obtained mapping relationship between the database layer interface and the data table analyzed according to the target code file of the application, as a changed data table corresponding to the changed code in the application.

Optionally, the determining module 304 includes:

The above is an illustrative scheme of the data table determination device based on the change code of the embodiment. The technical solution of the change code based data table specifying device is the same as that of the change code based data table specifying method, and for details not described in detail, reference may be made to the description of the technical solution of the change code based data table specifying method.

The present specification provides an embodiment of a computing device as follows:

FIG. 4 illustrates a block diagram of a computing device 400 provided in accordance with one embodiment of the present description. The components of the computing device 400 include, but are not limited to, a memory 410 and a processor 420. Processor 420 is coupled to memory 410 via bus 430 and database 450 is used to store data.

Computing device 400 also includes access device 440, access device 440 enabling computing device 400 to communicate via one or more networks 460. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. The access device 440 may include one or more of any type of network interface (e.g., a Network Interface Card (NIC)) whether wired or wireless, such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.

In one embodiment of the present description, the above-described components of computing device 400, as well as other components not shown in FIG. 4, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 4 is for purposes of example only and is not limiting as to the scope of the present description. Those skilled in the art may add or replace other components as desired.

Computing device 400 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smartphone), wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 400 may also be a mobile or stationary server.

The present specification provides a computing device comprising a memory 410, a processor 420, and computer instructions stored on the memory and executable on the processor, the processor 420 being configured to execute the following computer-executable instructions:

the obtaining change code submitted for the application includes:

The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solution of the above-mentioned data table determining method based on change codes belong to the same concept, and details that are not described in detail in the technical solution of the computing device can be referred to the description of the technical solution of the above-mentioned data table determining method based on change codes.

This specification provides one example of a computer-readable storage medium, comprising:

the present specification provides a computer readable storage medium storing computer instructions that, when executed by a processor, are operable to:

the obtaining change code submitted for the application includes:

The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium is the same as that of the above-mentioned data table determination method based on the change code, and for details that are not described in detail in the technical solution of the storage medium, reference may be made to the description of the technical solution of the above-mentioned data table determination method based on the change code.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.

It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of acts, but those skilled in the art should understand that the present embodiment is not limited by the described acts, because some steps may be performed in other sequences or simultaneously according to the present embodiment. Further, those skilled in the art should also appreciate that the embodiments described in this specification are preferred embodiments and that acts and modules referred to are not necessarily required for an embodiment of the specification.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

The preferred embodiments of the present specification disclosed above are intended only to aid in the description of the specification. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the embodiments and the practical application, to thereby enable others skilled in the art to best understand and utilize the embodiments. The specification is limited only by the claims and their full scope and equivalents.

Claims

1. A change code based data table determination method, comprising:

based on the change code, determining a change line number corresponding to the change code in a change file, determining a change method to which the change line number belongs, and searching a database layer interface called by the change method from the analyzed calling relationship between the application method and the database layer interface to serve as a change database layer interface;

2. The method according to claim 1, wherein the step of determining a change line number corresponding to the change code in the change file based on the change code, determining a change method to which the change line number belongs, and searching a database layer interface called by the change method from the analyzed call relationship between the application method and the database layer interface as a change database layer interface comprises:

3. The method for determining a data table based on change codes as claimed in claim 1, wherein the mapping relationship between the database layer interface and the data table is determined as follows:

4. The method according to claim 3, wherein before the steps of obtaining the database layer interface in the object code file by parsing the object code file and identifying the SQL corresponding to the database layer interface are executed, the method further comprises:

5. The method according to claim 3, wherein the step of associating the database layer interface with the data table corresponding to the SQL statement through the SQL identifier and the SQL statement identifier, and establishing the mapping relationship between the database layer interface and the data table further includes:

6. The change code based data table determining method of claim 1, the update request comprising: the application name, code repository address, start code version, object code version of the application;

the obtaining change code submitted for the application includes:

7. A change code based data table determining apparatus comprising:

the determining module is configured to determine a change line number corresponding to the change code in a change file based on the change code, determine a change method to which the change line number belongs, and search a database layer interface called by the change method from the analyzed calling relationship between the application method and the database layer interface to serve as a change database layer interface;

8. The change code based data table determining apparatus of claim 7, the determining module comprising:

9. The change code-based data table determining apparatus according to claim 7, wherein the mapping relationship between the database layer interface and the data table is determined by operating the following modules:

10. The change code based data table determining apparatus of claim 9, further comprising:

11. The change code based data table determining apparatus of claim 9, further comprising:

12. The change code based data table determining apparatus of claim 7, the update request comprising: the application name, code repository address, start code version, object code version of the application;

13. A computing device, comprising:

a memory and a processor;

and searching a data table mapped by the changed database layer interface in the acquired mapping relation between the database layer interface and the data table analyzed according to the target code file of the application, wherein the data table is used as a data table corresponding to the changed code in the application.

14. A computer readable storage medium storing computer instructions which, when executed by a processor, carry out the steps of the change code based data table determining method of any one of claims 1 to 6.