CN112486991B

CN112486991B - Database report processing method and device and electronic equipment

Info

Publication number: CN112486991B
Application number: CN202011366768.2A
Authority: CN
Inventors: 郑海波
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2020-11-26
Filing date: 2020-11-26
Publication date: 2024-03-01
Anticipated expiration: 2040-11-26
Also published as: CN112486991A

Abstract

The embodiment of the invention discloses a database report processing method, a database report processing device and electronic equipment. The method comprises the following steps: in response to receiving an instruction for generating a main sub-object structure instance, determining a first main entity object and a first sub-entity object indicated by the instruction, wherein the first main entity object and the first sub-entity object are reports respectively; invoking a pre-created main sub-object structure indicated by an instruction, mapping a main object in the main sub-object structure to a first main entity object, and mapping a sub-object in the main sub-object structure to a first sub-entity object; the main sub-object structure comprises a preset constraint relation of a main object and a sub-object; the first main entity object and the first sub-entity object are stored respectively. The same main sub-object structure can be multiplexed into a plurality of service scenes with the same or similar service logic, and the first main entity object and the first sub-entity object in each service scene are constrained by utilizing the preset constraint relation packaged in the service scene, so that the multiplexing rate of codes is improved.

Description

Database report processing method and device and electronic equipment

Technical Field

The disclosure relates to the technical field of internet, and in particular relates to a database report processing method, a database report processing device and electronic equipment.

Background

Various data may be stored in the database, such as data for physical objects such as orders, goods, payments, warehouses, dispatches, etc. may be stored in the e-commerce system database. Each entity object can store corresponding data in the form of a database report in the database.

Disclosure of Invention

This disclosure is provided in part to introduce concepts in a simplified form that are further described below in the detailed description. This disclosure is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

The embodiment of the disclosure provides a database report processing method, a database report processing device and electronic equipment.

In a first aspect, an embodiment of the present disclosure provides a database report processing method, where the method includes: in response to receiving an instruction for generating a main sub-object structure instance, determining a first main entity object and a first sub-entity object indicated by the instruction, wherein the first main entity object and the first sub-entity object are reports respectively; invoking a pre-created main sub-object structure indicated by the instruction, mapping a main object in the main sub-object structure to the first main entity object, and mapping a sub-object in the main sub-object structure to the first sub-entity object; the main sub-object structure comprises a preset constraint relation between the main object and the sub-object; the first main entity object and the first sub-entity object are stored separately.

In a second aspect, an embodiment of the present disclosure provides a database report processing apparatus, including: the determining module is used for determining a first main entity object and a first sub-entity object indicated by the instruction in response to receiving the instruction for generating the main sub-object structure instance, wherein the first main entity object and the first sub-entity object are reports respectively; the mapping module is used for calling a pre-created main sub-object structure indicated by the instruction, mapping a main object in the main sub-object structure to the first main entity object, and mapping a sub-object in the main sub-object structure to the first sub-entity object; the main sub-object structure comprises a preset constraint relation between the main object and the sub-object; and the storage module is used for respectively storing the first main entity object and the first sub-entity object.

In a third aspect, an embodiment of the present disclosure provides an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, which when executed by the one or more processors, cause the one or more processors to implement the database report processing method of the first aspect.

In a fourth aspect, an embodiment of the present disclosure provides a computer readable medium having stored thereon a computer program, which when executed by a processor, implements the steps of the database report processing method described in the first aspect.

In response to receiving an instruction for generating a main sub-object structure instance, determining a first main entity object and a first sub-entity object indicated by the instruction, where the first main entity object and the first sub-entity object are reports respectively; invoking a pre-created main sub-object structure indicated by the instruction, mapping a main object in the main sub-object structure to the first main entity object, and mapping a sub-object in the main sub-object structure to the first sub-entity object; the main sub-object structure comprises a preset constraint relation between the main object and the sub-object; the first main entity object and the first sub-entity object are stored separately. By the scheme, the same main sub-object structure can be multiplexed into a plurality of service scenes with the same or similar service logic, and the first main entity object and the first sub-entity object in each service scene are constrained by utilizing the preset constraint relation between the main object and the sub-object packaged in the main sub-object structure, so that the multiplexing rate of codes is improved. In addition, the user does not need to write codes for a plurality of business scenes with the same or similar business logic one by one, so that the burden of writing codes by the user is reduced, and on the other hand, the efficiency of generating the first main entity object and the first sub-entity object with the preset constraint relationship can be improved.

Drawings

The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.

FIG. 1 is a flow chart of one embodiment of a database report processing method according to the present disclosure;

FIG. 2 is a flow diagram of creating a master sub-object structure in accordance with the present disclosure;

