Table data processing method, device, equipment, medium and product

Abstract

Embodiments of the present disclosure provide a table data processing method, device, equipment, medium and product. The method comprises: in response to a data access request for a target table input by a client, displaying at least part of records of the target table in a target interface of the client; a record refers to a row of data in the target table; receiving a sub-record editing operation for the target table through the target interface, determining hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation, and updating display data of the target table in the target interface according to the hierarchical description data; the hierarchical description data is used to describe parent-child relationship data corresponding to the sub-record and a parent record containing the sub-record in the target table. The technical scheme of the embodiments of the present disclosure realizes on-demand loading of records of the table, and can quickly and effectively update the changed records, thereby improving the processing efficiency and use experience of the table.

Description

TECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to the technical field of computer processing, and particularly, to a table data processing method, device, equipment, medium and product. BACKGROUND

[0002] With the rapid development of information technology, tables have become an indispensable part of various industries, which carry a large amount of information in an intuitive and clear way. Users can store, manage and view data records through tables.

[0003] For viewing data records through tables, the table data processing manner in the related art often loads all data records at one time according to an access request of table data, and reloads all data records when the data records change. However, when the data volume is very large (such as million rows), loading all data at one time may cause the client to bear huge memory and computing pressure, resulting in low table processing efficiency and poor user experience. SUMMARY

[0004] Embodiments of the present disclosure provide a table data processing method, device, equipment, medium and product to display records of a table on demand and update changed records quickly and effectively, thereby improving the processing efficiency and user experience of the table.

[0005] In a first aspect, the embodiments of the present disclosure provide a table data processing method, which comprises:

[0006] In response to a data access request for a target table input at a client, displaying at least part of records of the target table in a target interface of the client; wherein the record refers to a row of data in the target table.

[0007] Receiving a sub-record editing operation for the target table through the target interface, determining hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation, and updating display data of the target table in the target interface according to the hierarchical description data; wherein the hierarchical description data is used to describe parent-child relationship data corresponding to the sub-record and the parent record containing the sub-record in the target table.

[0008] In a second aspect, the embodiments of the present disclosure also provide a table data processing device, which comprises:

[0009] A data access request module is configured to display at least part of records of a target table in a target interface of a client in response to a data access request for the target table input at the client; wherein the record refers to a row of data in the target table.

[0010] The table data display module is configured to receive, through the target interface, a sub-record editing operation for the target table, determine hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation, and update display data of the target table in the target interface according to the hierarchical description data; wherein the hierarchical description data is used to describe parent-child relationship data corresponding to the sub-record and a parent record containing the sub-record in the target table.

[0011] In a third aspect, the embodiments of the present disclosure further provide an electronic device, which comprises:

[0012] one or more processors;

[0013] a storage device configured to store one or more programs,

[0014] When the one or more programs are executed by the one or more processors, the one or more processors implement the table data processing method according to any of the embodiments of the present disclosure.

[0015] In a fourth aspect, the embodiments of the present disclosure further provide a storage medium containing computer executable instructions, which are used to execute the table data processing method according to any of the embodiments of the present disclosure when executed by a computer processor.

[0016] In a fifth aspect, the embodiments of the present disclosure further provide a computer program product, which comprises a computer program and is used to implement the table data processing method according to any of the embodiments of the present disclosure when executed by a processor.

[0017] The technical scheme of the embodiment of the present disclosure displays at least part of records of the target table in the target interface of the client in response to the data access request for the target table input by the client, and since the records refer to a row of data in the target table, the on-demand display of the records of the target table is realized. Then, the sub-record editing operation for the target table is received through the target interface, and the hierarchical description data corresponding to the edited sub-record is determined according to the sub-record editing operation. In the technical scheme, the hierarchical description data describing the parent-child relationship data corresponding to the sub-record and the parent record containing the sub-record in the target table is defined, the nesting level of the records in the target table is reduced, and the data structure of the target table is simplified. Then, the display data of the target table in the target interface can be updated relatively quickly and specifically according to the hierarchical description data. The technical scheme of the embodiment of the present disclosure solves the technical problem of low table processing efficiency in the related art, realizes the on-demand display of the records of the table and the specific update of the changed records relatively quickly and effectively, does not need to load all data of the target table, supports the quick editing and display of the sub-records in the on-demand display of the table, and improves the processing efficiency and use experience of the target table. BRIEF DESCRIPTION OF DRAWINGS

[0018] The above and other features, advantages, and aspects of the present disclosure will become more apparent by describing in detail the following specific embodiments in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. It should be understood that the drawings are schematic, and the original and elements are not necessarily drawn according to the scale.

[0019] Figure 1 A flowchart of a table data processing method provided by an embodiment of the present disclosure is shown in the figure;

[0020] Figure 2 A flowchart of another table data processing method provided by an embodiment of the present disclosure is shown in the figure;

[0021] Figure 3 A flowchart of another table data processing method provided by an embodiment of the present disclosure is shown in the figure;

[0022] Figure 4 A flowchart of another table data processing method provided by an embodiment of the present disclosure is shown in the figure;

[0023] Figure 5 An interface example diagram suitable for record display of a table data processing method provided by an embodiment of the present disclosure is shown in the figure;

[0024] Figure 6A timing schematic diagram when response table data of a table data processing method suitable for the table data processing method is loaded on demand is provided for the embodiments of the present disclosure.

[0025] Figure 7 An interface example diagram of a record operation of a table data processing method is provided for the embodiments of the present disclosure.

[0026] Figure 8 A timing schematic diagram when a response sub-record editing operation of a table data processing method suitable for the table data processing method is provided for the embodiments of the present disclosure.

[0027] Figure 9 A structural schematic diagram of a table data processing apparatus is provided for the embodiments of the present disclosure.

[0028] Figure 10 A structural schematic diagram of an electronic device for implementing the embodiments of the present disclosure is provided for the embodiments of the present disclosure. DETAILED DESCRIPTION

[0029] Embodiments of the present disclosure will be described in more detail by referring to the drawings. Although certain embodiments of the present disclosure are shown in the drawings, it is understood that the present disclosure can be implemented in various forms, and should not be interpreted as being limited to the embodiments set forth herein, but rather, these embodiments are provided to make the present disclosure more thorough and complete. It is understood that the drawings and embodiments of the present disclosure are for exemplary purposes only, and are not intended to limit the scope of protection of the present disclosure.

[0030] It should be understood that each step recited in the method embodiments of the present disclosure can be executed in different orders, and / or in parallel. In addition, the method embodiments can include additional steps and / or omit the execution of the steps shown. The scope of the present disclosure is not limited in this respect.

[0031] The term "comprising" and variations thereof as used herein are open-ended, that is, "comprising 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 are given below in the description of the application.

[0032] It should be noted that the concepts of "first", "second", etc. mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not intended to limit the order or interdependence of the functions performed by these devices, modules or units.

[0033] It should be noted that the modification of "one", "multiple" mentioned in the present disclosure is illustrative but not restrictive, and those skilled in the art should understand that "one or more" should be understood unless otherwise explicitly indicated in the context.

