Data processing method, device, electronic device and storage medium

Abstract

The disclosed embodiments disclose a data processing method, apparatus, electronic device, and storage medium, the method comprising: determining data inheritance information of the first business object in response to a business data request for a first business object; wherein the data inheritance information records the data inheritance relationship between the first business object and a second business object; and reading the business data associated with the second business object as the business data of the first business object itself based on the data inheritance information of the first business object. When the method of the disclosed embodiments is used to process the data linkage relationship between objects, it is only necessary to associate different objects through the inheritance relationship between objects to automatically complete the logic of data linkage changes, making the system very flexible, reducing the code for processing the association relationship between each object, saving the system administrator's operation time, and significantly reducing the complexity of operation.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of data processing technology, and in particular to a data processing method, device, electronic device, and storage medium. Background Art

[0002] In the field of enterprise services, there are complex associations between object entities. The associations between object entities constitute a huge data network, and the associations between object representations and object entities are arbitrary and not static.

[0003] Given the arbitrary nature of the relationships between object entities, when an object entity changes, the only way to manually modify its associated objects is to adapt to the changes. However, due to the complex relationships between object entities, manual modification is inefficient, and careless modification errors can lead to more problems. Summary of the Invention

[0004] The embodiments of the present disclosure provide a data processing method, apparatus, electronic device, and storage medium to improve the modification efficiency and accuracy of an object entity.

[0005] In a first aspect, an embodiment of the present disclosure provides a data processing method, including:

[0006] In response to a business data request for a first business object, determining data inheritance information of the first business object; the data inheritance information records a data inheritance relationship between the first business object and a second business object, the data inheritance relationship being used to indicate that business data associated with the second business object is inherited by the first business object;

[0007] According to the data inheritance information of the first business object, the business data associated with the second business object is read as the business data of the first business object itself.

[0008] In a second aspect, an embodiment of the present disclosure further provides a data processing device, including:

[0009] an inheritance information determination module, configured to determine, in response to a business data request for a first business object, data inheritance information of the first business object; the data inheritance information recording a data inheritance relationship between the first business object and a second business object, the data inheritance relationship indicating that business data associated with the second business object is inherited by the first business object;

[0010] The business data reading module is used to read the business data associated with the second business object according to the data inheritance information of the first business object as the business data of the first business object itself.

[0011] In a third aspect, an embodiment of the present disclosure further provides an electronic device, including:

[0012] one or more processing devices;

[0013] a storage device for storing one or more programs;

[0014] When the one or more programs are executed by the one or more processing devices, the one or more processing devices implement the data processing method provided in the embodiment of the present disclosure.

[0015] In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processing device, the data processing method provided in the embodiment of the present disclosure is implemented.

[0016] A data processing solution is provided in the disclosed embodiment. Different objects are associated in the form of a relationship chain by adopting flexible data inheritance attributes. When the data linkage relationship between objects needs to be processed, the different objects only need to be associated through the inheritance relationship between objects. The logic of data linkage changes can be automatically completed, which makes the system very flexible, reduces the code for processing the relationship between each object, saves the operation time of the system administrator, and greatly reduces the operation complexity.

[0017] The above disclosure is only an overview of the technical solution of the present disclosure. In order to more clearly understand the technical means of the present disclosure, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present disclosure more obvious and easy to understand, the specific implementation methods of the present disclosure are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Other features, objects, and advantages of the present disclosure will become more apparent upon reading the detailed description of non-limiting embodiments made with reference to the following drawings. The drawings are for illustration purposes only and are not to be considered as limiting the present disclosure. Like reference characters are used throughout the drawings to denote like parts. In the drawings:

[0019] Figure 1 A flow chart of a data processing method provided in an embodiment of the present disclosure is shown;

[0020] Figure 2 A schematic structural diagram of a data processing device provided in an embodiment of the present disclosure is shown;

[0021] Figure 3 A schematic structural diagram of a data processing device provided in an embodiment of the present disclosure is shown;

[0022] Figure 4 A schematic structural diagram of an electronic device provided in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0023] The present disclosure will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are intended only to illustrate the present disclosure and are not intended to limit the present disclosure. It should also be noted that, for ease of description, the accompanying drawings only illustrate portions relevant to the present disclosure, not all structures.