FIG. 3 is a flow chart of another embodiment of a database report processing method according to the present disclosure;

FIG. 4 is a schematic diagram of one embodiment of a database report processing apparatus according to the present disclosure;

FIG. 5 is an exemplary system architecture in which a database report processing method of one embodiment of the present disclosure may be applied;

fig. 6 is a schematic diagram of a basic structure of an electronic device provided according to an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.

It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.

It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.

The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

It should be noted that, without conflict, the embodiments of the present disclosure and features of the embodiments may be combined with each other.

Referring to FIG. 1, a flowchart of one embodiment of a database report processing method according to the present disclosure is shown, and as shown in FIG. 1, the database report processing method includes the following steps 101 to 103.

Step 101, in response to receiving an instruction for generating a main sub-object structure instance, determining a first main entity object and a first sub-entity object indicated by the instruction, where the first main entity object and the first sub-entity object are reports respectively.

In practice, a user may create a plurality of entity objects, which may be stored in a database in the form of a database report. In some application scenarios, a computer on which a database system is installed may be used as a terminal device, and the method for processing the database report may be implemented by using the terminal device.

After the entity object is created, the user may send an instruction to generate a master sub-object structure instance. Here, the user may write the corresponding code for generating the main sub object structure instance, and execute the code in the corresponding database development tool, so as to achieve the purpose of sending the above instruction. After receiving the instruction, the terminal device may determine the first main entity object and the first sub-entity object indicated by the instruction. Here, the above instruction may include identity information of the first main entity object and the first sub-entity object, so that the terminal device may find the corresponding first main entity object and first sub-entity object according to the identity information.

For example, after the user creates the entity object such as the commodity, the order, the payment order, the inventory order, the delivery order, the return order, and the inventory order, if the instruction for generating the main sub-object structure example a is received, the terminal device may generate the main sub-object structure example a according to the information contained in the instruction for indicating that the commodity is the first main entity object and that one or more of the order, the payment order, the inventory order, the delivery order, the return order, and the inventory order are the first sub-entity object, and that one or more of the order, the payment order, the inventory order, the delivery order, the return order, and the inventory order are the first sub-entity object.

Step 102, calling a pre-created main sub-object structure indicated by an instruction, mapping a main object in the main sub-object structure to a first main entity object, and mapping a sub-object in the main sub-object structure to a first sub-entity object; the main sub-object structure comprises a preset constraint relation of the main object and the sub-object.

In some application scenarios, the instruction for generating the main sub-object structure instance may include identity information of the main sub-object structure that needs to be called. According to the identity information of the main sub-object structure indicated by the instruction information, the terminal equipment can call the required main sub-object structure. Here, a plurality of main sub-object structures may be created in advance, and each main sub-object structure may have its own identity information. When the user calls, the identity information of the target main sub-object structure can be embedded in the instruction, so that the terminal equipment can determine the target main sub-object structure which the user wants to call in the main sub-object structures. For example, a main sub-object structure a, a main sub-object structure B, and a main sub-object structure C may be created in advance, and each main sub-object structure may be provided with the respective corresponding identity information "a", "B", "C". At this time, if the user wants to call the main sub-object structure B to generate the corresponding main sub-object structure instance B', the identity information "B" may be added to the instruction for generating the main sub-object structure instance, so as to call the main sub-object structure B.

The main sub-object structure may include a main object, a sub-object, and a preset constraint relationship therebetween. When the terminal device invokes the main sub-object structure, the main object in the main sub-object structure may be mapped to the first main entity, and the sub-object may be mapped to the first sub-entity. In this way, the first main entity object and the first sub-entity object can be constrained according to the preset constraint relation between the main object and the sub-object in the main sub-object structure. For example, after the main sub-object structure B is invoked, the first main entity object "commodity" and the first sub-entity object a "order", the first sub-entity object B "payment order", the first sub-entity object c "inventory" and the first sub-entity object d "delivery order" may be constrained according to a preset constraint relationship in the main sub-object structure B. The preset constraint relation may include, for example, that when the first sub-entity object e "returns bill" is added, the first sub-entity object e "returns bill" and the first main entity object "commodity" need to be associated and stored.

Step 103, storing the first main entity object and the first sub entity object respectively.

After the first main entity object and the first sub-entity object are constrained by using the preset constraint relation in the main sub-object structure, the first main entity object and the first sub-entity object can be stored respectively. Thus, a set of reports with preset constraint relationships is created. Then, the user can edit the first main entity object and the first sub-entity object as one target object.