[0034] The names of the messages or information exchanged between the plurality of devices in the embodiments of the present disclosure are only for illustrative purposes, and are not used to limit the scope of the messages or information.

[0035] It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the type, use range, use scenario, etc. of the personal information involved in the present disclosure should be informed to the user and the authorization of the user should be obtained through appropriate means according to relevant laws and regulations.

[0036] For example, in response to receiving the active request of the user, the prompt information is sent to the user to explicitly prompt the user that the operation requested to be performed will require obtaining and using the personal information of the user. Thus, the user can voluntarily choose whether to provide the personal information to the software or hardware such as electronic device, application program, server or storage medium, etc. that performs the operation of the technical solutions of the present disclosure according to the prompt information.

[0037] As an optional but not limited implementation manner, in response to receiving the active request of the user, the prompt information can be sent to the user in the form of a pop-up window, and the prompt information can be presented in the form of text in the pop-up window. In addition, the pop-up window can also carry selection controls for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0038] It can be understood that the above notification and user authorization process is only illustrative, and does not limit the implementation manner of the present disclosure, and other manners meeting the relevant laws and regulations can also be applied to the implementation manner of the present disclosure.

[0039] It can be understood that the data involved in the present technical solution (including but not limited to the data itself, the acquisition or use of the data) should comply with the requirements of the relevant laws and regulations and relevant provisions.

[0040] Figure 1 A flowchart of a table data processing method provided by the embodiments of the present disclosure, the embodiments of the present disclosure are applicable to the scene of processing table data, and the method can be executed by a table data processing device. The device can be realized in the form of software and / or hardware, and can be realized by an electronic device, which can be a mobile terminal, a PC terminal or a server, etc. As shown in the figure, the method of the present embodiment can specifically include: Figure 1

[0041] ​S110, in response to the data access request for the target table input by the client, displaying at least part of records of the target table in a target interface of the client; wherein the record refers to one row of data in the target table.

[0042] The target table can be understood as a table that needs to be accessed, and can be used to store, manage and display data records. The data in the target table can be in the form of rows. The record can refer to the data recorded in one row of the target table. In actual application, the target table usually includes multiple rows of data, that is, the target table usually includes multiple records. In the embodiments of the present disclosure, the records in the target table can have a parent-child relationship. The target table can include one or more parent records and one or more child records subordinate to the parent records. It should be noted that the number of child records under different parent records in the target table can be the same or different.

[0043] In the embodiments of the present disclosure, the data access request can be understood as a request for data access to the data in the target table, and can be used to display at least part of the records of the target table in the target interface of the client. In the embodiments of the present disclosure, the target interface can be understood as an interface for displaying at least part of the records of the target table. In the embodiments of the present disclosure, the layout of the target interface can be adaptive layout using a responsive layout, to adapt to display screens of different resolutions; or can be laid out in a preset interface size, wherein the preset interface size can be set according to actual needs, which is not limited here. Optionally, the preset interface size includes a preset interface length and / or a preset interface width.

[0044] In the embodiments of the present disclosure, the application scenario of the data access request for the target table input by the client can be that the records of the target table are not displayed on the target interface of the client; or can be that the records of the target table are displayed on the target interface of the client.

[0045] As an optional implementation of the embodiments of the present disclosure, in response to the data access request for the target table input by the client, specifically, in the case that the records of the target table are not displayed on the target interface of the client, in response to the data viewing operation for the target table input by the client. Based on this, after receiving the data viewing operation for the target table input by the client, the default loaded record of the target table can be determined. Then the default loaded record can be displayed in the target interface of the client. The default loaded record can be understood as a record that needs to be displayed by default when accessing the target table for the first time within a preset time period. For example, the default loaded record can be the record of the target table displayed on the target interface when the target table was closed last time.

[0046] In the embodiments of the present disclosure, the default at least partial records of the target table can be determined based on a preset record identifier and a preset record display number of the target table. The preset record identifier can be used to distinguish the data content in different tables of the target interface. For example, the preset record identifier can be the first record displayed in the target table. In some scenarios, the preset record identifier is referred to as a column title, which is used to identify the data content of the column where the column title is located, or in other words, which is used to distinguish the data content of different columns. The preset record identifier can be set according to actual needs, which is not specifically set here. The preset record display number can be set according to actual needs, which is not specifically limited here, for example, 20, 30, or 50, etc. It can be understood that the preset record display number does not exceed the upper limit of the number of records that can be displayed in the target interface.

[0047] As another optional implementation of the embodiments of the present disclosure, in response to the data access request for the target table input by the client, specifically, in the case that the target interface of the client displays the records of the target table, the target interface is scrolled in response to the operation of the target interface displaying the records of the target table. Based on this, after receiving the scrolling operation of the target interface displaying the records of the target table, the at least partial records of the target table displayed in the target interface of the client are updated.

[0048] In the embodiments of the present disclosure, the storage location of the records of the target table can be the client or the server. There are various ways to display the at least partial records of the target table in the target interface of the client.

[0049] As an optional implementation of the embodiments of the present disclosure, in the case that the storage location of the records of the target table is the client, after receiving the data access request for the target table input by the client, the at least partial records of the target table are read from the client, and the at least partial records are displayed in the target interface of the client.

[0050] As another optional implementation of the embodiments of the present disclosure, in the case that the storage location of the records of the target table is the server, the response to the data access request for the target table input by the client to display the at least partial records of the target table in the target interface of the client can include: in response to the data access request for the target table input by the client, the target data corresponding to the record accessed by the request is obtained from the table data of the target table stored in the server, and the target data is cached in the client; and the target table is displayed in the target interface of the client according to the target data cached in the client.

[0051] The target data can be understood as table data corresponding to the data access request of the target table stored in the server. Specifically, after receiving the data access request for the target table input in the client, the data access request can be sent to the server. Then, the target data corresponding to the record accessed can be obtained from the table data of the target table stored in the server. After obtaining the target data of the server, the target data can be stored in the cache of the client. Then, according to the target data cached in the client, the target table can be displayed in the target interface of the client. Generally, the target data is the data displayed in the target interface, that is, the table data that needs to be rendered by the view layer.

[0052] On the basis of the above embodiment, in order to facilitate subsequent access to the target table through the client, after the client receives the target data issued by the server, the target data of the target table can be stored in a preset storage location. On this basis, in order to reduce the occupation of the storage space of the client, when the client receives the target data of the target table issued by the server, the receiving time of the target data can be marked. Within a preset time period from the receiving time, if no data access request for the target table is input in the client, the target data stored in the client can be deleted.

[0053] S120, receiving a sub-record editing operation for the target table through the target interface, determining hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation, and updating the display data of the target table in the target interface according to the hierarchical description data; wherein the hierarchical description data is used to describe the parent-child relationship data corresponding to the sub-record and the parent record containing the sub-record in the target table.

[0054] The sub-record editing operation can be understood as an operation for editing a sub-record in the target table. In the embodiment of the present disclosure, the sub-record editing operation can include a sub-record adding operation and / or a sub-record deleting operation. The sub-record adding operation can be understood as an operation for adding at least one sub-record in the target table. The sub-record deleting operation can be understood as an operation for deleting at least one sub-record in the target table. In the disclosed embodiment, the hierarchical description data can be used to describe the parent-child relationship data corresponding to the sub-record and the parent record containing the sub-record in the target table. That is, the hierarchical description data can be used to determine the parent record to which the sub-record belongs and all sub-records under the parent record.