[0024] Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow charts describe the various operations (or steps) as sequential processes, many of the operations (or steps) therein can be implemented in parallel, concurrently, or simultaneously. In addition, the order of the various operations can be rearranged. The process can be terminated when its operation is completed, but can also have additional steps not included in the accompanying drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0025] Figure 1 The flowchart of a data processing method provided in the embodiment of the present disclosure is shown. The embodiment of the present disclosure is applicable to the case where data is operated when data is processed for an object. The method can be executed by a data processing device, which can be implemented in software and / or hardware, and the device can be configured in a device with network communication function. Figure 1 As shown, the data processing method provided in the embodiment of the present disclosure may include:

[0026] S110. In response to a business data request for a first business object, determine data inheritance information of the first business object; the data inheritance information records a data inheritance relationship between the first business object and a second business object, and the data inheritance relationship is used to indicate that business data associated with the second business object is inherited to the first business object.

[0027] In the embodiments of the present disclosure, an object refers to anything to be studied, from the simplest number to the complex airplane, etc., which can be regarded as an object. An object can not only represent some specific things, but also represent abstract rules, plans or events. The first business object can contain one or more things, and the second business object can contain one or more things. The first business object and the second business object can be things of the same level or things of different levels. For example, the first business object is specifically "employee", and the second business object can be specifically "department"; or, the first business object is specifically "employee", and the second business object can also be specifically "employee".

[0028] In the disclosed embodiment, when there are complex data associations between objects, if the business data of a certain business object is required to perform data operations, it is necessary to find the business data associated with the business object based on the data associations between the objects, so as to perform subsequent data processing operations. That is, the traditional method is to match the complex relationships between business objects in a strong constraint manner, so that the business data can be obtained based on the associations between the matched objects. However, the associations between business objects are not fixed and will change over time. Once changed, it is necessary to frequently modify the permission constraints to adapt to the frequently changing associations between business objects, which will make the configuration process of the business data associations extremely complicated. In addition, configuration errors will inevitably occur during the configuration process. Even if the business data associations are configured correctly, the subsequent need to query the business object association table will also make the data acquisition operation more complicated.

[0029] In the embodiment of the present disclosure, in order to solve the problem of management complexity caused by frequently modifying permission constraints to adapt to frequently changing business scenarios due to matching complex relationships between business objects in a strong constraint manner, the transmission relationship of business data is configured through data inheritance information in the embodiment of the present disclosure. The data inheritance information of the first business object records the data inheritance relationship between the first business object and the second business object. Optionally, the data inheritance information of the first business object records the data transmission rules between the first business object and the second business object from the business association of people, things, and things. It can be seen that the data inheritance information of the first business object plays the role of a dynamic association link between business objects with "people, things, and things" as the core, and is a data management method that takes "application characteristics" as the main line in the process of data transmission in the system.

[0030] S120 . Read the business data associated with the second business object according to the data inheritance information of the first business object as the business data of the first business object itself.

[0031] In the disclosed embodiments, a data inheritance relationship can be pre-established between a first business object and a second business object. After establishing this data inheritance relationship, the business data associated with the second business object can be automatically inherited to the first business object based on this data inheritance relationship. After this process, the first business object appears to directly own the business data associated with the second business object. When a business data request is made to the first business object, the business data associated with the second business object can be directly read as its own business data based on the data inheritance information. This entire reading process can be performed directly from the first business object, without requiring a table lookup.

[0032] In an optional manner of an embodiment of the present disclosure, the data inheritance relationship between the first business object and the second business object specifically includes: a first reference relationship between the first business object and the second business object; and a second reference relationship between the first business object and the second business object, respectively, and the same target business data object.

[0033] In this embodiment, in order to realize the data inheritance function of the business data between the first business object and the second business object, it is necessary to first establish a first reference relationship between the first business object and the second business object, as well as a second reference relationship between the first business object and the second business object, before subsequent data reading operations can be performed based on the first reference relationship and the second reference relationship. Optionally, the first reference relationship can be used to represent the reference association relationship between the first business object itself and the second business object itself. Only with the first reference relationship can it be guaranteed that business data can be transferred between the first business object and the second business object. Otherwise, there will be no bridge for data transfer between the first business object and the second business object, and accordingly, data cannot be transferred between the business objects.