When reports are applied in a business system, it is often seen that: a report contains one or more regions, each of which is directed to the same object, but each of which displays a different theme. A report such as this may be referred to as a "master sub report". Each small area in the main sub-report can be called a sub-report, and the whole report formed by the sub-reports can be called a main report. The business logic can be clearer by storing the corresponding data in the main report and the sub report which are associated in the main report and the sub report.

The user can write and establish the codes corresponding to the main and sub reports according to the service demands, and use the database development tool to run the codes, so as to establish the main and sub reports meeting the service demands. In the related art, when a user designs a main sub-report, one entity object can be determined as the main report, and other entity objects can be determined as sub-reports. And then processing business logic between the main report and the sub report in a hard coding mode when writing codes. However, as the service development requirements increase, the service scenario becomes more complex, and more codes need to be written to meet the current service requirements. As the amount of code increases, the probability of error when the user composes the code increases. Moreover, due to the change of the service logic, an adjustment operation of adding, deleting or modifying the corresponding code is required, and if the service scene is used in a stable practical environment, the adjustment easily causes instability of the service system, thereby bringing corresponding risks. In addition, when codes representing the logic relationship inside the main report and the sub report are written in a hard coding mode, if a plurality of main reports and sub reports with the same or similar business logic exist in the business system, a user still needs to write codes capable of representing the internal logic relationship for each group of main report and sub report according to the business logic, the multiplexing rate of the codes is lower, and the generation efficiency of the main report and the sub report is lower.

In this embodiment, by first determining, in response to receiving an instruction to generate a main sub-object structure instance, a first main entity object and a first sub-entity object indicated by the instruction, where the first main entity object and the first sub-entity object are respectively a report; then, a pre-created main sub-object structure indicated by the instruction is called, a main object in the main sub-object structure is mapped to a first main entity object, and a sub-object in the main sub-object structure is mapped to a first sub-entity object; the main sub-object structure comprises a preset constraint relation of a main object and a sub-object; finally, the first main entity object and the first sub-entity object are stored respectively. The same main sub-object structure can be multiplexed into a plurality of service scenes with the same or similar service logic, and the first main entity object and the first sub-entity object in each service scene are constrained by utilizing the preset constraint relationship between the main object and the sub-object packaged in the main sub-object structure, so that the multiplexing rate of codes is improved. In addition, the user does not need to write codes for a plurality of business scenes with the same or similar business logic one by one, so that the burden of writing codes by the user is reduced, and on the other hand, the efficiency of generating the first main entity object and the first sub-entity object with the preset constraint relationship can be improved.

Referring to FIG. 2, which illustrates a flow chart of one embodiment of pre-creating a main sub-object structure in accordance with the present disclosure, as shown in FIG. 2, a sub-object structure may be pre-created based on steps 201 through 205 as follows.

In step 201, a main object is determined, where the main object includes at least one attribute field.

When the main sub-object structure is created, the main object corresponding to the main sub-object structure needs to be determined first. In some application scenarios, a report with empty content may be created and determined as the primary object, and other child objects may adhere to the report. In other application scenarios, placeholders, template data, etc. may be used in the report for editing. When a user maps a primary object to a first primary entity object, data in the first primary entity object may be saved in the first primary entity object by replacing placeholders or replacing template data.

A plurality of attribute fields may be included in the master object. An attribute field may correspond to an attribute of the primary object. That is, a plurality of attribute fields may be set for the main object to characterize a plurality of attributes possessed by the main object. For example, if a user wants to create a main sub-object structure instance with a main object being a "salesman table", the plurality of attribute fields included in the main object in the main sub-object structure called by the user may map attributes such as salesman name, salesman job number, salesman gender, and the like, respectively.

Step 202, a sub-object array is determined, the sub-object array comprising at least one data.

After the primary object is determined, other reports created may be determined to be child objects attached to the primary object, and the child objects may be associated with an array to form a child object array.

In some application scenarios, the number of sub-objects may be multiple. In these application scenarios, different sub-objects may correspond to different sub-object arrays. Each sub-object can respectively correspond to a plurality of data, the data of each sub-object can be arranged in a corresponding sub-object array, and an association relationship can be established between the sub-object corresponding to the sub-object array and the main object through the sub-object array and the main object.

In some application scenarios, multiple sub-objects may correspond to a multi-dimensional array of sub-objects. In this way, the association relationship between the main object and one sub-object array can be extended to be the association relationship between the main object and the multi-dimensional sub-object array corresponding to the multi-dimensional sub-object array, and the association relationship between the multi-dimensional sub-object corresponding to the multi-dimensional sub-object array and the main object can be established. Compared with a main sub-object structure containing only one sub-object array, the association relationship in the main sub-object structure does not change, so that the stability of the main sub-object structure is not damaged; in addition, as the main object can establish the same association relation with a plurality of sub-objects corresponding to the multi-dimensional sub-object array, the expansibility of the main sub-object structure is improved.

