CN117951142A

CN117951142A - Data processing method, device, equipment and storage medium

Info

Publication number: CN117951142A
Application number: CN202311094499.2A
Authority: CN
Inventors: 刘杰; 谌立; 俞敏; 曾琳铖曦
Original assignee: Mashang Consumer Finance Co Ltd
Current assignee: Mashang Consumer Finance Co Ltd
Priority date: 2023-08-29
Filing date: 2023-08-29
Publication date: 2024-04-30

Abstract

The invention relates to a data processing method, a device, equipment and a storage medium, wherein the method comprises the following steps: determining a first field name included in a database to be changed, wherein the database to be changed is a database corresponding to a first application; acquiring a first mapping relation, a second mapping relation, a third mapping relation and a fourth mapping relation from a database to be changed, wherein the first mapping relation is a mapping relation between a first field and a second field in a PO, the second mapping relation is a mapping relation between the second field and a third field in a BO, the third mapping relation is a mapping relation between the third field and a fourth field in a VO, and the fourth mapping relation is a mapping relation between the fourth field and a fifth field in an interface; determining M interfaces according to the first field name and the first, second, third and fourth mapping relations; n applications of the plurality of applications are determined from the M interfaces. By adopting the method, all applications of the database including the first field do not need to be detected, and the efficiency of determining the affected application after the first field is changed can be improved.

Description

Data processing method, device, equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a data processing method, apparatus, device, and storage medium.

Background

The fields of an application are stored in a corresponding database. The same fields may exist for databases corresponding to different applications. Other applications, where the database generally includes a field, may be affected when the field in the database to which the application corresponds is changed.

For example, database 1 is used to store fields of a first application, database 2 is used to store fields of a second application, database 3 is used to store fields of a third application, and all of databases 1,2, 3 include field a. When changing field a in database 1, it affects both the first application and also other applications, e.g. the second application and/or the third application. However, it is currently not possible to determine which applications are specifically affected, and all applications in the database including field a need to be detected, which is time-consuming and labor-consuming.

Disclosure of Invention

The invention provides a data processing method, a device, equipment and a storage medium, which are used for efficiently determining applications possibly affected when fields in a database corresponding to a certain application are changed.

In a first aspect, an embodiment of the present invention provides a data processing method, including:

determining the name of a first field included in the database to be changed; the database to be changed is a database corresponding to a first application, and the first application is any one of a plurality of applications;

Acquiring a first mapping relation, a second mapping relation, a third mapping relation and a fourth mapping relation from the database to be changed, wherein the first mapping relation is a mapping relation between the first field and a second field in a persistence object PO, the second mapping relation is a mapping relation between the second field and a third field in a business object BO, the third mapping relation is a mapping relation between the third field and a fourth field in a display layer object VO, and the fourth mapping relation is a mapping relation between the fourth field and a fifth field in an interface;

Determining M interfaces according to the name of the first field, the first mapping relation, the second mapping relation, the third mapping relation and the fourth mapping relation, wherein M is a positive integer;

And determining N applications in the plurality of applications according to the M interfaces, wherein N is a positive integer, and the N applications comprise the first application.

By adopting the method, the name of the first field in the database to be changed is determined, and the first mapping relation to the fourth mapping relation are further obtained from the database. The first mapping relationship to the fourth mapping relationship describe the mapping relationship between the first field and the second field in the PO, the mapping relationship between the second field and the third field in the BO, the mapping relationship between the third field and the fourth field in the VO, and the mapping relationship between the fourth field and the fifth field in the interface, respectively, so that the interface corresponding to the first field can be determined based on the name of the first field and the four mapping relationships. And then determining the corresponding application according to the interface corresponding to the first field, namely determining the specific application influenced by modifying the first field, and adopting the method can improve the efficiency of determining the application influenced by modifying the first field without detecting all the applications of the database including the first field, thereby saving time and labor.

In a second aspect, an embodiment of the present invention provides a data processing apparatus, including:

A processing unit, configured to determine a first field name included in the database to be modified; the database to be changed is a database corresponding to a first application, and the first application is any one of a plurality of applications;

The receiving and transmitting unit is used for acquiring a first mapping relation, a second mapping relation, a third mapping relation and a fourth mapping relation from the database to be changed, wherein the first mapping relation is a mapping relation between the first field and a second field in the persistence object PO, the second mapping relation is a mapping relation between the second field and a third field in the business object BO, the third mapping relation is a mapping relation between the third field and a fourth field in the display layer object VO, and the fourth mapping relation is a mapping relation between the fourth field and a fifth field in an interface;

The processing unit is further configured to determine M interfaces according to the name of the first field, the first mapping relationship, the second mapping relationship, the third mapping relationship, and the fourth mapping relationship, where M is a positive integer; and determining N applications in the plurality of applications according to the M interfaces, wherein N is a positive integer, and the N applications comprise the first application.

In a third aspect, the present application also provides a computer device. The computer device may perform the method design described above. The computer device may be a chip or a circuit capable of performing the functions corresponding to the above-described methods, or a device comprising the chip or the circuit.

In one possible implementation, the computer device includes: a memory for storing computer executable program code; and a processor coupled to the memory. Wherein the program code stored in the memory comprises instructions which, when executed by the processor, cause the computer device or devices in which the computer device is installed to perform the method of any of the above possible designs.

The computer device may further comprise a communication interface, which may be a transceiver, or if the computer device is a chip or a circuit, the communication interface may be an input/output interface of the chip, such as input/output pins or the like.

In one possible design, the computer device comprises corresponding functional units for implementing the steps in the above method, respectively. The functions may be realized by hardware, or may be realized by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions.

In a fourth aspect, the present application provides a computer readable storage medium storing a computer program which, when run on a device, performs a method of any one of the above possible designs.

In addition, the technical effects caused by any implementation manner of the second aspect to the fourth aspect may refer to the technical effects caused by different implementation manners of the first aspect, which are not described herein.

Drawings

FIG. 1 is a schematic diagram of a prior art object-hierarchy relationship;

FIG. 2 is a flowchart of a data processing method according to an embodiment of the present invention;

Fig. 3 is a schematic diagram of four mapping relationships corresponding to a field named "Appname" provided in an embodiment of the present invention;

FIG. 4 is a schematic diagram of a data processing apparatus 400 according to an embodiment of the present invention;

fig. 5 is a schematic diagram of a data processing apparatus 500 according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail below with reference to the accompanying drawings, and it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

The application scenario described in the embodiment of the present invention is for more clearly describing the technical solution of the embodiment of the present invention, and does not constitute a limitation on the technical solution provided by the embodiment of the present invention, and as a person of ordinary skill in the art can know that the technical solution provided by the embodiment of the present invention is applicable to similar technical problems as the new application scenario appears. In the description of the present invention, unless otherwise indicated, the meaning of "a plurality" is two or more.

The data blood relationship is a relationship that data naturally forms with each other in the whole life cycle from generation, processing, fusion, and circulation to final extinction.

Blood edge analysis is a technical means for comprehensively tracking the data processing process, so as to find all relevant data with certain data as a starting point and the relation among the relevant data. Therefore, when a certain data has a problem, the source and the generation process of the problem data can be rapidly positioned through the blood relationship, and the problem data can be conveniently processed later.

The technical concept in the present application is explained:

1. persistent object (PERSISTENT OBJECT, PO)

The objects corresponding to the database, PO, are used to represent the data without any data manipulation. The PO is typically located at the data persistence layer.

2. Business Object (BO)

Conversion between PO and VO can be performed. The BO is typically located at the business layer.

3. Display layer Object (View Object, VO)

The object interacted with the front end is used for displaying, for example, the displaying mode can be a webpage, a client, an APP or the like. The VO is typically located at the traffic control layer.

4. Data persistence layer (Dao layer)

The Dao layer mainly works as a data persistence layer, and some tasks responsible for communicating with the database are encapsulated here.