[0034] In this embodiment, a second reference relationship can optionally be used to characterize the business data transfer relationship between the first business object and the second business object. Only with the second reference relationship can it be determined which business data associated with the second business object needs to be inherited by the first business object. When a reference relationship is established between the first business object and a target business data object, and when a reference relationship is established between the second business object and the same target business data object, it indicates that both the first business object and the second business object point to the target business data for the business data to be transferred. In this case, the second reference relationship indicates that the target business data associated with the second business object needs to be transferred to the first business object.

[0035] In this embodiment, since the second reference relationship defines the business data transfer type, that is, both business objects point to the same target business data object. Therefore, when reading the business data associated with the second business object as the business data of the first business object, the business data of the target business data object associated with the second business object can be read based on the second reference relationship in the data inheritance information, and the business data of the target business data object can be used as the business data of the first business object.

[0036] In this embodiment, after establishing the first reference relationship and the second reference relationship between the first business object and the second business object, the first reference relationship and the second reference relationship can be loaded into the database. Then, when a business data request is made to the first business object subsequently, the business data associated with the second business object can be obtained based on the loaded first reference relationship and the second reference relationship. At this time, reading the business data associated with the second business object is like reading the business data of the first business object itself directly from the database, without having to query the relationship between objects based on the relationship table between the first business object and the second business object, and then obtaining the corresponding business data from the database based on the relationship between objects.

[0037] In an optional manner of the embodiment of the present disclosure, the first reference relationship is specifically configured as follows: the field identifier of the business type field associated with the first business object points to the second business object.

[0038] In this embodiment, complex relationships exist between object entities in the enterprise service domain. These relationships are generally described by field references on the objects. The following describes establishing a reference relationship. The fields of a first business object include a business type field. Specifically, the business type field associated with the first business object can be configured to dynamically point the field identifier of the business type field of the first business object to the second business object, thereby establishing a first reference relationship. Figure 2 A schematic diagram of establishing a reference relationship provided in an embodiment of the present disclosure is shown. Figure 2 Taking the first business object as an employee and the second business object as a business department as an example, by pointing the field ID of the department field associated with the employee object to the business department object, a reference association relationship begins to exist between the employee and the business department.

[0039] In an optional manner of the embodiment of the present disclosure, the second reference relationship is specifically configured as follows: the field identifier of the business data field associated with the first business object and the field identifier of the business data field associated with the second business object both point to the target business data object.

[0040] In this embodiment, from the perspective of establishing a reference relationship, both the fields of the first business object and the fields of the second business object can include business data fields. Specifically, the business data fields associated with the first business object and the second business object can be configured to dynamically point the field identifier of the business data field of the first business object to the target business data object, while also pointing the field identifier of the business data field of the second business object to the target business data object. This allows the establishment of a second reference relationship. The corresponding business data in the target business data object is the data to be inherited. For example, taking the first business object as an employee, the second business object as a business department, and the business data field of the first business object as the person in charge field as an example, by configuring the person in charge field, the field ID of the person in charge field of the employee object can be pointed to the target person in charge object, and the field ID of the person in charge field of the business department object can be pointed to the target person in charge object. With the establishment of the first and second reference relationships, a reference relationship is established between the employee object and the business department object. The person in charge field on the employee object and the person in charge field on the department object both reference the same target person in charge object. In this case, the employee object can inherit the target person in charge of the department object.

[0041] In an optional manner of an embodiment of the present disclosure, the storage method of data inheritance relationship includes: single-value field storage and multi-value field storage, wherein the single-value field is an overlay storage of the data inheritance relationship, and the multi-value field is an inheritance hierarchy sequential storage of the data inheritance relationship.

[0042] In this embodiment, when establishing data inheritance information, the business data of the second business object can be inherited to the first business object based on the established data inheritance information. After the first business object inherits the business data of the second business object, the inherited business data needs to be stored in the database. In subsequent queries, the inheritance relationship of the business data can be directly ignored, and the business data can be directly obtained from the first business object. Optionally, when the business data is stored in the database, the field identifier is stored instead of the final inherited business data. Therefore, when the business data itself is updated, there is no need to refresh the data inheritance information of the business data, and thus there is no need to re-store the data inheritance information.