In step 203, a target attribute field of the at least one attribute field is associated with the array of sub-objects.

One attribute field may be selected as the target attribute field. After the attribute field is selected as the target attribute field, the target attribute field may be associated with the child object array, and then an association relationship between the initiator object array and the main object may be established. In some application scenarios, the target attribute field may be associated with the sub-object array by writing and running code that associates the target attribute field with the sub-object array such that a user may map to a corresponding sub-object array through the target attribute field when accessing the target attribute field. In other application scenarios, the identity information of the sub-object array may be associated with the target attribute field, or the user may map to the corresponding sub-object array through the target attribute field when accessing the target attribute field.

Step 204, generating a preset constraint relation between the main object and the sub-object array according to the user instruction.

The user can write codes representing the preset constraint relation between the main object and the sub-object array, and after the codes are run, the preset constraint relation between the main object and the sub-object array can be realized. The preset constraint relationship may include, for example, a preset addition relationship, a preset deletion relationship, a preset modification relationship, a preset query relationship, and the like.

Step 205, encapsulating the main object, the sub-object array, and the preset constraint relationship between the main object and the sub-object array, and generating a main sub-object structure.

After the preset constraint relation corresponding to the user instruction is generated, the main object, the sub-object and the preset constraint relation between the main object and the sub-object can be packaged based on the preset constraint relation to form a corresponding main sub-object structure. Thus, when the user writes codes corresponding to the business scenes of the first main entity object and the first sub-entity object which are the same or similar to the preset constraint relation of the main sub-object structure, the main sub-object structure can be called to generate the first sub-entity object and the first sub-entity object with the preset constraint relation, and the user does not need to write codes for representing the constraint relation between the first sub-entity object and the first sub-entity object, so that the burden of writing codes by the user is reduced.

In some alternative implementations, the step 203 may include: and setting the identity of the main object in a preset attribute field corresponding to the child object array.

In some application scenarios, the identity of the main object may be set in a preset attribute field corresponding to the child object array, so as to establish an association relationship between the main object and the child object array.

For example, in these application scenarios, if the identity of the main object is "123", the identity may be set in an identity attribute field (preset attribute field) corresponding to the child object array, and then an association relationship between the main object and the child object array may be established.

In some alternative implementations, the preset constraint relationship includes at least one of: adding, deleting, modifying and inquiring main objects; adding, deleting, modifying and inquiring child objects; and modifying and inquiring the main sub object instance corresponding to the main sub object structure.

The user can write a code representing a first preset constraint relation for generating the constraint main object, and after the code is operated, a corresponding first preset constraint relation can be generated, and the user can realize the operation of adding, deleting, modifying and inquiring the first main entity object through the first preset constraint relation; the code representing the second preset constraint relation for generating the constraint sub-object can be written, and after the code is operated, a corresponding second preset constraint relation can be generated, and the user can realize the adding operation, the deleting operation, the modifying operation and the inquiring operation on the first sub-entity object through the second preset constraint relation; and a code representing a third preset constraint relation for generating the constraint main sub object structure instance can be written, and after the code is operated, a corresponding third preset constraint relation can be generated, and through the third preset constraint relation, the user can realize modification operation and query operation on the main sub object structure instance. After the main sub object structure with the preset constraint relation is called and the corresponding main sub object structure instance is generated, when the main sub object structure instance or the first main entity object and the first sub entity object are subjected to addition operation, deletion operation, modification operation or query operation, the main sub object structure instance or the first main entity object and the first sub entity object can be constrained based on the preset constraint relation, so that the method is convenient and practical.

Referring to FIG. 3, a flowchart of another embodiment of the database report processing method of the present disclosure is shown, and as shown in FIG. 3, the database report processing method includes the steps of:

in step 301, in response to receiving an instruction for generating a main sub-object structure instance, it is determined that a first main entity object and a first sub-entity object indicated by the instruction are respectively a report.

Step 302, a pre-created main sub-object structure indicated by an instruction is called, a main object in the main sub-object structure is mapped to a first main entity object, and a sub-object in the main sub-object structure is mapped to a first sub-entity object; the main sub-object structure comprises a preset constraint relation of the main object and the sub-object.

Step 303, storing the first main entity object and the first sub-entity object, respectively.

The steps 301 to 303 may be the same as or similar to the steps 101 to 103 in the embodiment shown in fig. 1, and will not be described here again.

Step 304, receiving an instruction for executing a preset operation on the first main entity object and the first sub-entity object, which is sent by the user through a preset interface.