5. Service layer (Service layer)

The Service layer can put all internal business logic in the processing, such as adding, deleting and checking by the user, or sending verification codes or mails and the like.

6. Service control layer (Controller layer)

The Controller layer is used for controlling the service layer and has the function of mainly supporting a bridge for communicating with the service layer from the outside. For example, when the mobile terminal and the front end call the interface to access related services, the related service layer codes are demodulated by the Controller layer through the Controller layer, and data are returned to the mobile terminal and the front end.

7. Fields in a database

The fields in the database may also be referred to as fields in a database table, and the field types in the database include binary types, character types, date and time types, and the like.

Exemplary, a specific structural diagram for each of the above layers and objects is shown in fig. 1 below. Specifically, the PO is an object corresponding to the database, and conversion can be performed between the PO and the BO, and conversion can be performed between the BO and the VO. Wherein the conversion between PO and BO is at the DAO layer, and the conversion between BO and VO is at the Service layer.

Currently, after a database field of a certain application is changed, it is difficult to determine a specific application affected by the change of the database field. Based on the above, the application provides a data processing method, which is used for efficiently determining the application which is specifically affected when the field in the database corresponding to a certain application is changed.

As shown in fig. 2, the flow of the data processing method provided by the application is specifically as follows:

Step 200: the name of the first field included in the database to be changed is determined.

The database to be changed is a database corresponding to a first application, wherein the first application is any one of a plurality of applications. The first field may be any field in a corresponding database in the first application, which is not limited by the present application.

Step 210: and acquiring a first mapping relation, a second mapping relation, a third mapping relation and a fourth mapping relation from the database to be changed.

The following describes the above-described respective mapping relationships:

(1) First mapping relation

Illustratively, the first mapping is a mapping between the first field and a second field in the PO. The type of the first field is the same as the type of the second field. Illustratively, the first mapping relationship may be determined by an object relationship mapping (Object Relational Mapping, ORM) framework (i.e., programming framework).

For example, a database corresponding to the first application includes a field named "appname", and a PO includes a field named "Appname", and then a mapping relationship between the field named "appname" in the database to be modified and the field named "Appname" in the PO is constructed, and the constructed mapping relationship may be stored in the database corresponding to the first application through a beam pattern agent (BeamMapProxy) class, for example. The names of the fields in the database are different from those of the fields in the PO with the mapping relation, namely, the naming rules of the fields are different. For example, the names of the fields in the PO may be a variant of the names of the fields in the database, such as case-to-case conversion, addition of underlining, and the like.

(2) Second mapping relation

Illustratively, the second mapping is a mapping of the second field in the PO and the third field in the BO. The second mapping may be included in the PO. The name of the second field may be the same as the name of the third field, or the name of the second field may be different from the name of the third field, for example, the name of the third field is a variant of the name of the second field, such as case-to-case conversion, addition of an underline, or the like. In addition, the type of the second field is the same as the type of the third field.

For example, if the name of the second field is "APPCODE" and the type is a character type, the name of the third field may also be "APPCODE" and the type may also be a character type.

For another example, if the name of the second field is "APPCODE" and the type is a character type, the name of the third field is "app_code" and the type is also a character type.

Typically, there is a mapping relationship between fields in one BO and fields in one PO.

(3) Third mapping relation

Illustratively, the third mapping relationship is a mapping relationship of a third field in the BO and a fourth field in the VO. The third mapping relationship may be included in the BO. The names of the third field and the fourth field may be the same, or the names of the third field and the fourth field may be different, for example, the names of the fourth field are variants of the names of the third field, such as case-to-case conversion, addition of underlining, and the like. In addition, the type of the third field is the same as the type of the fourth field.

Typically, there is a mapping relationship between fields in one BO and fields in one VO.

(4) Fourth mapping relation