[0055] In the embodiments of the present disclosure, the storage location of the hierarchical description data can be the client, or can be the server. There are various ways to determine the hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation.

[0056] As an optional implementation of the embodiments of the present disclosure, in the case where the storage location of the hierarchical description data is the client, the edited sub-record can be determined according to the sub-record editing operation. Then, the hierarchical description data corresponding to the edited sub-record in the client can be updated based on the edited sub-record. Thus, the hierarchical description data corresponding to the edited sub-record can be read from the client.

[0057] As another optional implementation of the embodiments of the present disclosure, in the case where the storage location of the hierarchical description data is the server, the edited sub-record can be determined according to the sub-record editing operation. After the edited sub-record is determined, the edited sub-record can be sent to the server, so that the server updates the hierarchical description data corresponding to the edited sub-record, and the updated hierarchical description data is pushed to the client, so that the client obtains the hierarchical description data corresponding to the edited sub-record.

[0058] In the embodiments of the present disclosure, the updating of the display data of the target table in the target interface according to the hierarchical description data can specifically include: determining the parent record to which the edited sub-record belongs and all sub-records under the parent record according to the hierarchical description data. Thus, the display data of the target table in the target interface can be updated based on the parent record to which the edited sub-record belongs and all sub-records under the parent record.

[0059] In the embodiments of the present disclosure, the hierarchical description data can include first description data and second description data. The first description data can be used to describe the parent-child relationship between the sub-record and the parent record to which the sub-record belongs. The second description data can be used to describe the parent-child relationship between the parent record and the sub-record contained in the parent record. In the embodiments of the present disclosure, the first description data and the second description data are used as the hierarchical description data, which has the advantage that in the case where a sub-record is added or deleted under a certain parent record of the target table displayed in the target interface, the changed record in the target table can be loaded specifically without reloading all records of the target table. In addition, the record of the target table in the target interface can be loaded and displayed on demand more quickly and effectively.

[0060] In the embodiments of the present disclosure, the hierarchical description data is stored in the form of a key-value pair (Map). The first description data can take the identification of the sub-record as the key and the identification of the parent record to which the sub-record belongs as the value. The second description data can take the identification of the parent record as the key and the identification of the sub-record subordinate to the parent record as the value. In the embodiments of the present disclosure, two Maps are used, one for storing the mapping of sub-records to parent records, i.e., the first description data, and the other for storing the mapping of parent records to sub-records, i.e., the second description data, which realizes the flat data storage of the records in the target table, reduces the nested level of data, makes the data access more direct, and makes the addition, deletion and modification of records more flexible. In addition, the use of Map can facilitate the updating of the parent-child relationship between the parent records and the sub-records in the target table without the need to reconstruct the entire data structure. Furthermore, it also avoids the repeated storage of data and facilitates understanding and maintenance.

[0061] On the basis of the above-mentioned embodiments, the hierarchical description data corresponding to the edited sub-record can be determined according to the sub-record editing operation, specifically including: in the case where the sub-record editing operation includes a sub-record addition operation, the first description data corresponding to the added sub-record can be added, and the description data corresponding to the added sub-record can be written into the second description data of the parent record to which the added sub-record belongs; and / or in the case where the sub-record editing operation includes a sub-record deletion operation, the first description data corresponding to the added sub-record can be deleted, and the description data corresponding to the added sub-record can be deleted from the second description data of the parent record to which the added sub-record belongs. With this technical solution, the deletion of sub-records can be realized simply and quickly, the processing rate of the target table is improved, and the view update speed after the deletion of sub-records is improved.

[0062] On the basis of the above-mentioned embodiments, the embodiments of the present disclosure can further include that the client can include a current client and a collaborative client cooperating with the current client. In the embodiments of the present disclosure, the number of the collaborative client can be one, two or more than two. The current client and the collaborative client respectively establish a data communication link with the server based on a network communication protocol (such as Websoket). After the collaborative client receives the sub-record editing operation for the target table, the collaborative client can send the sub-record editing operation for the target table to the server, so that the server broadcasts the message of the sub-record editing operation for the target table of the collaborative client to the client in communication link with the server. After the current client obtains the message from the data communication link, the sub-record editing operation for the target table of the collaborative client can be obtained based on the message. Then, the sub-record editing operation for the target table of the collaborative client can be executed on the target table of the current client, thereby realizing the function of multiple clients cooperating to process the sub-record editing operation of the target table.

[0063] The technical scheme of the embodiments of the present disclosure displays at least part of the records of the target table in the target interface of the client in response to the data access request for the target table input by the client, and since the records refer to a row of data in the target table, the on-demand display of the records of the target table is realized. The sub-record editing operation for the target table is received through the target interface, and the hierarchical description data corresponding to the edited sub-record is determined according to the sub-record editing operation. In the technical scheme, the hierarchical description data describing the parent-child relationship data corresponding to the sub-records in the target table and the parent records containing the sub-records is defined, so as to reduce the nesting level of the records in the target table and simplify the data structure of the target table. Then, the display data of the target table in the target interface can be updated relatively quickly and targetedly according to the hierarchical description data. The technical scheme of the embodiments of the present disclosure solves the technical problem of low table processing efficiency in the existing table processing, realizes the on-demand loading of the records of the table and the relatively quick and effective targeted updating of the changed records, does not need to load all the data of the target table, supports the quick editing and display of the sub-records in the on-demand display of the table scenario, and improves the processing efficiency and use experience of the target table.

[0064] Figure 2Another flowchart of a table data processing method is provided in the embodiments of the present disclosure. The technical solution of the present embodiment is based on the above-mentioned embodiments. The sub-record editing operation includes a sub-record moving operation. The hierarchical description data corresponding to the edited sub-record is determined according to the sub-record moving operation, including: determining the edited sub-record according to the sub-record moving operation, and determining the first parent record to which the edited sub-record belongs before moving and the second parent record to which the edited sub-record belongs after moving; modifying the parent record in the first description data corresponding to the edited sub-record from the first parent record to the second parent record, deleting the description data corresponding to the edited sub-record in the second description data corresponding to the first parent record, and adding the description data corresponding to the edited sub-record in the second description data corresponding to the second parent record. The specific implementation can be seen from the description of the present embodiment. Among them, the same or similar technical features as the previous embodiments will not be described here. As shown in Figure 2 The method of the present embodiment can specifically include:

[0065] S210, in response to a data access request for a target table input by a client, displaying at least part of the records of the target table in a target interface of the client; wherein the record refers to a row of data in the target table.

[0066] S220, receiving a sub-record editing operation for the target table through the target interface; wherein the sub-record editing operation includes a sub-record moving operation.

[0067] The sub-record moving operation can be understood as an operation for moving or adjusting the position of at least one sub-record in the target table.

[0068] S230, determining the edited sub-record according to the sub-record moving operation, and determining the first parent record to which the edited sub-record belongs before moving and the second parent record to which the edited sub-record belongs after moving.