[0043] In this embodiment, for single-value field storage, the final result of business data inheritance is supported for storage on the single-value field. If manually specified, the inherited business data will be directly overwritten. For multi-value field storage, multi-value field storage inheritance is not overwritten like the storage inheritance of single-value fields. The multi-value field storage inheritance method is not appended, that is, after manual specification, the business data inherited from the last time will continue to be added, and the subsequent inherited business data will be appended in the order of inheritance hierarchy. Optionally, the overall solution adopts hierarchical caching for performance, and a large number of write diffusion methods can resolve the "data query avalanche" effect that may be caused by too deep a data inheritance hierarchy.

[0044] In this implementation, a storage structure must be designed to distinguish between manually specified business data and inherited business data. Optionally, a data inheritance relationship table and a business data inheritance write diffusion table can be established. The inheritance relationship chain of business data can also be cached in Radis. During queries and updates, Redis can be used to accelerate queries, prioritizing time over space, using a write diffusion approach.

[0045] The following takes the Employee object and the Department object as an example to explain in detail the data inheritance relationship between the Employee object and the Department object. Table 1 is a descriptive information table for the data inheritance relationship between the Employee object and the Department object, showing a detailed description of the business type field and business data field for the Employee object and the Department object. Table 2 is a data inheritance relationship table for the Employee object and the Department object, showing the data inheritance result achieved based on the data inheritance relationship between the Employee object and the Department object. Table 3 is a write diffusion description information table for the Employee object and the Department object. Table 4 is a data inheritance write diffusion data table for the Employee object and the Department object.

[0046] Table 1

[0047] id describe tenant_id tenants is_inheriting Whether to cut off inheritance record_id Employee record field identifier object_id Employee object field identifier field_id HRBP field of employee inherited_record_id Department record field identifier inherited_object_id Department object field identifier inherited_field_id Negative hrbp field of department updated_at Timestamp

[0048] Table 2

[0049] record_id field_id inherited_record_id inherited_field_id dept_l2 field1_hrbp dept_l1 field1_hrbp dept_l3 field1_hrbp dept_l2 field1_hrbp dept_l4 field1_hrbp dept_l3 field1_hrbp employee1 field2_hrbp dept4 field1_hrbp employee2 field2_hrbp dept3 field1_hrbp

[0050] Table 3

[0051] id describe tenant_id tenants object_id employee's objectId field_id HRBP field of employee record_id employee's recordId inherited_record_id The employee's hrbp field inherits the department's recordId target_record_id The employee's hrbp field inherits the hrbp's recordId updated_at Timestamp

[0052] Table 4

[0053] record_id field_id inherited_record_id target_record_id level order dept_l1 field1_hrbp dept_l1 hrbp1_rid 0 1 dept_l2 field1_hrbp dept_l1 hrbp1_rid 1 1 dept_l2 field1_hrbp dept_l2 hrbp2_rid 0 1 dept_l3 field1_hrbp dept_l1 hrbp1_rid 2 1 dept_l3 field1_hrbp dept_l2 hrbp2_rid 1 1 dept_l3 field1_hrbp dept_l3 hrbp3_rid 0 1 dept_l4 field1_hrbp dept_l1 hrbp1_rid 3 1 dept_l4 field1_hrbp dept_l2 hrbp2_rid 2 1 dept_l4 field1_hrbp dept_l3 hrbp3_rid 1 1 dept_l4 field1_hrbp dept_l4 hrbp4_rid 0 1 employee1 field2_hrbp employee1 hrbp0_rid 0 1 employee1 field2_hrbp dept4 hrbp4_rid 1 1 employee1 field2_hrbp dept3 hrbp3_rid1 2 1 employee1 field2_hrbp dept3 hrbp3_rid2 2 2 employee1 field2_hrbp dept3 hrbp3_rid3 2 3 employee1 field2_hrbp dept2 hrbp2_rid 3 1 employee1 field2_hrbp dept1 hrbp1_rid 4 1 employee2 field2_hrbp employee2 hrbp0_rid 0 1 employee2 field2_hrbp dept3 hrbp3_rid 1 1 employee2 field2_hrbp dept2 hrbp2_rid 2 1 employee2 field2_hrbp dept1 hrbp1_rid 3 1