Illustratively, the fourth mapping relationship is a mapping relationship of a fourth field in the VO and a fifth field in the interface, and the fourth mapping relationship may be included in the VO. The name of the fourth field may be the same as the name of the fifth field, or the name of the fourth field may be different from the name of the fifth field. For example, the name of the fifth field is a variation of the name of the fourth field, such as case-to-case conversion, addition of underlining, and the like. In addition, the type of the fourth field is the same as the type of the fifth field.

Typically, fields in one VO may have a mapping relationship with fields in multiple interfaces.

In one possible implementation manner, before the first mapping relationship, the second mapping relationship, the third mapping relationship and the fourth mapping relationship are obtained from the database to be modified, the second mapping relationship, the third mapping relationship and the fourth mapping relationship may be obtained by: in the event that an application request message for a first application is detected, PO, BO, and VO in each of the plurality of applications are accessed. The application request message may be a hypertext transfer protocol (HypertextTransferProtocol, http) request, or may be another request, which is not limited by the present application, and may illustratively be a PO, BO, and VO in each of a plurality of applications through proxy access. Further, the second mapping relation in PO, the third mapping relation in BO and the fourth mapping relation in VO are obtained through reflection. Wherein the reflection may enable acquisition of the desired parameters without modification of the object. And finally, storing the second mapping relation, the third mapping relation and the fourth mapping relation into a database corresponding to the first application.

Therefore, through the above process, each time an application request message is detected, the PO, the BO and the VO in each application in the plurality of applications can be accessed, so that the second mapping relationship in the PO, the third mapping relationship in the BO and the fourth mapping relationship in the VO are obtained, and each mapping relationship is updated in time.

Illustratively, the four mappings corresponding to the field named "APPNAME" are shown in FIG. 3. The database corresponding to the first application has a field named "APPname", and according to the ORM framework, it can be determined that the field named "APPNAME" exists in the PO1, and the two fields form a first mapping relationship. In the case of detecting an application request message for the first application, the PO, BO, and VO in each of the plurality of applications are accessed, and a second mapping relationship is acquired in the PO1, for example, the second mapping relationship is a mapping relationship between a field named "APPNAME" in the PO1 and a field named "APPNAME" in the BO1, and a third mapping relationship is acquired in the VO1, for example, a mapping relationship between a field named "APPNAME" in the BO1 and a field named "APPNAME" in the VO1, and a fourth mapping relationship is acquired in the VO1, for example, the fourth mapping relationship includes a mapping relationship between a field named "APPNAME" in the VO1 and a field named "APPNAME" in the interface 1, and a mapping relationship between a field named "APPNAME" in the VO1 and a field named "APPNAME" in the interface 3. Further, the first mapping relation, the second mapping relation, the third mapping relation and the fourth mapping relation are all stored in a database corresponding to the first application.

Step 220: and determining M interfaces according to the name of the first field, the first mapping relation, the second mapping relation, the third mapping relation and the fourth mapping relation, wherein M is a positive integer.

Illustratively, after the first mapping relationship, the second mapping relationship, the third mapping relationship, and the fourth mapping relationship are obtained from the database to be modified in step 210, M interfaces may be determined according to the name of the first field and the mapping relationships. Firstly, inquiring a first mapping relation according to the name of a first field to determine a second field in a PO corresponding to the first field, then inquiring the second mapping relation according to the second field in the PO corresponding to the first field to determine a third field in a BO corresponding to the first field, then inquiring the third mapping relation according to the third field in the BO corresponding to the first field to determine a fourth field in a VO corresponding to the first field, and finally inquiring the fourth mapping relation according to the fourth field in the VO corresponding to the first field to determine interfaces corresponding to the first field, wherein the number of the interfaces corresponding to the first field is M.

For example, as shown in fig. 3, if the name of the first field is APPname, the first mapping relationship is queried first, the field named "APPNAME" in PO1 is determined, then the second mapping relationship is queried according to the field named "APPNAME" in PO1, the field named "APPNAME" in BO1 is determined, then the third mapping relationship is queried according to the field named "APPNAME" in BO1, the field named "APPNAME" in VO1 is determined, finally the fourth mapping relationship is queried according to the field named "APPNAME" in VO1, and interface 1 and interface 3 are determined, and 2 interfaces are all obtained.