[0069] The first parent record can be understood as the parent record to which the edited sub-record belongs before moving. The second parent record can be understood as the parent record to which the edited sub-record belongs after moving.

[0070] Specifically, the edited sub-record is determined according to the sub-record moving operation, and the parent record to which the edited sub-record belongs before moving, i.e. the first parent record, is determined. The parent record to which the edited sub-record belongs after moving, i.e. the second parent record, is also determined.

[0071] In the embodiments of the present disclosure, the manner of determining the first parent record to which the edited child record belongs before moving can specifically be: obtaining the first description data of the edited child record before moving; and determining the first parent record to which the edited child record belongs before moving based on the first description data of the edited child record before moving. Similarly, the manner of determining the second parent record to which the edited child record belongs after moving can specifically be: obtaining the first description data of the edited child record after moving; and determining the second parent record to which the edited child record belongs after moving based on the first description data of the edited child record after moving.

[0072] In S240, the parent record in the first description data corresponding to the edited child record is modified from the first parent record to the second parent record, the description data corresponding to the edited child record in the second description data corresponding to the first parent record is deleted, and the description data corresponding to the edited child record is added in the second description data corresponding to the second parent record.

[0073] Specifically, the parent record in the first description data corresponding to the edited child record can be modified from the first parent record to the second parent record, so that the parent record in the first description data corresponding to the edited child record is the second parent record. After the modification, the description data corresponding to the edited child record in the second description data corresponding to the first parent record can be determined, the description data corresponding to the edited child record in the second description data corresponding to the first parent record can be deleted, and the description data corresponding to the edited child record can be written in the second description data corresponding to the second parent record.

[0074] In S250, the display data of the target table in the target interface is updated according to the modified first description data and the modified second description data.

[0075] The technical scheme of the embodiments of the present disclosure can realize the function of performing the child record moving operation on the child record in the target table by determining the edited child record according to the child record moving operation, determining the first parent record to which the edited child record belongs before moving and the second parent record to which the edited child record belongs after moving, modifying the parent record in the first description data corresponding to the edited child record from the first parent record to the second parent record, deleting the description data corresponding to the edited child record in the second description data corresponding to the first parent record, and adding the description data corresponding to the edited child record in the second description data corresponding to the second parent record.

[0076] Figure 3Another flowchart of a table data processing method provided by the embodiments of the present disclosure is shown. The technical solution of the embodiments is based on the above-mentioned embodiments, and optionally, the client stores table data corresponding to the data access request; the updating of the display data of the target table in the target interface according to the hierarchical description data corresponding to the edited sub-record based on the sub-record editing operation comprises: in the client, determining the hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation and the table data corresponding to the data access request stored in the client, and updating the display data of the target table in the target interface according to the hierarchical description data determined by the client. The specific implementation can be seen from the description of the embodiments. Among them, the same or similar technical features as the previous embodiments will not be described here. As shown in Figure 3 The method of the embodiments can specifically include:

[0077] S310, in response to a data access request for a target table input in a client, displaying at least part of the records of the target table in a target interface of the client; wherein the record refers to a row of data in the target table, and the client stores table data corresponding to the data access request.

[0078] S320, receiving a sub-record editing operation for the target table through the target interface, and in the client, determining hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation and the table data corresponding to the data access request stored in the client, and updating the display data of the target table in the target interface according to the hierarchical description data determined by the client.

[0079] Among them, the hierarchical description data can be used to describe the parent-child relationship data corresponding to the sub-records in the target table and the parent records containing the sub-records.

[0080] In the embodiment of the present disclosure, the client has stored table data corresponding to the data access request. Then, after receiving the sub-record editing operation on the target table through the target interface, the hierarchical description data corresponding to the sub-record before editing can be updated in the client according to the sub-record editing operation and the table data corresponding to the data access request stored in the client. Thus, the hierarchical description data corresponding to the sub-record after editing can be obtained, i.e., the hierarchical description data corresponding to the edited sub-record. Then, the display data of the target table in the target interface can be updated according to the hierarchical description data determined by the client. The processing in the embodiment of the present disclosure not only realizes the instant visibility of the modified target table in the client, but also ensures that the client operation is prioritized on the screen, i.e., the rendering result of the target table can be immediately seen in the client without waiting for the response of the server.

[0081] In the embodiment of the present disclosure, after the display data of the target table in the target interface is updated according to the hierarchical description data determined by the client, the method can further include: in the case that the client receives the hierarchical description data corresponding to the edited sub-record issued by the server, updating the stored hierarchical description data corresponding to the edited sub-record in the client according to the received hierarchical description data; and updating the display data of the target table in the target interface according to the updated hierarchical description data in the client.

[0082] Specifically, in the case that the client receives the hierarchical description data corresponding to the edited sub-record issued by the server, the stored hierarchical description data corresponding to the edited sub-record in the client can be updated according to the received hierarchical description data. Then, the display data of the target table in the target interface can be updated according to the updated hierarchical description data in the client. In the embodiment of the present disclosure, after receiving the sub-record editing operation on the target table through the target interface, the message of the editing operation can be uploaded to the server, so that the server updates the hierarchical description data corresponding to the edited sub-record based on the message, and issues the updated hierarchical description data corresponding to the edited sub-record to the client.

[0083] It should be noted that, in the embodiment of the present disclosure, in order to ensure consistency of the hierarchical description data in the client and the server, the hierarchical description data corresponding to the edited sub-record is determined in the client according to the sub-record editing operation and the table data corresponding to the data access request stored in the client, and does not need to be stored in the client. The hierarchical description data stored in the client can be the hierarchical description data corresponding to the edited sub-record issued by the server.

[0084] The technical scheme of the embodiments of the present disclosure realizes the instant visibility of the modified target table in the client, and reduces the waiting time of the client, by determining the hierarchical description data corresponding to the edited sub-record in the client according to the sub-record editing operation and the table data corresponding to the data access request stored in the client, and updating the display data of the target table in the target interface in the client according to the hierarchical description data determined by the client.

[0085] Figure 4 The flowchart of another table data processing method provided by the embodiments of the present disclosure is shown. The technical scheme of the present embodiment, on the basis of the above-mentioned embodiments, can optionally include adding a preset identifier to the hierarchical description data corresponding to the edited sub-record stored in the client, and updating the hierarchical description data corresponding to the edited sub-record stored in the client based on the preset identifier. The specific implementation can be seen from the description of the present embodiment. The technical features same as or similar to the foregoing embodiments are not described herein. As shown in the figure, the method of the present embodiment can specifically include: Figure 4

[0086] S410, in response to a data access request for a target table input in a client, displaying at least part of the records of the target table in a target interface of the client; wherein the record refers to a row of data in the target table.

[0087] S420, receiving a sub-record editing operation for the target table through the target interface, adding a preset identifier to the hierarchical description data corresponding to the edited sub-record stored in the client, and updating the hierarchical description data corresponding to the edited sub-record stored in the client based on the preset identifier.