[0054] In an optional method of the embodiment of the present disclosure, in view of the scenario where batch modification of reference relationships causes a large number of changes in inheritance relationships (for example, adjusting the organizational structure to batch modify the superior department), if there is a value inheritance relationship field below, the synchronous operation is likely to cause a processing timeout. At this time, you can choose to use an asynchronous operation method to search in the order of inheritance hierarchy. In particular, for the storage inheritance method of multi-valued fields, it is particularly necessary to use an asynchronous operation method to search in the order of inheritance hierarchy. Optionally, the value inheritance relationship is allowed in the data definition state and has reasonable business scenarios, but when taking the inherited business data in the running state, it is necessary to identify the circular dead loop, be able to correctly handle the circular dead loop, and stop the loop processing.

[0055] The disclosed embodiment provides a data processing solution. There is an association relationship between object entities. When the data of a certain object changes, how can the data of its associated objects change flexibly? The disclosed embodiment innovatively adopts the method of "data value inheritance" to realize data linkage change. Value inheritance can play the role of a dynamic association link with "people, things, and events" as the core in the business system. It is a management method that takes "application characteristics" as the main line in the propagation of data in the system. It solves the management complexity problem of frequently modifying permission constraints to adapt to frequently changing business scenarios caused by traditional strong constraint model matching business. By adopting flexible data inheritance attributes, different objects are associated in the form of a relationship chain. When processing the data linkage relationship between objects, it is only necessary to associate the objects through data inheritance information to automatically complete the logic of data linkage change. There is no need for hard-coded code modification implementation, nor does it require system administrators to frequently modify business constraint rules. This makes the system very flexible, reduces the code for processing the association relationship between each object, saves the system administrator's operation time, and reduces the complexity of operation.

[0056] Figure 3 The schematic diagram of the structure of a data processing device provided in the embodiment of the present disclosure is shown. The embodiment of the present disclosure is applicable to the case where data is operated when data is processed for an object. The device can be implemented in software and / or hardware, and can be configured in a device with network communication function. Figure 3 As shown, the data processing device provided in the embodiment of the present disclosure includes: an inheritance information determination module 310 and a business data reading module 320. Among them:

[0057] An inheritance information determination module 310 is configured to determine, in response to a business data request for a first business object, data inheritance information of the first business object; the data inheritance information records a data inheritance relationship between the first business object and a second business object, the data inheritance relationship indicating that business data associated with the second business object is inherited by the first business object;

[0058] The business data reading module 320 is configured to read the business data associated with the second business object according to the data inheritance information of the first business object as the business data of the first business object itself.

[0059] Based on the above embodiment, optionally, the data inheritance relationship includes: a first reference relationship between the first business object and the second business object; and a second reference relationship between the first business object and the second business object and the same target business data object respectively;

[0060] Correspondingly, the business data reading module is configured to read the business data of the target business data object associated with the second business object as the business data of the first business object itself.

[0061] Based on the above embodiment, optionally, the first reference relationship is specifically configured as follows: the field identifier of the business type field associated with the first business object points to the second business object.

[0062] Based on the above embodiment, optionally, the second reference relationship is specifically configured as follows: the field identifier of the business data field associated with the first business object and the field identifier of the business data field associated with the second business object both point to the target business data object.

[0063] Based on the above embodiment, optionally, the storage method of the data inheritance relationship includes: single-value field storage and multi-value field storage.

[0064] Based on the above embodiment, optionally, the single-value field is an overlay storage of the data inheritance relationship; and the multi-value field is an inheritance level sequential storage of the data inheritance relationship.

[0065] The data processing device provided in the embodiments of the present disclosure can execute the data processing method provided in any of the above embodiments of the present disclosure, and has the corresponding functions and beneficial effects of executing the data processing method. For technical details not fully described in the above embodiments, please refer to the data processing method provided in any embodiment of the present application.

[0066] Figure 4 FIG2 shows a schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure. Figure 4, which shows a structural diagram of an electronic device 400 suitable for implementing the embodiments of the present disclosure. Figure 4 The electronic device shown is only an example and should not limit the functions and scope of use of the embodiments of the present disclosure.