Step 230: n applications in the plurality of applications are determined according to the M interfaces, wherein N is a positive integer. Wherein the N applications include a first application.

In one possible implementation, after M interfaces are determined in step 220, N applications corresponding to the M interfaces may be determined according to a call relationship between the interfaces and the applications. If the M interfaces do not have corresponding call interfaces, determining an application corresponding to the M interfaces according to a call relationship between the interfaces and the application.

In another possible implementation manner, after determining M interfaces in step 220, it may also be determined whether each of the M interfaces has a corresponding call interface, so as to determine N applications according to the M interfaces and the call interfaces of the M interfaces. For example, if some or all of the M interfaces have corresponding call interfaces, for example, the M interfaces include an interface a, and the call interface corresponding to the interface a is an interface B, that is, the interface a can be called by the interface B, an application corresponding to the M interfaces and the call interfaces of the M interfaces is determined according to a call relationship between the interfaces and the application.

Illustratively, the call relationship between the interface and the application may be determined by pinpoint or otherwise determined, as the application is not limited in this regard.

With the above design, considering that the applications corresponding to the calling interfaces for calling the M interfaces may be affected by the modification of the first field, the applications may not include the first field, but may also be affected by the modification of the first field, so that the determined affected applications are more comprehensive. For example, as shown in fig. 3, if the name of the first field is APPname, the interface 1 and the interface 3 are determined according to the first to fourth mapping relations, where the calling interface of the interface 1 is the interface a, and the interface 3 does not have a calling interface, then according to the interface 1, the interface 3, the interface a determines the affected application, for example, it may be determined that the application calling the interface 1 is the first application, the application calling the interface 3 is the second application, and the application calling the interface a is the fifth application according to pinpoint. Thus, when the first field is changed, the specific application that it affects may be determined to be the first application, the second application, and the fifth application.

Further, in one possible design, after determining N applications according to M interfaces, the corresponding change risk level of the first field may be determined according to the value of N.

In an example, a first threshold may be set, where when N is less than the first threshold, the corresponding change risk level of the first field is a low level, and when N is greater than or equal to the first threshold, the corresponding change risk level of the first field is a high level. Wherein the first threshold is set according to an empirical value.

In another example, a first threshold and a second threshold may also be set, and when N is smaller than the first threshold, the corresponding alteration risk level of the first field is a low level; when N is larger than or equal to a first threshold value and smaller than a second threshold value, the corresponding change risk level of the first field is a middle level; when N is larger than the second threshold value, the corresponding alteration risk level of the first field is high. The first threshold and the second threshold are set according to experience values, and the first threshold is smaller than the second threshold.

Illustratively, when the corresponding change risk level of the first field is a low level, the first field may be automatically changed by the system; when the corresponding change risk level of the first field is medium, the first field is automatically changed through the system after passing through the approval process; when the corresponding change risk level of the first field is high, the first field needs to pass through an approval process and is manually changed by a database manager.

It is to be understood that the present application is not limited to a threshold number of divisions, nor is it limited to a number of levels of divisions. Specifically, the threshold for the database field may be one, two, or J thresholds as described above, J being a positive integer greater than 2. Likewise, the risk level for modification may include a low level, a high level, or a low level, a medium level, a high level, and L levels, where L is a positive integer greater than 3. In addition, after the first field is changed, the code modification and the subsequent application function test are carried out on the specific application affected by the first field.