[0088] ​The hierarchical description data is used to describe the parent-child relationship data corresponding to the sub-record and the parent record containing the sub-record in the target table. The preset identifier can be used to identify whether the hierarchical description data corresponding to the edited sub-record stored in the client is accurate. In the embodiment of the present disclosure, in the case that the hierarchical description data corresponding to the sub-record is added with the preset identifier, it can be determined that the hierarchical description data corresponding to the sub-record is inaccurate. Similarly, in the case that the hierarchical description data corresponding to the sub-record is not added with the preset identifier, it can be determined that the hierarchical description data corresponding to the sub-record is accurate. In the embodiment of the present disclosure, by adding the preset identifier to the hierarchical description data corresponding to the sub-record, the inaccurate record in the target table can be quickly located, so as to accurately update the inaccurate record. The form of the preset identifier can include numbers and / or letters.

[0089] Specifically, after receiving the sub-record editing operation for the target table through the target interface, the hierarchical description data corresponding to the edited sub-record stored in the client can be determined. Therefore, the preset identifier can be added to the hierarchical description data corresponding to the edited sub-record stored in the client. Then, the hierarchical description data corresponding to the edited sub-record stored in the client can be updated based on the preset identifier.

[0090] In the embodiment of the present disclosure, the updating of the hierarchical description data corresponding to the edited sub-record stored in the client based on the preset identifier can include: the sub-record editing operation can be first sent to the server, so that the server updates the hierarchical description data corresponding to the edited sub-record stored in the server based on the sub-record editing operation. Then, the hierarchical description data corresponding to the edited sub-record issued by the server can be received, and the hierarchical description data corresponding to the edited sub-record stored in the client is updated according to the received hierarchical description data and the preset identifier.

[0091] In the embodiment of the present disclosure, the updating of the hierarchical description data corresponding to the edited sub-record stored in the client according to the received hierarchical description data and the preset identifier can include: storing the received hierarchical description data into the client, and deleting the hierarchical description data added with the preset identifier; or, replacing the hierarchical description data added with the preset identifier with the received hierarchical description data.

[0092] S430, updating the display data of the target table in the target interface according to the hierarchical description data.

[0093] On the basis of the above embodiments, after receiving the hierarchical description data issued by the server, it can be determined whether the display data obtained based on the hierarchical description data issued by the server is consistent with the display data of the target table displayed by the client at the current moment. If not, the display data of the target table in the target interface is updated based on the hierarchical description data issued by the server. If yes, the operation of updating the display data of the target table in the target interface based on the hierarchical description data issued by the server is not needed to be performed, so that the hierarchical description data stored by the client can be updated without awareness.

[0094] The technical scheme of the embodiment of the present disclosure adds a preset identifier to the hierarchical description data corresponding to the edited sub-record stored in the client, and updates the hierarchical description data corresponding to the edited sub-record stored in the client based on the preset identifier, so that the hierarchical description data corresponding to the edited sub-record stored in the client can be updated more quickly and conveniently.

[0095] As an optional implementation of the embodiment of the present disclosure, the table processing method of the embodiment can include the following specific steps:

[0096] 1. After receiving the data access request for the target table input by the client, at least part of the records of the target table can be displayed in the target interface of the client. The record refers to a row of data in the target table. Referring to Figure 5 , the records in the target table include parent record 1, sub-record 1.1 subordinate to parent record 1, record 2, parent record 3, sub-record 3.1 subordinate to parent record 3, record 4, record 5, record 6, and record 7.

[0097] Specifically, as shown in Figure 6 , after receiving the table opening operation for the target table input by the operator in the client, the hierarchical information (hierarchical description data) of the target table in the client can be determined to obtain part of the record data of the target table from the server. After the client receives the part of the record data returned by the server, the hierarchical relationship of the part of the records can be calculated in the client, and the parent record and its sub-records in the target table can be cached in the client. After the calculation in the client is completed, the target table can be notified to re-render the record data. The process of re-rendering the target table can specifically include that the parent record can be obtained from the cache of the client first. Then, the sub-records subordinate to the parent record can be obtained from the cache of the client.

[0098] 2. The sub-record editing operation for the target table is received through the target interface, and the sub-record editing operation includes a sub-record moving operation. For example, Figure 7As shown, the target interface can receive a drag operation to drag a child record from the target table to the parent record 3.

[0099] 3. Based on the drag operation of dragging child record 1.1 into parent record 3 in the target table, it can be determined that the record being edited is child record 1.1, and that the parent record to which child record 1.1 belongs before the move is parent record 1 and the parent record to which it belongs after the move is parent record 3.

[0100] 4. After that, as Figure 8 As shown, in the client, child record 1.1 under parent record 1 can be deleted, and child record 1.1 can be added under parent record 3. Furthermore, the hierarchical information of parent record 1 and parent record 3 stored in the client can be locally marked as dirty. Then, based on the marked hierarchical information, the target table can be rendered selectively, allowing for priority rendering of the target table on the client side when the hierarchical information does not need to be sent from the server.

[0101] 5. After deleting child record 1.1 under parent record 1 and adding child record 1.1 under parent record 3 on the client, the child record drag operation of dragging child record 1.1 to parent record 3 for the target table can be sent to the server so that the server updates the hierarchical information corresponding to the child record drag operation and sends the updated hierarchical information to the client.

[0102] 6. After receiving the updated hierarchy information, the client can store the updated hierarchy information and determine whether the result of rendering the target table based on the updated hierarchy information is consistent with the result of the client rendering the target table. If yes, it can be determined that the client does not need to render the records of the client-displayed target table based on the updated hierarchy information. If no, the client-displayed target table can be rendered based on the updated hierarchy information to adjust the records of the client-displayed target table.

[0103] The technical solution of this disclosure addresses the technical problem of low table processing efficiency in existing table processing methods. It enables on-demand loading of table records and relatively quick and effective targeted updates of changed records, thereby improving table processing efficiency and user experience.

[0104] Figure 9 This is a schematic diagram of the structure of a tabular data processing device provided in an embodiment of the present disclosure, as shown below. Figure 9As shown, the apparatus comprises a data access request module 510 and a table data display module 520. The data access request module 510 is configured to display at least part of records of a target table in a target interface of a client in response to a data access request for the target table input by the client, wherein the record refers to a row of data in the target table. The table data display module 520 is configured to receive a sub-record editing operation for the target table through the target interface, determine hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation, and update display data of the target table in the target interface according to the hierarchical description data, wherein the hierarchical description data is used to describe parent-child relationship data corresponding to the sub-record in the target table and the parent record containing the sub-record.

[0105] The technical scheme of the embodiment of the present disclosure displays at least part of records of a target table in a target interface of a client in response to a data access request for the target table input by the client through the data access request module 510, wherein the record refers to a row of data in the target table, thereby realizing on-demand loading of records of the target table. The table data display module 520 receives a sub-record editing operation for the target table through the target interface, determines hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation, and updates display data of the target table in the target interface according to the hierarchical description data. In the technical scheme, the hierarchical description data describing parent-child relationship data corresponding to the sub-record in the target table and the parent record containing the sub-record is defined, thereby reducing the nesting level of records in the target table and simplifying the data structure of the target table. Then, the display data of the target table in the target interface can be updated relatively quickly and targetedly according to the hierarchical description data. The technical scheme of the embodiment of the present disclosure solves the technical problem of low table processing efficiency in the prior art, realizes on-demand loading of records of a table and relatively quick and effective targeted updating of records that have changed, does not need to load all data of the target table, supports quick editing and display of sub-records in the scenario of on-demand display of a table, and improves the processing efficiency and use experience of the target table.