The preset interface may be an interface corresponding to a preset constraint relationship. Different preset interfaces may correspond to different preset constraint relationships. The user can send instructions corresponding to the preset interfaces to instruct to execute preset operations through different preset interfaces. For example, the user may send an instruction indicating to perform a preset operation of adding the first sub-entity object through a preset interface a, where the preset interface a corresponds to a preset constraint relationship of adding the sub-object.

In step 305, a preset operation is performed on the first main entity object and the first sub-entity object based on a preset constraint relationship corresponding to the preset interface.

After receiving the instruction, the terminal device can execute corresponding operations on the first main entity object and the first sub-entity object according to a preset constraint relation corresponding to the preset interface. For example, after receiving an instruction sent by the user through the preset interface a and indicating to perform a preset operation of adding the first sub-entity object, the terminal device may perform the following preset operation according to the instruction: and adding a target first sub-entity object, and carrying out association storage on the target first sub-entity object and a corresponding first main entity object.

Compared with the embodiment shown in fig. 1, the embodiment highlights that the user instructs the terminal device to execute the corresponding operation on the first main entity object and the first sub-entity object through the preset interface corresponding to the preset constraint relationship, so that the user experience is improved.

In some alternative implementations, step 304 includes: receiving a modification instruction of a first sub-entity object sent by a user through a first preset interface corresponding to a preset constraint relation, wherein the modification instruction comprises an identity of a first main entity object, an identity of the first sub-entity object and position information corresponding to data to be modified.

The user may send a modification instruction for modifying the first sub-entity object to the terminal device based on the first preset interface. In some application scenarios, the user may write the identity of the first main entity object, the identity of the first sub-entity object, and the location information corresponding to the data to be modified in the code characterizing the modification instruction, so that the terminal device may determine the specific location of the data to be modified according to the identity of the first main entity object, the identity of the first sub-entity object, and the location information corresponding to the data to be modified.

Thus, the step 305 may include: and modifying the data in the first sub-entity object at the position indicated by the position information according to the preset modification constraint relation corresponding to the first preset interface.

After receiving the modification instruction, the terminal device can determine the specific position of the data which the user wants to modify according to the identity of the first main entity object, the identity of the first sub entity object and the position information corresponding to the data to be modified, which are contained in the modification instruction. After determining the specific location of the data that the user wants to modify, the first sub-entity object may be modified according to the modification requirements of the user.

For example, the user may send a modification instruction through the first preset interface to modify the chinese score of Zhang three in the first sub-entity object "chinese score table" from 85 score to 90 score. After receiving the modification instruction, the terminal device may find the first main entity object "student table" according to the identity identifier "A1" of the first main entity object "student table" included in the modification instruction, and find the first sub-entity object associated with the first main entity object, and then may find the first sub-entity object "language score table" according to the identity identifier "A1" of the first sub-entity object included in the modification instruction, and find the language score of Zhang three according to the position information "seventh row and third column" corresponding to the to-be-modified data "Zhang three", and then may modify Zhang three language score in the first sub-entity object from 85 to 90.

In some alternative implementations, the step 304 may further include: receiving a search instruction for the first sub-entity object sent by a user through a second preset interface corresponding to a preset constraint relation, wherein the search instruction comprises an identity of a first main entity object and an identity of the first sub-entity object.

The user may send a search instruction for searching the first sub-entity object to the terminal device based on the second preset interface. In some application scenarios, the user may write the identity of the first main entity object and the identity of the first sub-entity object in the code characterizing the search instruction, so that the terminal device may find the corresponding first sub-entity object according to the identity of the first main entity object and the identity of the first sub-entity object.

Thus, the step 305 may include: and searching the first sub-entity object in a preset database according to a preset searching constraint relation corresponding to the second preset interface.

After receiving the search instruction, the terminal device can search the first sub-entity object in a preset database according to the identity of the first main entity object and the identity of the first sub-entity object contained in the search instruction. The preset database may include a storage area for storing the first main entity object and the first sub-entity object in the current service scenario.

For example, the preset database contains physical objects such as a shoes order, a shoes inventory, a men's shoes inventory, etc. The identity of the order of the shoes is B1, the identity of the stock list of the women shoes is B1, and the identity of the stock list of the men shoes is B2. When the search instruction contains the identification marks ' B1 ' and ' B2 ', the corresponding men's shoe inventory list can be searched in the preset database according to the two identification marks.

In some alternative implementations, the database report processing method may further include: and displaying the data in the searched first sub-entity object.