It should be noted that the embodiment shown in fig. 2 is only described by taking the modification of the first field as an example, and a plurality of fields may be modified simultaneously, which is not limited by the present application. By adopting the method, the name of the first field in the database to be changed is determined, and the first mapping relation to the fourth mapping relation are further obtained from the database. The first mapping relationship to the fourth mapping relationship describe the mapping relationship between the first field and the second field in the PO, the mapping relationship between the second field and the third field in the BO, the mapping relationship between the third field and the fourth field in the VO, and the mapping relationship between the fourth field and the fifth field in the interface, respectively, so that the interface corresponding to the first field can be determined based on the name of the first field and the four mapping relationships. And then determining the corresponding application according to the interface corresponding to the first field, namely determining the specific application influenced by modifying the first field, and adopting the method can improve the efficiency of determining the application influenced by modifying the first field without detecting all the applications of the database including the first field, thereby saving time and labor. Further, a corresponding change risk level may be determined according to the number of affected applications, and a corresponding operation may be performed according to the change risk level.

The data processing method provided by the embodiment of the application can be applied to any scene needing data processing, and can be applied to products of the scenes, for example, updating fields in a database based on requirements, expanding the fields in the database, modifying the types of the fields in the database and the like.

The division of the units in the embodiments of the present invention is schematically shown, which is merely a logic function division, and may have another division manner when actually implemented, and in addition, each functional unit in each embodiment of the present invention may be integrated in one processor, or may exist separately and physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

An embodiment of the present invention further provides a data processing apparatus 400, as shown in fig. 4, including: a processing module 410 and a transceiver module 420.

The transceiver module 420 may include a receiving unit and a transmitting unit. The processing module 410 is configured to control and manage the operations of the data processing apparatus 400. The transceiver module 420 is used to support communication of the data processing apparatus 400 with other apparatuses. Optionally, the data processing apparatus 400 may further comprise a storage unit for storing program code and data of the data processing apparatus 400.

Alternatively, each module in the data processing apparatus 400 may be implemented by software.

Alternatively, the processing module 410 may be a processor or controller, such as a general purpose central processing unit (central processing unit, CPU), a general purpose processor, a Digital Signal Processing (DSP), an Application Specific Integrated Circuit (ASIC), a field programmable gate array (field programmable GATE ARRAY, FPGA) or other programmable logic device, transistor logic device, hardware components, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules and circuits described in connection with the disclosure of embodiments of the application. The processor may also be a combination that performs the function of a computation, e.g., a combination comprising one or more microprocessors, a combination of a DSP and a microprocessor, etc. Transceiver module 420 may be a communication interface, a transceiver, or a transceiver circuit, etc., where the communication interface is generally referred to, and in a specific implementation, the communication interface may include multiple interfaces, and the storage unit may be a memory.

The processing module 410 invokes the transceiver module 420 to perform:

A processing module 410, configured to determine a name of a first field included in the database to be modified; the database to be changed is a corresponding database in a first application, and the first application is any one of a plurality of applications;

The transceiver module 420 is configured to obtain a first mapping relationship, a second mapping relationship, a third mapping relationship, and a fourth mapping relationship from the database to be modified, where the first mapping relationship is a mapping relationship between the first field and a second field in the PO, the second mapping relationship is a mapping relationship between the second field and a third field in the BO, the third mapping relationship is a mapping relationship between the third field and a fourth field in the VO, and the fourth mapping relationship is a mapping relationship between the fourth field and a fifth field in the interface;

the processing module 410 is further configured to determine M interfaces according to the name of the first field, the first mapping relationship, the second mapping relationship, the third mapping relationship, and the fourth mapping relationship, where M is a positive integer; and determining N applications in the plurality of applications according to the M interfaces, wherein N is a positive integer, and the N applications comprise the first application.

An embodiment of the present invention further provides another data processing apparatus 500, as shown in fig. 5, including:

a communication interface 501, a memory 502, and a processor 503;

Wherein the data processing apparatus 500 communicates with other devices, such as sending and receiving messages, through the communication interface 501; a memory 502 for storing program instructions; and a processor 503 for calling the program instructions stored in the memory 502, and executing the method according to the obtained program.

Processor 503 invokes execution of program instructions stored by communication interface 501 and memory 502:

determining the name of a first field included in the database to be changed; the database to be changed is a corresponding database in a first application, and the first application is any one of a plurality of applications;