[0106] On the basis of any optional technical scheme in the embodiment of the present disclosure, optionally, the hierarchical description data comprises first description data and second description data; the first description data is used to describe the subordinate relationship between the sub-record and the parent record to which the sub-record belongs; and the second description data is used to describe the subordinate relationship between the parent record and the sub-record contained by the parent record.

[0107] Optionally, the sub-record editing operation comprises a sub-record adding operation and / or a sub-record deleting operation; the table data display module 520 comprises a first hierarchical description data determination unit; the first hierarchical description data determination unit is configured to, in the case that the sub-record editing operation comprises a sub-record adding operation, add first description data corresponding to the added sub-record, and write the description data corresponding to the added sub-record into second description data of a parent record to which the added sub-record belongs; and / or, in the case that the sub-record editing operation comprises a sub-record deleting operation, delete first description data corresponding to the added sub-record, and delete the description data corresponding to the added sub-record from second description data of a parent record to which the added sub-record belongs.

[0108] Optionally, the sub-record editing operation comprises a sub-record moving operation. Further, the table data display module 520 can comprise a second hierarchical description data determination unit. The second hierarchical description data determination unit is configured to determine an edited sub-record according to the sub-record moving operation, and determine a first parent record to which the edited sub-record belongs before moving and a second parent record to which the edited sub-record belongs after moving; modify the parent record in first description data corresponding to the edited sub-record from the first parent record to the second parent record, delete the description data corresponding to the edited sub-record in second description data corresponding to the first parent record, and add the description data corresponding to the edited sub-record in second description data corresponding to the second parent record.

[0109] Optionally, the hierarchical description data is stored in the form of key-value pairs; the first description data takes the identifier of the sub-record as the key and the identifier of the parent record to which the sub-record belongs as the value; and the second description data takes the identifier of the parent record as the key and the identifier of the sub-record belonging to the parent record as the value.

[0110] Optionally, the table data corresponding to the data access request is stored in the client. Further, the table data display module 520 can be configured to determine, in the client, hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation and the table data corresponding to the data access request stored in the client, and update the display data of the target table in the target interface according to the hierarchical description data determined by the client.

[0111] On the basis of any optional technical solution in the embodiments of the present disclosure, the table data processing apparatus optionally further comprises a table data updating module. The table data updating module is configured to, in a case where the client receives hierarchical description data corresponding to the edited sub-record issued by the server after the display data of the target table in the target interface is updated according to the hierarchical description data determined by the client, update the stored hierarchical description data corresponding to the edited sub-record in the client according to the received hierarchical description data, and update the display data of the target table in the target interface according to the updated hierarchical description data in the client.

[0112] On the basis of any optional technical solution in the embodiments of the present disclosure, the table data display module 520 optionally comprises a hierarchical description data updating sub-module. The hierarchical description data updating sub-module is configured to add a preset identifier to the hierarchical description data corresponding to the edited sub-record stored in the client, and update the hierarchical description data corresponding to the edited sub-record stored in the client based on the preset identifier.

[0113] On the basis of any optional technical solution in the embodiments of the present disclosure, the hierarchical description data updating sub-module optionally comprises a server-side hierarchical updating unit and a client-side hierarchical updating unit. The server-side hierarchical updating unit is configured to send the sub-record editing operation to the server, so that the server updates the hierarchical description data corresponding to the edited sub-record stored in the server based on the sub-record editing operation. The client-side hierarchical updating unit is configured to receive the hierarchical description data corresponding to the edited sub-record issued by the server, and update the stored hierarchical description data corresponding to the edited sub-record in the client according to the received hierarchical description data and the preset identifier.

[0114] On the basis of any optional technical solution in the embodiments of the present disclosure, the data access request module 510 optionally comprises a client data caching unit and a target table display unit. The client data caching unit is configured to, in response to a data access request for a target table input in a client, acquire target data corresponding to a record requested to be accessed from table data of the target table stored in the server, and cache the target data in the client. The target table display unit is configured to display the target table in a target interface of the client according to the target data cached in the client.

[0115] The table data processing apparatus provided in the embodiments of the present disclosure can execute the table data processing method provided in any embodiment of the present disclosure, and has the corresponding function modules and beneficial effects of executing the table data processing method.

[0116] It is to be noted that the units and modules included in the above apparatus are only divided according to the functional logic, and are not limited to the above division, as long as the corresponding functions can be implemented; in addition, the specific names of each functional unit are only for the convenience of mutual differentiation, and do not serve to limit the protection scope of the embodiments of the present disclosure.

[0117] Reference will now be made to the drawings Figure 10 , which show a structural schematic diagram of an electronic device (e.g., a terminal device or a server) 600 suitable for use in implementing the embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure can include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (Personal Digital Assistant), a PAD (Tablet Personal Computer), a PMP (Portable Multimedia Player), a vehicle terminal (e.g., a car navigation terminal), and the like, as well as a fixed terminal such as a digital TV, a desktop computer, and the like. Figure 10 The electronic device shown is merely an example and should not impose any limitation on the functions and use range of the embodiments of the present disclosure.

[0118] As shown in Figure 10 , the electronic device 600 can include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601 that can perform various appropriate actions and processes according to programs stored in a read-only memory (ROM) 602 or loaded into a random access memory (RAM) 603 from a storage device 606. Various programs and data required for the operation of the electronic device 600 are also stored in the RAM 603. 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 the bus 604.

[0119] In general, the following devices can be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, and the like; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, and the like; a storage device 606 including, for example, a magnetic tape, a hard disk, and the like; and a communication device 609. The communication device 609 can allow the electronic device 600 to communicate wirelessly or by wire with other devices to exchange data. Although Figure 10 The electronic device 600 is shown with various devices, but it is understood that all of the devices shown are not required to be implemented or present. More or fewer devices can alternatively be implemented or present.

[0120] In particular, according to embodiments of the present disclosure, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for executing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network by the communication apparatus 609, or installed from the storage apparatus 606, or installed from the ROM 602. When the computer program is executed by the processing apparatus 601, the above-mentioned functions defined in the methods of the embodiments of the present disclosure are executed.

[0121] The names of the messages or information exchanged between the plurality of devices in the embodiments of the present disclosure are only for illustrative purposes, and are not intended to limit the scope of the messages or information.

[0122] The electronic device provided by the embodiments of the present disclosure and the table data processing method provided by the above-described embodiments belong to the same inventive concept, and the technical details not described in detail in the embodiments of the present disclosure can be referred to the above-described embodiments, and the present embodiments have the same beneficial effects as the above-described embodiments.

[0123] The embodiments of the present disclosure provide a computer storage medium, which stores a computer program, and the program is executed by a processor to implement the table data processing method provided by the above-described embodiments.