In some application scenarios, after the data corresponding to the first sub-entity object is found in the preset database, the data corresponding to the first sub-entity object may be displayed. Here, the data may be presented through a presentation window. For example, when the score of Zhang three in the searched first sub-entity object "Chinese score table" is 90 times, a display window can display the information such as "number of academic: XXX, chinese score: 90 "of information content.

By displaying the data in the searched first sub-entity object, the user can quickly and intuitively see the data, and the user experience is improved.

In some alternative implementations, the step 304 may include: receiving a deleting instruction of the first main entity object sent by a user through a third preset interface corresponding to a preset constraint relation, wherein the deleting instruction comprises an identity of the first main entity object and an identity of a first sub-entity object.

The user may send a deletion instruction for deleting the first main entity object to the terminal device based on the third preset interface. In some application scenarios, the user may write the identity of the first main entity object and the identity of the first sub-entity object in the code characterizing the deletion instruction, so that the terminal device may specify the first main entity object that the user specifically wants to delete.

Thus, the step 305 may include: and sequentially deleting the first sub-entity object and the first main entity object according to a preset deletion constraint relation corresponding to the third preset interface.

After receiving the deletion instruction, the terminal device can delete the corresponding entity object according to the identity in the deletion instruction.

When deleting, the first sub-entity object may be deleted first, and then the first main entity object may be deleted. Thus, when the first master entity is deleted, the first sub-entity object associated therewith is deleted. For example, the user sends a deletion instruction including the identity identifier "A1" of the first main entity object and the identity identifier "A1" of the first sub entity object through the third preset interface, after receiving the deletion instruction, the terminal device may delete the "language score table" corresponding to the identity identifier "A1" and the "math score table" corresponding to the identity identifier "a2" according to the received identity identifier, and then delete the "student table" corresponding to the identity identifier "A1".

In some alternative implementations, the database report processing method may further include: and responding to the received request for modifying the identity of the first main entity object corresponding to the first sub-entity object, and feeding back prompt information for prompting prohibition of modification.

In practice, since the first sub-entity object is attached to the first main entity object, the deviation of the business logic may occur after the first sub-entity object is separated from the first main entity object. For example, analyzing the first sub-entity object "order list" alone cannot know the corresponding order object, and analyzing the "order list" in combination with the first main entity object "order list" can make the user know the detail data corresponding to a certain order object, and thus make the business logic clearer. Therefore, the association relationship between the first sub-entity object and the first main entity object cannot be changed. When the request is received, the user can be prompted that the association relationship cannot be modified so as to ensure that the business logic is not deviated.

In some application scenarios, the method may further include determining, when an access instruction or an operation instruction for accessing the first sub-entity object sent by the user is received, whether the user has permission to access or operate the first main entity object through an identity of the first main entity object included in the instruction, and allowing the user to access or operate the first sub-entity object when it is determined that the user has permission to access or operate the first main entity object.

Referring to fig. 4, a schematic diagram of an embodiment of a database report processing apparatus according to the present disclosure is shown, and as shown in fig. 4, the database report processing apparatus includes a determining module 401, a mapping module 402, and a storing module 403. The determining module 401 is configured to determine, in response to receiving an instruction for generating a main sub-object structure instance, a first main entity object and a first sub-entity object indicated by the instruction, where the first main entity object and the first sub-entity object are respectively a report; a mapping module 402, configured to invoke a pre-created main sub-object structure indicated by the instruction, map a main object in the main sub-object structure to a first main entity object, and map a sub-object in the main sub-object structure to a first sub-entity object; the main sub-object structure comprises a preset constraint relation of a main object and a sub-object; the storage module 403 is configured to store the first main entity object and the first sub entity object respectively.

It should be noted that, the specific processes and the technical effects brought by the determining module 401, the mapping module 402 and the storage module 403 of the database report processing apparatus may refer to the related descriptions of the steps 101 to 103 in the corresponding embodiment of fig. 1, and are not repeated here.

In some optional implementations of this embodiment, the main sub-object structure may be created by a creation module that creates the main sub-object structure in advance based on the following steps: determining a main object, wherein the main object comprises at least one attribute field; determining a sub-object array, the sub-object array comprising at least one datum; associating a target attribute field in the at least one attribute field with the array of sub-objects; generating a preset constraint relation between the main object and the child object array according to a user instruction; and packaging the main object, the sub-object array and a preset constraint relation between the main object and the sub-object array to generate a main sub-object structure.

In some optional implementations of this embodiment, the creating module is further configured to: and setting the identity of the main object in a preset attribute field corresponding to the child object array.

In some optional implementations of this embodiment, the preset constraint relationship includes at least one of: adding, deleting, modifying and inquiring main objects; adding, deleting, modifying and inquiring child objects; and modifying and inquiring the main sub object instance corresponding to the main sub object structure.