[0067] like Figure 4 As shown, the electronic device 400 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 401, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage device 408 into a random access memory (RAM) 403. Various programs and data required for the operation of the device 400 are also stored in the RAM 403. The processing device 401, the ROM 402, and the RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0068] Typically, the following devices may be connected to the I / O interface 405: an input device 406 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 407 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 408 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 409. The communication device 409 may allow the device 400 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 4 The apparatus 400 is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0069] In particular, according to a data processing method provided in the aforementioned embodiment of the present disclosure, the process of data processing described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure may include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the data processing method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 409, or installed from the storage device 408, or installed from the ROM 402. When the computer program is executed by the processing device 401, the above-mentioned functions defined in the technical solution of the data processing method provided in the aforementioned embodiment of the present disclosure are executed.

[0070] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0071] The computer-readable medium may be included in the device, or may exist independently without being incorporated into the device.

[0072] Optionally, the computer-readable medium carries one or more programs. When the one or more programs are executed by the device, the device can: determine the data inheritance information of the first business object in response to a business data request for the first business object; the data inheritance information records the data inheritance relationship between the first business object and the second business object, and the data inheritance relationship is used to indicate that the business data associated with the second business object is inherited to the first business object; and read the business data associated with the second business object based on the data inheritance information of the first business object as the business data of the first business object itself.

[0073] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0074] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0075] The units involved in the embodiments described in this disclosure may be implemented in software or hardware. In some cases, the name of a unit does not limit the unit itself. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses."

[0076] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also includes other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned disclosed concepts. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

Claims

1. A data processing method, characterized in that: include: In response to a business data request for a first business object, determining data inheritance information of the first business object; The data inheritance information records a data inheritance relationship between the first business object and the second business object, where the data inheritance relationship indicates that the business data associated with the second business object is inherited to the first business object; Reading the business data associated with the second business object according to the data inheritance information of the first business object as the business data of the first business object itself; The data inheritance relationship includes: a first reference relationship between the first business object and the second business object; and a second reference relationship between the first business object and the second business object and the same target business data object respectively; Correspondingly, reading the business data associated with the second business object as the business data of the first business object itself includes: Reading the business data of the target business data object associated with the second business object as the business data of the first business object itself; The second reference relationship is specifically configured as follows: the field identifier of the business data field associated with the first business object and the field identifier of the business data field associated with the second business object both point to the target business data object; the business data field associated with the first business object and the business data field associated with the second business object are of the same type.

2. The method according to claim 1, characterized in that The first reference relationship is specifically configured as follows: the field identifier of the business type field associated with the first business object points to the second business object.

3. The method according to claim 1, characterized in that The storage methods of the data inheritance relationship include: single-value field storage and multi-value field storage.

4. The method according to claim 3, characterized in that The single-value field is an overlay storage of the data inheritance relationship; the multi-value field is an inheritance level sequential storage of the data inheritance relationship.

5. A data processing device, characterized in that: include: an inheritance information determination module, configured to determine data inheritance information of a first business object in response to a business data request for the first business object; The data inheritance information records a data inheritance relationship between the first business object and the second business object, where the data inheritance relationship indicates that the business data associated with the second business object is inherited to the first business object; a business data reading module, configured to read business data associated with the second business object according to data inheritance information of the first business object, as the business data of the first business object itself; The data inheritance relationship includes: a first reference relationship between the first business object and the second business object; and a second reference relationship between the first business object and the second business object and the same target business data object; Correspondingly, the business data reading module is used to: read the business data of the target business data object associated with the second business object as the business data of the first business object itself; The second reference relationship is specifically configured as follows: the field identifier of the business data field associated with the first business object and the field identifier of the business data field associated with the second business object both point to the target business data object; the business data field associated with the first business object and the business data field associated with the second business object are of the same type.

6. The device according to claim 5, characterized in that The first reference relationship is specifically configured as follows: the field identifier of the business type field associated with the first business object points to the second business object.

7. The device according to claim 5, characterized in that The storage methods of the data inheritance relationship include: single-value field storage and multi-value field storage.

8. The device according to claim 7, characterized in that The single-value field is an overlay storage of the data inheritance relationship; the multi-value field is an inheritance level sequential storage of the data inheritance relationship.

9. An electronic device, characterized in that: include: one or more processing devices; a storage device for storing one or more programs; When the one or more programs are executed by the one or more processing devices, the one or more processing devices implement the data processing method according to any one of claims 1 to 4.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processing device, the data processing method described in any one of claims 1 to 4 is implemented.

Images