[0124] It should be noted that the computer readable medium of the present disclosure described above can be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination of the above. More specific examples of computer readable storage media can 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 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, the computer readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or apparatus. In the present disclosure, the computer readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer readable program code. Such a propagated data signal can take many forms, including but not limited to an electromagnetic signal, an optical signal or any suitable combination of the above. The computer readable signal medium can also be any computer readable medium other than the computer readable storage medium, which can send, propagate or transmit a program for use by or in conjunction with an instruction execution system, device or apparatus. The program code contained in the computer readable medium can be transmitted by any suitable medium, including but not limited to a wire, a cable, an RF (radio frequency) or the like, or any suitable combination of the above.

[0125] According to one or more embodiments of the present disclosure, example one provides a table data processing method, comprising: in response to a data access request for a target table input by a client, displaying at least part of the records of the target table in a target interface of the client; wherein the record refers to a row of data in the target table; receiving a sub-record editing operation for the target table through the target interface, determining hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation, and updating the display data of the target table in the target interface according to the hierarchical description data; wherein the hierarchical description data is used to describe the parent-child relationship data corresponding to the sub-record and the parent record containing the sub-record in the target table.

[0126] According to one or more embodiments of the present disclosure, Example Two provides the method of Example One, further comprising: optionally, the hierarchical description data comprises first description data and second description data; the first description data is used to describe the dependency relationship between the sub-record and the parent record to which the sub-record belongs; and the second description data is used to describe the dependency relationship between the parent record and the sub-record contained in the parent record.

[0127] According to one or more embodiments of the present disclosure, Example Three provides the method of Example One, further comprising: optionally, the sub-record editing operation comprises a sub-record adding operation and / or a sub-record deleting operation; and the determining the hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation comprises: in the case that the sub-record editing operation comprises a sub-record adding operation, adding the first description data corresponding to the added sub-record, and writing the description data corresponding to the added sub-record into the second description data of the parent record to which the added sub-record belongs; and / or in the case that the sub-record editing operation comprises a sub-record deleting operation, deleting the first description data corresponding to the added sub-record, and deleting the description data corresponding to the added sub-record from the second description data of the parent record to which the added sub-record belongs.

[0128] According to one or more embodiments of the present disclosure, Example Four provides the method of Example One, further comprising: optionally, the sub-record editing operation comprises a sub-record moving operation; and the determining the hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation comprises: determining the edited sub-record according to the sub-record moving operation, and determining the first parent record to which the edited sub-record belongs before moving and the second parent record to which the edited sub-record belongs after moving; modifying the parent record in the first description data corresponding to the edited sub-record from the first parent record to the second parent record, deleting the description data corresponding to the edited sub-record in the second description data corresponding to the first parent record, and adding the description data corresponding to the edited sub-record in the second description data corresponding to the second parent record.

[0129] According to one or more embodiments of the present disclosure, Example Five provides the method of Example One, further comprising: optionally, the hierarchical description data is stored in the form of key-value pairs; the first description data takes the identification of the sub-record as the key and the identification of the parent record to which the sub-record belongs as the value; and the second description data takes the identification of the parent record as the key and the identification of the sub-record subordinate to the parent record as the value.

[0130] According to one or more embodiments of the present disclosure, Example Six provides the method of Example One, further including: optionally, the client stores table data corresponding to the data access request; and the updating, according to the sub-record editing operation, of the hierarchical description data corresponding to the edited sub-record, and the updating, according to the hierarchical description data, of the display data of the target table in the target interface, include: in the client, determining, according to the sub-record editing operation and the table data corresponding to the data access request stored in the client, the hierarchical description data corresponding to the edited sub-record, and updating, according to the hierarchical description data determined by the client, the display data of the target table in the target interface.

[0131] According to one or more embodiments of the present disclosure, Example Seven provides the method of Example One, further including: optionally, after the updating, according to the hierarchical description data determined by the client, of the display data of the target table in the target interface, further including: in a case where the client receives hierarchical description data corresponding to the edited sub-record issued by a server, updating, according to the received hierarchical description data, the stored hierarchical description data corresponding to the edited sub-record in the client; and updating, according to the updated hierarchical description data in the client, the display data of the target table in the target interface.

[0132] According to one or more embodiments of the present disclosure, Example Eight provides the method of Example One, further including: optionally, the determining, according to the sub-record editing operation, of the hierarchical description data corresponding to the edited sub-record, includes: adding a preset identifier to the hierarchical description data corresponding to the edited sub-record stored in the client, and updating the hierarchical description data corresponding to the edited sub-record stored in the client based on the preset identifier.

[0133] According to one or more embodiments of the present disclosure, Example Nine provides the method of Example One, further including: optionally, the updating, based on the preset identifier, of the hierarchical description data corresponding to the edited sub-record stored in the client, includes: sending the sub-record editing operation to a server, so that the server updates the hierarchical description data corresponding to the edited sub-record stored in the server based on the sub-record editing operation; receiving hierarchical description data corresponding to the edited sub-record issued by the server, and updating, according to the received hierarchical description data and the preset identifier, the stored hierarchical description data corresponding to the edited sub-record in the client.

[0134] According to one or more embodiments of the present disclosure, Example Ten provides the method of Example One, further comprising: optionally, in response to the data access request for the target table input at the client, displaying at least partial records of the target table in a target interface of the client, including: in response to the data access request for the target table input at the client, obtaining target data corresponding to the requested records from the table data of the target table stored at the server, and caching the target data in the client; and displaying the target table in the target interface of the client according to the target data cached in the client.

[0135] According to one or more embodiments of the present disclosure, Example Eleven provides a table data processing apparatus, comprising: a data access request module configured to display at least partial records of a target table in a target interface of a client in response to a data access request for the target table input at the client; wherein the records refer to one row of data in the target table; and a table data display module configured to receive a sub-record editing operation for the target table through the target interface, determine hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation, and update display data of the target table in the target interface according to the hierarchical description data; wherein the hierarchical description data is used to describe parent-child relationship data corresponding to the sub-record in the target table and the parent record containing the sub-record.

[0136] In some embodiments, the client and the server can communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol), and can be interconnected with digital data communication (e.g., a communication network) of any form or medium. Examples of the communication network include a local area network (“LAN”), a wide area network (“WAN”), an internetwork (e.g., the Internet), and an end-to-end network (e.g., an ad hoc end-to-end network), as well as any currently known or future developed network.

[0137] The above computer readable medium can be included in the above electronic device; or can exist separately without being assembled into the electronic device.

[0138] The computer readable medium described above carries one or more programs, when the one or more programs are executed by the electronic device, cause the electronic device to: in response to a data access request for a target table input by a client, display at least part of records of the target table in a target interface of the client; wherein the record refers to a row of data in the target table; receive a sub-record editing operation for the target table through the target interface, determine hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation, and update display data of the target table in the target interface according to the hierarchical description data; wherein the hierarchical description data is used to describe parent-child relationship data corresponding to the sub-record in the target table and the parent record containing the sub-record.