In some optional implementations of this embodiment, the database report processing apparatus further includes an operation module, where the operation module is configured to: receiving an instruction for executing preset operation on a first main entity object and a first sub-entity object, which are sent by a user through a preset interface; and executing preset operation on the first main entity object and the first sub-entity object based on a preset constraint relation corresponding to the preset interface.

In some optional implementations of this embodiment, the operation module is further configured to: receiving a modification instruction of a first sub-entity object sent by a user through a first preset interface corresponding to a preset constraint relation, wherein the modification instruction comprises an identity of a first main entity object, an identity of the first sub-entity object and position information corresponding to data to be modified; and modifying the data in the first sub-entity object at the location indicated by the location information according to the preset modification constraint relationship corresponding to the second preset interface.

In some optional implementations of this embodiment, the operation module is further configured to: receiving a search instruction for the first sub-entity object sent by a user through a second preset interface corresponding to a preset constraint relation, wherein the search instruction comprises an identity of a first main entity object and an identity of a first sub-entity object; and searching the first sub-entity object in a preset database according to the preset searching constraint relation corresponding to the second preset interface.

In some optional implementations of this embodiment, the database report processing apparatus further includes a display module, where the display module is configured to: and displaying the data in the searched first sub-entity object.

In some optional implementations of this embodiment, the operation module is further configured to: receiving a deleting instruction of a first main entity object sent by a user through a third preset interface corresponding to a preset constraint relation, wherein the deleting instruction comprises an identity of the first main entity object and an identity of a first sub-entity object; and sequentially deleting the first sub-entity object and the first main entity object according to a preset deletion constraint relation corresponding to the third preset interface.

In some optional implementations of this embodiment, the database report processing apparatus further includes a prompting module, where the prompting module is configured to: and responding to the received request for modifying the identity of the first main entity object corresponding to the first sub-entity object, and feeding back prompt information for prompting prohibition of modification.

Referring to FIG. 5, an exemplary system architecture is shown in which a database report processing method of one embodiment of the present disclosure may be applied.

As shown in fig. 5, the system architecture may include terminal devices 501, 502, 503, a network 504, and a server 505. The network 504 is used as a medium to provide communication links between the terminal devices 501, 502, 503 and the server 505. The network 504 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others. The terminal devices and servers described above may communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol ), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.

The terminal devices 501, 502, 503 may interact with the server 505 via the network 504 to receive or send messages or the like. Various client applications, such as a video distribution application, a search class application, a news information class application, may be installed on the terminal devices 501, 502, 503.

The terminal devices 501, 502, 503 may be hardware or software. When the terminal devices 501, 502, 503 are hardware, they may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablet computers, electronic book readers, MP3 players (Moving Picture Experts Group Audio Layer III, dynamic video expert compression standard audio plane 3), MP4 (Moving Picture Experts Group Audio Layer IV, dynamic video expert compression standard audio plane 4) players, laptop and desktop computers, and the like. When the terminal devices 501, 502, 503 are software, they can be installed in the above-listed electronic devices. Which may be implemented as multiple software or software modules (e.g., software or software modules for providing distributed services) or as a single software or software module. The present invention is not particularly limited herein.

The server 505 may be a server that can provide various services, for example, receives data acquisition requests transmitted from the terminal devices 501, 502, 503, performs analysis processing on the data acquisition requests, and transmits analysis processing results (for example, data corresponding to the above-described acquisition requests) to the terminal devices 501, 502, 503.

It should be noted that, the method for processing the database report provided by the embodiment of the present disclosure may be executed by the terminal device, and accordingly, the database report processing apparatus may be set in the terminal device.

It should be understood that the number of terminal devices, networks and servers in fig. 5 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to fig. 6, a schematic diagram of a configuration of an electronic device (e.g., the terminal device of fig. 5) suitable for use in implementing embodiments of the present disclosure is shown. The electronic device shown in fig. 6 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.

As shown in fig. 6, the electronic device may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 601, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the electronic apparatus are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

In general, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, magnetic tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 shows an electronic device having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a non-transitory computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via communication means 609, or from storage means 608, or from ROM 602. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by the processing device 601.

It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: in response to receiving an instruction for generating a main sub-object structure instance, determining a first main entity object and a first sub-entity object indicated by the instruction, wherein the first main entity object and the first sub-entity object are reports respectively; invoking a pre-created main sub-object structure indicated by an instruction, mapping a main object in the main sub-object structure to a first main entity object, and mapping a sub-object in the main sub-object structure to a first sub-entity object; the main sub-object structure comprises a preset constraint relation of a main entity object and a sub-entity object; the first main entity object and the first sub-entity object are stored respectively.

Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including, but not limited to, an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. The name of the module is not limited to the unit itself in some case, and for example, the storage module 403 may also be described as "a module that stores the first main entity object and the first sub entity object, respectively".

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).

Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.