acquiring a first mapping relation, a second mapping relation, a third mapping relation and a fourth mapping relation from the database to be changed, wherein the first mapping relation is a mapping relation between the first field and a second field in PO, the second mapping relation is a mapping relation between the second field and a third field in BO, the third mapping relation is a mapping relation between the third field and a fourth field in VO, and the fourth mapping relation is a mapping relation between the fourth field and a fifth field in an interface;

The specific connection medium between the communication interface 501, the memory 502, and the processor 503 is not limited to the above embodiment of the present invention, and may be, for example, a bus, which may be classified into an address bus, a data bus, a control bus, and the like.

In the embodiment of the present invention, the processor may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps and logic blocks disclosed in the embodiments of the present invention. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present invention may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.

In the embodiment of the present invention, the memory may be a nonvolatile memory, such as a hard disk (HARD DISK DRIVE, HDD) or a solid-state disk (SSD), or may be a volatile memory (RAM). The memory may also be 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 in embodiments of the present invention may also be circuitry or any other device capable of performing memory functions for storing program instructions and/or data.

The embodiment of the present invention also provides a computer readable storage medium including program code for causing a computer to execute the steps of the method provided in the embodiment of the present invention.

The embodiment of the invention also provides a computer program product, which comprises: computer program code for causing a computer to carry out the steps of the method provided by the embodiments of the invention as described above when the computer program code is run on a computer.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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. It is therefore intended that the following claims be interpreted as including the 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 modifications and variations can be made to the present invention without departing from the scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. A method of data processing, the method comprising:

2. The method of claim 1, wherein the determining M interfaces from the name of the first field, the first mapping, the second mapping, the third mapping, and the fourth mapping comprises:

inquiring a first mapping relation according to the name of a first field to determine a second field in the PO corresponding to the first field;

inquiring a second mapping relation according to the second field to determine a third field in the BO corresponding to the first field;

Inquiring a third mapping relation according to the third field to determine a fourth field in the VO corresponding to the first field;

and inquiring a fourth mapping relation according to the fourth field to determine M interfaces corresponding to the first field.

3. The method of claim 1, comprising, prior to obtaining a first mapping, a second mapping, a third mapping, and a fourth mapping from the database to be modified:

accessing a PO, BO, VO in each of the plurality of applications in case an application request message for the first application is detected;

And obtaining a second mapping relation in the PO, a third mapping relation in the BO and a fourth mapping relation in the VO through reflection, and storing the second mapping relation, the third mapping relation and the fourth mapping relation into a database corresponding to the first application.

4. The method of claim 1, wherein determining N applications from the M interfaces comprises:

determining calling interfaces of the M interfaces according to the M interfaces;

and determining N applications according to the M interfaces and the calling interfaces of the M interfaces.

5. The method of claim 1, wherein the first mapping relationship is determined by an object relationship mapping framework.

6. The method of claim 1, after determining N applications from the M interfaces, comprising:

and determining the change risk level corresponding to the first field according to the value of the N.

7. The method of claim 6, wherein the determining the change risk level corresponding to the first field based on the value of N comprises:

Under the condition that N is smaller than a first threshold value, the change risk level corresponding to the first field is a low level; under the condition that N is larger than or equal to a first threshold value and smaller than a second threshold value, the change risk level corresponding to the first field is a middle level; and under the condition that the N is larger than a second threshold value, the change risk level corresponding to the first field is high, wherein the second threshold value is larger than the first threshold value.

8. A data processing apparatus, the apparatus comprising:

a processing unit, configured to determine a name of a first field included in the database to be modified; the database to be changed is a corresponding database in a first application, and the first application is any one of a plurality of applications;

9. A computer device comprising a processor and interface circuitry for receiving signals from other devices than the device and transmitting signals from the processor to the processor or sending signals from the processor to other devices than the device, the processor being operable to implement the method of any one of claims 1 to 7 by logic circuitry or executing code instructions.

10. A computer readable storage medium storing computer instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 7.