[0139] Computer program code for carrying out operations of the present disclosure can be written in any one or more programming languages, including object oriented programming languages such as Java, Smalltalk, C++ or the like, conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can 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 latter scenario, the remote computer can 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 the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0140] The flow diagrams and the block diagrams in the drawings are illustrations of architectures, functionalities, and operations of possible implementations of systems, methods, and computer program products according to various embodiments of present disclosure. In this regard, each block in the flow diagrams or block diagrams can represent a module, a segment, or a 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 blocks can 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

[0141] The modules described in the embodiments of the present disclosure can be implemented in the form of software, or can be implemented in the form of hardware. In some cases, the names of the modules do not constitute a limitation on the modules themselves. For example, the data access request module can also be described as a module for displaying at least part of the records of the target table in the target interface of the client.

[0142] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that can be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system on a chips (SOCs), complex programmable logic devices (CPLDs), etc.

[0143] In the context of the present disclosure, a machine-readable medium can be a tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can 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 the machine-readable storage medium will include one or more lines of electrical connections, portable computer disks, hard disk drives, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), optical fibers, portable compact disc read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0144] The above description is merely the preferred embodiments of the present disclosure and the explanation of the principles of the applied technology. It should be understood by those skilled in the art that the disclosed scope of the present disclosure is not limited to the technical solutions formed by the specific combinations of the above technical features, and also covers other technical solutions formed by any combinations of the above technical features or equivalent features without departing from the disclosed concept. For example, the above features can be replaced with the technical features disclosed in the present disclosure (but not limited to) having similar functions to form technical solutions.

[0145] Moreover, while operations are depicted in a particular order, this should not be understood as requiring such an order nor infringing on the scope of the disclosure. Certain of the operations described in the discussion are combinable into a single operation, and certain operations can be separated into several operations. In some embodiments, the operations described in the discussion can be performed in an order different than presented in the discussion. In some embodiments, the operations described in the discussion can be performed concurrently. Also, while several specific implementation details are discussed in the discussion, these should not be interpreted as limiting the scope of the disclosure. Rather, certain features described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination.

[0146] 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 disclosed as example forms of implementing the claims.

Claims

1. A tabular data processing method, characterized by, The method comprises: in response to a data access request for a target table input by a client, displaying at least part of records of the target table in a target interface of the client; wherein the records refer to a row of data in the target table; receiving a sub-record editing operation for the target table through the target interface, determining hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation, and updating display data of the target table in the target interface according to the hierarchical description data; wherein the hierarchical description data is used to describe parent-child relationship data corresponding to the sub-record and the parent record containing the sub-record in the target table.

2. The tabular data processing method of claim 1, wherein, The hierarchical description data comprises first description data and second description data; the first description data is used to describe the subordinate relationship between the sub-record and the parent record to which the sub-record belongs; and the second description data is used to describe the subordinate relationship between the parent record and the sub-record contained by the parent record.

3. The tabular data processing method according to claim 2, characterized in that, The sub-record editing operation comprises a sub-record adding operation and / or a sub-record deleting operation; and the determination of the hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation comprises: in the case where the sub-record editing operation comprises a sub-record adding operation, adding first description data corresponding to the added sub-record, and writing description data corresponding to the added sub-record into second description data of the parent record to which the added sub-record belongs; and / or in the case where the sub-record editing operation comprises a sub-record deleting operation, deleting first description data corresponding to the added sub-record, and deleting description data corresponding to the added sub-record from second description data of the parent record to which the added sub-record belongs.

4. The tabular data processing method of claim 2, wherein, The sub-record editing operation comprises a sub-record moving operation; and the determination of the hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation comprises: determining the edited sub-record according to the sub-record moving operation, and determining a first parent record to which the edited sub-record belongs before moving and a second parent record to which the edited sub-record belongs after moving; modifying the parent record in the first description data corresponding to the edited sub-record from the first parent record to the second parent record, deleting description data corresponding to the edited sub-record in the second description data corresponding to the first parent record, and adding description data corresponding to the edited sub-record in the second description data corresponding to the second parent record.

5. The tabular data processing method of claim 2, wherein, The hierarchical description data is stored in the form of key-value pairs; the first description data takes the identification of the sub-record as the key and the identification of the parent record to which the sub-record belongs as the value; and the second description data takes the identification of the parent record as the key and the identification of the sub-record subordinate to the parent record as the value.

6. The tabular data processing method of claim 1, wherein, The client stores table data corresponding to the data access request; and the determination of the hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation and the updating of the display data of the target table in the target interface according to the hierarchical description data comprise: In the client, hierarchical description data corresponding to the edited sub-record is determined according to the sub-record editing operation and table data corresponding to the data access request stored in the client, and display data of the target table in the target interface is updated according to the hierarchical description data determined in the client.

7. The tabular data processing method according to claim 6, characterized in that, After the display data of the target table in the target interface is updated according to the hierarchical description data determined in the client, the method further comprises: In the case that the client receives hierarchical description data corresponding to the edited sub-record issued by the server, the stored hierarchical description data corresponding to the edited sub-record in the client is updated according to the received hierarchical description data; The display data of the target table in the target interface is updated according to the updated hierarchical description data in the client.

8. The tabular data processing method of claim 1, wherein, The hierarchical description data corresponding to the edited sub-record is determined according to the sub-record editing operation, comprising: A preset identifier is added to the stored hierarchical description data corresponding to the edited sub-record in the client, and the stored hierarchical description data corresponding to the edited sub-record in the client is updated based on the preset identifier.

9. The tabular data processing method according to claim 8, characterized in that, The hierarchical description data corresponding to the edited sub-record is updated based on the preset identifier, comprising: The sub-record editing operation is sent to the server, so that the server updates the hierarchical description data corresponding to the edited sub-record stored in the server based on the sub-record editing operation; The hierarchical description data corresponding to the edited sub-record issued by the server is received, and the stored hierarchical description data corresponding to the edited sub-record in the client is updated according to the received hierarchical description data and the preset identifier.

10. The tabular data processing method of claim 1, wherein, The display of at least part of the records of the target table in the target interface of the client in response to the data access request for the target table input in the client, comprising: In response to the data access request for the target table input in the client, target data corresponding to the record requested to be accessed is obtained from the table data of the target table stored in the server, and the target data is cached in the client; The target table is displayed in the target interface of the client according to the target data cached in the client.

11. A tabular data processing apparatus, characterized by comprising: Comprise: A data access request module is configured to display at least part of the records of the target table in the target interface of the client in response to the data access request for the target table input in the client; wherein the record refers to a row of data in the target table; A table data display module is configured to receive a sub-record editing operation for the target table through the target interface, determine hierarchical description data corresponding to the edited sub-record according to the sub-record editing operation, and update display data of the target table in the target interface according to the hierarchical description data; wherein the hierarchical description data is used to describe parent-child relationship data corresponding to the sub-record and the parent record containing the sub-record in the target table.

12. An electronic device, comprising: The electronic device comprises: One or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, cause the one or more processors to carry out the table data processing method of any one of claims 1-10.

13. A storage medium containing computer-executable instructions, wherein: the computer executable instructions, when executed by a computer processor, perform the table data processing method of any one of claims 1-10.

14. A computer program product comprising a computer program, characterized in that, the computer program, when executed by a processor, carries out the table data processing method of any one of claims 1-10.

Images