Claims

1. A method for processing a database report, comprising:

in response to receiving an instruction for generating a main sub-object structure instance, determining a first main entity object and a first sub-entity object indicated by the instruction, wherein the first main entity object and the first sub-entity object are reports respectively;

invoking a pre-created main sub-object structure indicated by the instruction, mapping a main object in the main sub-object structure to the first main entity object, and mapping a sub-object in the main sub-object structure to the first sub-entity object; the main sub-object structure comprises a preset constraint relation between the main object and the sub-object;

the first main entity object and the first sub-entity object are stored separately.

2. The method of claim 1, wherein the main sub-object structure is created in advance based on the steps of:

Determining a main object, wherein the main object comprises at least one attribute field;

determining a sub-object array, the sub-object array comprising at least one datum;

associating a target attribute field of the at least one attribute field with the array of sub-objects;

generating a preset constraint relation between the main object and the child object array according to a user instruction;

and packaging the main object, the sub-object array and a preset constraint relation between the main object and the sub-object array to generate the main sub-object structure.

3. The method of claim 2, wherein associating the target attribute field of the at least one attribute field with the array of child objects comprises:

and setting the identity of the main object in a preset attribute field corresponding to the child object array.

4. The method of claim 2, wherein the preset constraint relationship comprises at least one of:

adding, deleting, modifying and inquiring the main object;

adding, deleting, modifying and inquiring the child objects;

and modifying and inquiring the main sub object instance corresponding to the main sub object structure.

5. The method according to claim 1, wherein the method further comprises:

receiving an instruction which is sent by a user through a preset interface and used for executing preset operation on the first main entity object and the first sub-entity object;

and executing the preset operation on the first main entity object and the first sub-entity object based on a preset constraint relation corresponding to the preset interface.

6. The method of claim 5, wherein receiving the instruction for performing the preset operation on the first main entity object and the first sub-entity object, which is sent by the user through the preset interface, includes:

receiving a modification instruction of the first sub-entity object sent by a user through a first preset interface corresponding to the preset constraint relation, wherein the modification instruction comprises an identity of the first main entity object, an identity of the first sub-entity object and position information corresponding to data to be modified; and

the performing the preset operation on the first main entity object and the first sub-entity object based on a preset constraint relation corresponding to the preset interface includes:

and modifying the data in the first sub-entity object at the position indicated by the position information according to a preset modification constraint relation corresponding to the first preset interface.

7. The method of claim 5, wherein receiving the instruction for performing the preset operation on the first main entity object and the first sub-entity object, which is sent by the user through the preset interface, further comprises:

receiving a search instruction for the first sub-entity object sent by a user through a second preset interface corresponding to the preset constraint relation, wherein the search instruction comprises an identity of the first main entity object and an identity of the first sub-entity object; and

and searching the first sub-entity object in a preset database according to a preset searching constraint relation corresponding to the second preset interface.

8. The method of claim 7, wherein the method further comprises:

and displaying the searched data in the first sub-entity object.

9. The method of claim 5, wherein receiving the instruction for performing the preset operation on the first main entity object and the first sub-entity object, which is sent by the user through the preset interface, further comprises:

Receiving a deleting instruction to the first main entity object sent by a user through a third preset interface corresponding to the preset constraint relation, wherein the deleting instruction comprises an identity of the first main entity object and an identity of the first sub-entity object; and

and deleting the first sub-entity object and the first main entity object in sequence according to a preset deletion constraint relation corresponding to the third preset interface.

10. The method according to claim 1, wherein the method further comprises:

and responding to the received request for modifying the identity of the first main entity object corresponding to the first sub-entity object, and feeding back prompt information for prompting prohibition of modification.

11. A database report processing apparatus, comprising:

the determining module is used for determining a first main entity object and a first sub-entity object indicated by the instruction in response to receiving the instruction for generating the main sub-object structure instance, wherein the first main entity object and the first sub-entity object are reports respectively;

The mapping module is used for calling a pre-created main sub-object structure indicated by the instruction, mapping a main object in the main sub-object structure to the first main entity object, and mapping a sub-object in the main sub-object structure to the first sub-entity object; the main sub-object structure comprises a preset constraint relation between the main object and the sub-object;

and the storage module is used for respectively storing the first main entity object and the first sub-entity object.

12. An electronic device, comprising:

one or more processors;

storage means having stored thereon one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-10.

13. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any one of claims 1-10.