Table data processing methods, apparatus, equipment, media, and products

Abstract

We provide table data processing methods, apparatus, equipment, media, and products. [Solution] The method includes the step of displaying at least a portion of the records in the target table on the client side's target interface in response to a data access request to the target table entered on the client side. A record refers to a single row of data in the target table. The method also includes the step of receiving a sub-record editing operation on the target table via the target interface, determining hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and updating the display data in the target interface of the target table based on the hierarchical description data. The hierarchical description data is used to describe parent-child relationship data corresponding to sub-records and parent records containing sub-records in the target table.

Description

Technical Field

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

Background Art

[0002] With the rapid development of information technology, tables have become an indispensable part in all industries as a means to hold a large amount of information in an intuitive and clear manner. Users can store, manage, and check data records through tables.

[0003] Regarding the verification of data records in a table, in the table data processing method in the related art, all data records are loaded in a batch in response to an access request to the table data, and all data records are often reloaded when the data records are changed. However, when the amount of data is very large (for example, at the million-row level), loading all data in a batch will impose a huge memory and computational load on the client side, resulting in low table processing efficiency and potentially compromising the user experience.

Summary of the Invention

[0004] Embodiments of the present disclosure provide a table data processing method, apparatus, device, medium, and product that can display table records as needed and improve the processing efficiency and usage experience of the table by quickly and effectively narrowing down and updating the changed records.

[0005] According to a first aspect, an embodiment of the present disclosure includes a step of displaying at least a part of the records of the target table on the target interface on the client side in response to a data access request to the target table input on the client side, wherein the record refers to one row of data in the target table. A table data processing method is provided, comprising the steps of: receiving a sub-record editing operation on the target table via the target interface; determining hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation; and updating the display data of the target table in the target interface based on the hierarchical description data, wherein the hierarchical description data is used to describe parent-child relationship data corresponding to sub-records and parent records containing sub-records in the target table.

[0006] According to a second aspect, an embodiment of the present disclosure is a data access request module that, in response to a data access request to a target table entered on the client side, displays records of at least a portion of the target table in the client-side target interface, wherein the records refer to a data access request module that points to a single row of data in the target table. A table data processing device is further provided, which includes a table data display module that receives a sub-record editing operation on the target table via the target interface, determines hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and updates the display data of the target table in the target interface based on the hierarchical description data, wherein the hierarchical description data is used to describe parent-child relationship data corresponding to sub-records and parent records containing sub-records in the target table.

[0007] According to a third aspect, the embodiments of the present disclosure include one or more processors, A storage device for storing one or more programs, including, The present invention further provides an electronic device that, when the one or more programs described above are executed by the one or more processors, causes the one or more processors to execute the table data processing method described in any one of the embodiments of this disclosure.

[0008] According to a fourth aspect, embodiments of the present disclosure further provide a storage medium including computer-executable instructions, wherein when the computer-executable instructions are executed by a computer processor, the storage medium executes a table data processing method described in any one of the embodiments of the present disclosure.

[0009] According to a fifth aspect, embodiments of the present disclosure further provide a computer program product including a computer program, the computer program including a computer program that performs a table data processing method described in any one of the embodiments of the present disclosure when the computer program is executed by a processor.

[0010] The technical solution of the embodiment of this disclosure displays at least a portion of the records of the target table in the client-side target interface in response to a data access request to the target table entered on the client side, and the record refers to a single row of data in the target table, thereby enabling the display of records in the target table as needed. The target interface receives a sub-record editing operation for the target table and determines hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation. This technical solution simplifies the data structure of the target table by defining hierarchical description data that describes parent-child relationship data corresponding to sub-records and parent records containing sub-records in the target table. Subsequently, the data displayed in the target interface of the target table can be quickly filtered and updated based on the hierarchical description data. The technical solutions of the embodiments of this disclosure solve the technical problem of low table processing efficiency that exists in table processing methods in related technologies. Without loading all the data in the target table, it is possible to display the records of the table as needed, quickly and effectively filter and update the changed records, and support the rapid editing and display of sub-records when displaying the table as needed, thereby improving the processing efficiency and user experience of the target table. [Brief explanation of the drawing]

[0011] The above and other features, advantages, and aspects of each embodiment of this disclosure will become even clearer when viewed in conjunction with the drawings. Throughout the drawings, identical or similar reference numerals represent identical or similar elements. The drawings are illustrative and should be understood to mean that the actual objects and elements are not necessarily depicted in proportion. [Figure 1] Figure 1 is a schematic flowchart of a table data processing method according to an embodiment of the present disclosure. [Figure 2] Figure 2 is a schematic flowchart of another table data processing method according to an embodiment of the present disclosure. [Figure 3] Figure 3 is a schematic flowchart of another table data processing method according to an embodiment of the present disclosure. [Figure 4] Figure 4 is a schematic flowchart of another table data processing method according to an embodiment of the present disclosure. [Figure 5] Figure 5 shows an example of a record display interface applied to a table data processing method according to an embodiment of the present disclosure. [Figure 6] Figure 6 is a schematic time series diagram of a table data processing method according to an embodiment of the present disclosure, in which table data is loaded as needed in response to the present disclosure. [Figure 7] Figure 7 shows an example of a recording operation interface applied to a table data processing method according to an embodiment of the present disclosure. [Figure 8] Figure 8 is a schematic diagram of the time series in response to a sub-record editing operation, as applied to the table data processing method of the embodiment of the present disclosure. [Figure 9] Figure 9 is a schematic diagram of the structure of a table data processing device according to an embodiment of the present disclosure. [Figure 10] Figure 10 is a schematic diagram of the structure of an electronic device for realizing an embodiment of the present disclosure. [Modes for carrying out the invention]

[0012] The embodiments of this disclosure will be described in more detail below with reference to the drawings. Although several embodiments of this disclosure are shown in the drawings, this disclosure can be realized in various forms and should not be construed as being limited to the embodiments described herein. Rather, these embodiments should be understood as being provided for a more thorough and complete understanding of this disclosure. The drawings and embodiments of this disclosure are for illustrative purposes only and should not be used to limit the scope of protection of this disclosure.

[0013] It should be understood that each step described in the embodiments according to the method of the present disclosure may be executed in a different order and / or executed in parallel. Also, the method embodiments may include additional steps and / or omit the execution of the illustrated steps. The scope of the present disclosure is not limited in this regard.

[0014] As used herein, the term "comprising" and its variations are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "an embodiment" means "at least one embodiment", the term "another embodiment" means "at least one another embodiment", and the term "some embodiments" means "at least some embodiments". Related definitions of other terms are shown in the following description.

[0015] Note that the concepts such as "first", "second", etc. mentioned in the present disclosure are for distinguishing different devices, modules or units, and are not for limiting the order or interdependent relationship of the functions executed by these devices, modules or units.

[0016] Note that the modifiers "one" and "plural" in the present disclosure are exemplary rather than restrictive, and those skilled in the art should understand them as "one or plural" unless otherwise specified.

[0017] The names of messages or information that interact between multiple devices in the embodiments of the present disclosure are not intended to limit the scope of these messages or information, and are only used for the purpose of explanation.

[0018] Before using the technical solutions disclosed in each embodiment of the present disclosure, it can be understood that the types, scope of use, usage scenarios, etc. of personal information related to the present disclosure should be notified to users in an appropriate manner in accordance with relevant laws and regulations, and the permission of the users should be obtained.

[0019] For example, in response to receiving an active request from a user, presentation information is transmitted to the user so as to explicitly present to the user that obtaining and using the user's personal information is required for the requested operation. Thereby, based on the presentation information, the user can independently select whether to provide personal information to software or hardware such as an electronic device, an application, a server, or a storage medium that executes the operations of the technical solution of the present disclosure.

[0020] As a selectable but non-limiting implementation form, the method of transmitting presentation information to the user in response to receiving an active request from the user may be, for example, in the form of a pop-up window, and the presentation information can be shown in text within the pop-up window. Further, the pop-up window may further include a selection control for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0021] It should be understood that the above process of notification and obtaining user consent is merely exemplary and does not limit the embodiments of the present disclosure, and other methods that comply with relevant laws and regulations can also be applied to the embodiments of the present disclosure.

[0022] It is understood that the data related to the technical solution (including but not limited to the data itself, data acquisition, or data use) should comply with the requirements of corresponding laws and regulations and related provisions.

[0023] FIG. 1 is a flowchart schematic diagram of a table data processing method provided by an embodiment of the present disclosure. The embodiment of the present disclosure is applicable to a scenario of processing table data. The method may be executed by a table data processing device, and the device may be implemented in the form of software and / or hardware. Optionally, it may be implemented by an electronic device, and the electronic device may be a mobile terminal, a PC side, a server, or the like. As shown in FIG. 1, the method of this embodiment may specifically include the following steps.

[0024] S110: In response to a data access request to the target table entered by the client, the client-side target interface displays records of at least a portion of the target table, where the record refers to a single row of data in the target table.

[0025] Here, the target table may be understood as a table from which data access is required, and may be used to store, manage, and display data records. The data in the target table may be represented in the form of rows. A record may refer to the data recorded in one row in the target table. In practical application, a target table generally contains multiple rows of data, that is, a target table generally contains multiple records. In embodiments of this disclosure, parent-child relationships may exist between records in the target table. A target table may contain one or more parent records and one or more sub-records dependent on the parent records. The number of sub-records dependent on different parent records in a target table may be the same or different.

[0026] In embodiments of the present disclosure, a data access request may be understood as a request to access data in a target table, and may be used to display at least a portion of the records in the target table on a client-side target interface. In embodiments of the present disclosure, a target interface may be understood as an interface for displaying at least a portion of the records in the target table. In embodiments of the present disclosure, the target interface may be arranged adaptively by employing a responsive arrangement to fit different resolution display screens, or it may be arranged at a predetermined interface size, where the predetermined interface size may be set as required in practice and is not specifically limited herein. Optionally, the predetermined interface size includes a predetermined interface length and / or a predetermined interface width.

[0027] In the embodiments of this disclosure, the application of a data access request to the target table entered on the client side may occur even if the record of the target table is not displayed in the client-side target interface, or it may occur even if the record of the target table is displayed in the client-side target interface.

[0028] In one optional embodiment of the embodiments of this disclosure, responding to a data access request to a target table entered on the client side may specifically mean responding to a data confirmation operation for the target table entered on the client side when the record for the target table is not displayed in the client-side target interface. Based on this, after receiving the data confirmation operation for the target table entered on the client side, the default load record for the target table can be determined. Furthermore, the default load record can be displayed in the client-side target interface. Here, the default load record may be understood as the default record that should be displayed when the target table is accessed for the first time within a predetermined time. For example, the default load record may be the record for the target table that is displayed in the target interface when the target table was most recently closed.

[0029] In embodiments of this disclosure, determining the default records for at least some of the target table may be determined based on a predetermined record identifier and a predetermined number of records to display in the target table, where the predetermined record identifier may be used to distinguish data content in different tables of the target interface. For example, the predetermined record identifier may be the first record displayed in the target table. In some cases, the predetermined record identifier is called a column title and is used to identify the data content of the column data in which it is located, or to distinguish data content in different columns. The predetermined record identifier may be set as needed and is not specifically set here. The predetermined number of records to display may be set as needed and is not specifically limited here, for example, 20, 30, or 50. The predetermined number of records to display is understood not to exceed the upper limit of the number of records that can be displayed by the target interface.

[0030] In another optional embodiment of the embodiments of this disclosure, responding to a data access request to a target table entered on the client side may specifically mean responding to a scroll operation on the target interface displaying the record of the target table when the record of the target table is displayed on the client-side target interface. Based on this, after receiving a scroll operation on the target interface displaying the record of the target table, at least a portion of the record of the target table displayed on the client-side target interface can be updated.

[0031] In the embodiments of this disclosure, the storage location of the records in the target table may be on the client side or on the service side. There may be multiple methods for displaying at least a portion of the records in the target table in the client-side target interface.

[0032] In one optional embodiment of the embodiments of the present disclosure, if the storage location of the records in the target table is on the client side, after receiving a data access request to the target table entered on the client side, at least a portion of the records in the target table may be read from the client side and the at least portion of the records may be displayed on the target interface on the client side.

[0033] In another optional embodiment of the embodiments of the present disclosure, when the storage location of the records in the target table is on the service side, displaying at least a portion of the records in the target table on the client side target interface in response to a data access request to the target table entered on the client side may include, in response to a data access request to the target table entered on the client side, retrieving the target data corresponding to the record for which access is requested from the table data of the target table stored on the service side, caching the target data on the client side, and displaying the target table on the client side target interface based on the target data cached on the client side.

[0034] Here, target data may be understood as table data corresponding to a data access request to a target table stored on the service side. Specifically, after receiving a data access request to a target table entered on the client side, the data access request may be sent to the service side. Furthermore, target data corresponding to the record for which access is requested may be obtained from the table data of the target table stored on the service side. After obtaining the target data on the service side, the target data may be stored in the client side's cache memory. Furthermore, based on the target data cached on the client side, the target table may be displayed in the client side's target interface. Typically, target data is data displayed in the target interface, that is, table data that needs to be rendered in the view layer.

[0035] In addition to the above embodiment, in order to facilitate subsequent access to the target table by the client, the target data distributed by the service may be received by the client and then stored in a predetermined storage location in the target table. Based on this, in order to reduce the occupation of the client's storage space, when the target data of the target table distributed by the service is received by the client, the reception time of the target data may be marked. If no data access request to the target table is entered by the client within a predetermined time period from the reception time, a deletion process may be performed on the target data stored on the client.

[0036] S120: The target interface receives a sub-record editing operation for the target table, determines hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, updates the display data of the target table in the target interface based on the hierarchical description data, and uses the hierarchical description data to describe parent-child relationship data corresponding to the sub-records and parent records containing the sub-records in the target table.

[0037] Here, a sub-record editing operation may be understood as an operation to edit a sub-record in the target table. In embodiments of the present disclosure, the sub-record editing operation may include a sub-record addition operation and / or a sub-record deletion operation. A sub-record addition operation may be understood as an operation to add at least one sub-record to the target table. A sub-record deletion operation may be understood as an operation to delete at least one sub-record from the target table. In embodiments of the present disclosure, the hierarchical description data may be used to describe parent-child relationship data corresponding to the sub-records in the target table and the parent records containing the sub-records. That is, the hierarchical description data may be used to determine the parent records to which a sub-record belongs and all sub-records contained within the parent records.

[0038] In the embodiments of this disclosure, the storage location of the hierarchical description data may be on the client side or on the service side. There may be multiple methods for determining the hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation.

[0039] In one optional embodiment of the embodiments of this disclosure, if the storage location of the hierarchical description data is on the client side, the sub-record to be edited may be determined based on the sub-record editing operation. Furthermore, the hierarchical description data corresponding to the sub-record to be edited may be updated on the client side based on the sub-record to be edited. This allows the hierarchical description data corresponding to the sub-record to be edited to be read from the client side.

[0040] In another optional embodiment of the embodiments of this disclosure, if the storage location of the hierarchical description data is on the service side, the sub-record to be edited may be determined based on the sub-record editing operation. After determining the sub-record to be edited, the sub-record to be edited may be sent to the service side so that the service side updates the hierarchical description data corresponding to the sub-record to be edited, and the updated hierarchical description data corresponding to the sub-record to be edited may be delivered to the client side so that the client side can acquire the hierarchical description data.

[0041] In embodiments of this disclosure, updating the display data in the target interface of the target table based on the hierarchical description data may specifically include determining, based on the hierarchical description data, the parent record to which the sub-record to be edited belongs and all sub-records contained within the parent record. This allows updating the display data in the target interface of the target table based on the parent record to which the sub-record to be edited belongs and all sub-records contained within the parent record.

[0042] In the embodiments disclosed herein, the hierarchical description data may include first description data and second description data. Here, the first description data may be used to describe the dependency relationship between the sub-record and the parent record to which the sub-record belongs. The second description data may be used to describe the dependency relationship between the parent record and the sub-records contained within the parent record. In the embodiments disclosed herein, the advantage of using first and second description data as hierarchical description data is that when a sub-record is added to or deleted from a parent record in a target table displayed in the target interface, only the records that have changed in the target table can be loaded without having to reload all the records in the target table. Furthermore, it is possible to quickly and effectively load and display records in the target table in the target interface as needed.

[0043] In embodiments of this disclosure, the hierarchical description data is stored in the form of key-value pairs (Maps). Here, the first description data may have 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. The second description data may have the identifier of the parent record as the key and the identifier of the sub-record to which the parent record belongs as the value. In embodiments of this disclosure, two Maps are used, one of which is used to store the mapping from sub-records to parent records, i.e., the first description data, and the other is used to store the mapping from parent records to sub-records, i.e., the second description data, thereby enabling the storage of flattened data recorded in the target table, reducing the nested hierarchy of data, making data access more direct, allowing for more flexible addition, deletion, and modification of records, and by using Maps, it becomes easier to update the parent-child relationships between parent records and sub-records in the target table without having to rebuild the entire data structure. Furthermore, repeated storage of data is avoided, making it easier to understand and maintain.

[0044] In addition to the above embodiments, determining the hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation may specifically include, when the sub-record editing operation includes a sub-record addition operation, adding a first description data corresponding to the sub-record to be added and writing the description data corresponding to the added sub-record to the second description data of the parent record to which the added sub-record belongs, and / or, when the sub-record editing operation includes a sub-record deletion 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. By adopting this technical solution, deletion of sub-records can be easily and quickly implemented, the processing speed of the target table can be improved, and the update speed of the view after the sub-record has been deleted can be improved.

[0045] In addition to the embodiments described above, embodiments of this disclosure may further include a current client and a cooperating client that cooperates with the current client. In embodiments of this disclosure, the number of cooperating client may be one, two, or more. The current client and the cooperating client each establish a data communication link with the service based on a network communication protocol (e.g., WebSocket). After the cooperating client receives a sub-record editing operation on the target table, the cooperating client may transmit the sub-record editing operation to the service so that the service broadcasts a message of the cooperating client's sub-record editing operation on the target table to the client that has a communication link with the service. After the current client obtains the message from the data communication link, it may obtain the sub-record editing operation on the target table by the cooperating client based on the message. Thus, by performing a sub-record editing operation on the target table by the cooperating client on the target table of the current client, a function can be realized in which multiple clients cooperate to process sub-record editing operations on the target table.

[0046] According to the technical solution of the embodiment of this disclosure, in response to a data access request to the target table entered on the client side, at least a portion of the records of the target table are displayed on the client-side target interface, and the record refers to a single row of data in the target table, so that the records of the target table are displayed as needed. A sub-record editing operation on the target table is received by the target interface, and based on the sub-record editing operation, hierarchical description data corresponding to the sub-record to be edited is determined. In this technical solution, by defining hierarchical description data that describes parent-child relationship data corresponding to sub-records and parent records containing sub-records in the target table, the nesting hierarchy of records in the target table is reduced and the data structure of the target table is simplified. Based on the hierarchical description data, the data displayed on the target interface of the target table can be updated quickly and selectively. The technical solutions of the embodiments of this disclosure solve the technical problem of low table processing efficiency that exists in conventional table processing, load the records of a table as needed without loading all the data of the target table, and enable the rapid and effective filtering and updating of changed records. Furthermore, when displaying the table as needed, it supports the rapid editing and display of sub-records, thereby improving the processing efficiency and user experience for the target table.

[0047] Figure 2 is a schematic flowchart of another table data processing method according to an embodiment of the present disclosure. According to the technical solution of this embodiment, in addition to the above embodiment, the sub-record editing operation includes a sub-record movement operation, and determining the hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation includes determining the sub-record to be edited based on the sub-record movement operation, determining the first parent record to which the sub-record to be edited belongs before the movement and the second parent record to which it belongs after the movement, changing the parent record in the first description data corresponding to the sub-record to be edited from the first parent record to the second parent record, deleting the description data corresponding to the sub-record to be edited from the second description data corresponding to the first parent record, and adding the description data corresponding to the sub-record to be edited to the second description data corresponding to the second parent record. For specific embodiments, refer to the description of this embodiment. Technical features that are the same as or similar to those of the above embodiment will not be described. As shown in Figure 2, the method of this embodiment may specifically include the following steps.

[0048] S210: In response to a data access request to the target table entered by the client, the client-side target interface displays records of at least a portion of the target table, where the record refers to a single row of data in the target table.

[0049] S220: The target interface receives a sub-record editing operation for the target table, and the sub-record editing operation includes a sub-record move operation.

[0050] Here, a sub-record movement operation may be understood as an operation to move or adjust the position of at least one sub-record within the target table.

[0051] S230: Determine the sub-record to be edited based on the sub-record move operation, and determine the first parent record that is subordinate to the sub-record to be edited before the move and the second parent record that is subordinate to the sub-record after the move.

[0052] Here, the first parent record may be understood as the parent record to which the sub-record to be edited belongs before it is moved. The second parent record may be understood as the parent record to which the sub-record to be edited belongs after it is moved.

[0053] Specifically, the sub-record to be edited is determined based on the sub-record move operation, and the parent record to which the sub-record to be edited belongs before the move, i.e., the first parent record, is determined. And the parent record to which the sub-record to be edited belongs after the move, i.e., the second parent record, is determined.

[0054] In embodiments of this disclosure, the method for determining the first parent record to which a sub-record to be edited belongs before it is moved may specifically involve obtaining first description data before the sub-record to be edited is moved. The first parent record to which a sub-record to be edited belongs before it is moved is determined based on the first description data before the sub-record to be edited is moved. Similarly, determining the second parent record to which a sub-record to be edited belongs after it is moved may specifically involve obtaining first description data after the sub-record to be edited is moved. The second parent record to which a sub-record to be edited belongs after it is moved is determined based on the first description data after the sub-record to be edited is moved.

[0055] S240: Change the parent record in the first description data corresponding to the sub-record to be edited from the first parent record to the second parent record, delete the description data corresponding to the sub-record to be edited from the second description data corresponding to the first parent record, and add the description data corresponding to the sub-record to be edited to the second description data corresponding to the second parent record.

[0056] Specifically, the parent record in the first description data corresponding to the sub-record to be edited may be changed from the first parent record to the second parent record, so that the parent record in the first description data corresponding to the sub-record to be edited becomes the second parent record. After the change, the description data corresponding to the sub-record to be edited may be determined from the second description data corresponding to the first parent record, and a deletion operation may be performed on the description data corresponding to the sub-record to be edited from the second description data corresponding to the first parent record, or the description data corresponding to the sub-record to be edited may be written to the second description data corresponding to the second parent record.

[0057] S250: Update the display data in the target interface of the target table based on the modified first description data and the modified second description data.

[0058] According to the technical solution of the embodiment of this disclosure, a sub-record to be edited is determined based on the sub-record move operation, a first parent record dependent on the sub-record to be edited before the move and a second parent record dependent on the sub-record to be edited after the move are determined, the parent record in the first description data corresponding to the sub-record to be edited is changed from the first parent record to the second parent record, the description data corresponding to the sub-record to be edited is deleted from the second description data corresponding to the first parent record, the description data corresponding to the sub-record to be edited is added to the second description data corresponding to the second parent record, and a function is realized to perform a sub-record move operation on the sub-record in the target table.

[0059] Figure 3 is a schematic flowchart of another table data processing method provided by an embodiment of the present disclosure. The technical solution of this embodiment is that, in addition to the above embodiment, table data corresponding to the data access request is selectively stored on the client side. Updating hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and updating the display data in the target interface of the target table based on the hierarchical description data, includes, on the client side, determining the hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation and the table data corresponding to the data access request stored on the client side, and updating the display data in the target interface of the target table based on the hierarchical description data determined by the client side. For specific embodiments, refer to the description of this embodiment. Here, technical features that are the same as or similar to those of the above embodiment will not be described. As shown in Figure 3, the method of this embodiment may specifically include the following steps.

[0060] S310: In response to a data access request to a target table entered on the client side, the client-side target interface displays records of at least a portion of the target table, where the record refers to a single row of data in the target table, and the client side stores the table data corresponding to the data access request.

[0061] S320: The target interface receives a sub-record editing operation for the target table, and the client determines the hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation and the table data corresponding to the data access request stored on the client side, and updates the display data of the target table in the target interface based on the hierarchical description data determined by the client side.

[0062] Here, the hierarchical description data may be used to describe parent-child relationship data corresponding to sub-records and parent records containing sub-records in the target table.

[0063] In the embodiments of this disclosure, the client side stores table data corresponding to the data access request. Therefore, after receiving a sub-record editing operation for the target table via the target interface, the client side may update the corresponding hierarchical description data before the sub-record to be edited based on the sub-record editing operation and the table data corresponding to the data access request stored on the client side. This makes it possible to obtain the corresponding hierarchical description data after the sub-record to be edited, that is, to obtain the hierarchical description data corresponding to the sub-record to be edited. Furthermore, the display data of the target table in the target interface may be updated based on the hierarchical description data determined on the client side. In the embodiments of this disclosure, by processing in this way, not only is it possible to achieve real-time visibility of the modified target table on the client side, but it is also possible to ensure that client-side operations are displayed preferentially, that is, the rendering result of the target table can be displayed immediately on the client side without waiting for a response from the service side.

[0064] In embodiments of the present disclosure, the following may be further included: updating the display data in the target interface of the target table based on the hierarchical description data determined by the client; and, when the client receives hierarchical description data corresponding to the sub-record to be edited distributed by the service, updating the hierarchical description data corresponding to the sub-record to be edited stored on the client side based on the received hierarchical description data; and updating the display data in the target interface of the target table based on the hierarchical description data updated on the client side.

[0065] Specifically, when the client receives hierarchical description data corresponding to the sub-record to be edited, which has been distributed by the service, the client may narrow down and update the hierarchical description data corresponding to the sub-record to be edited, which is stored on the client side, based on the received hierarchical description data. Furthermore, the display data in the target interface of the target table may be updated based on the updated hierarchical description data on the client side. In the embodiments of this disclosure, after receiving a sub-record editing operation on the target table via the target interface, the service may upload a message for the editing operation to the service side so that it updates the hierarchical description data corresponding to the sub-record to be edited based on the message and distributes the updated hierarchical description data corresponding to the sub-record to be edited to the client side.

[0066] In the embodiments of this disclosure, in order to ensure consistency between the client-side and service-side hierarchical description data, the client-side determines the hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation and the table data corresponding to the data access request stored on the client side, without storing the data on the client side. The hierarchical description data stored on the client-side may be the hierarchical description data corresponding to the sub-record to be edited delivered by the service side.

[0067] According to the technical solution of the embodiment of this disclosure, the client side determines the hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation and the table data corresponding to the data access request stored on the client side, and updates the display data of the target table in the target interface based on the hierarchical description data determined by the client side, thereby realizing real-time visibility of the modified target table on the client side and achieving the technical effect of reducing the waiting time on the client side.

[0068] Figure 4 is a schematic flowchart of another table data processing method according to an embodiment of the present disclosure. The technical solution of this embodiment, in addition to the above embodiment, selectively determines hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and updates the display data in the target interface of the target table based on the hierarchical description data, which includes adding a predetermined identifier to the hierarchical description data corresponding to the sub-record to be edited stored on the client side, and updating the hierarchical description data corresponding to the sub-record to be edited stored on the client side based on the predetermined identifier. For specific embodiments, refer to the description of this embodiment. Here, the description of technical features that are the same as or similar to those of the above embodiment will be omitted. As shown in Figure 4, the method of this embodiment may specifically include the following steps.

[0069] S410: In response to a data access request to the target table entered by the client, the client-side target interface displays records of at least a portion of the target table, where the record refers to a single row of data in the target table.

[0070] S420: The target interface receives a sub-record editing operation for the target table, adds a predetermined identifier to the hierarchical description data corresponding to the sub-record to be edited stored on the client side, and updates the hierarchical description data corresponding to the sub-record to be edited stored on the client side based on the predetermined identifier.

[0071] Here, the hierarchical description data is used to describe parent-child relationship data corresponding to sub-records and parent records containing sub-records in the target table. A predetermined identifier can be used to identify whether the hierarchical description data corresponding to the sub-record to be edited, which is stored on the client side, is correct. In embodiments of this disclosure, if the predetermined identifier is added to the hierarchical description data corresponding to the sub-record, it can be determined that the hierarchical description data corresponding to the sub-record is incorrect. Similarly, if the predetermined identifier is not added to the hierarchical description data corresponding to the sub-record, it can be determined that the hierarchical description data corresponding to the sub-record is correct. In embodiments of this disclosure, by adding the predetermined identifier to the hierarchical description data corresponding to the sub-record, incorrect records in the target table can be quickly positioned to accurately update the incorrect records. The representation of the predetermined identifier may include numbers and / or letters.

[0072] Specifically, after receiving a sub-record editing operation for the target table via the target interface, the hierarchical description data corresponding to the sub-record to be edited, which is stored on the client side, can be determined. This allows a predetermined identifier to be added to the hierarchical description data corresponding to the sub-record to be edited, which is stored on the client side. Furthermore, the hierarchical description data corresponding to the sub-record to be edited, which is stored on the client side, can be updated based on the predetermined identifier.

[0073] In embodiments of this disclosure, updating the hierarchical description data corresponding to the sub-record to be edited, stored on the client side, based on the predetermined identifier, may first include transmitting the sub-record editing operation to the service side so that the service side updates the hierarchical description data corresponding to the sub-record to be edited, stored on the service side, based on the sub-record editing operation. Then, the hierarchical description data corresponding to the sub-record to be edited, distributed by the service side, may be received, and the hierarchical description data corresponding to the sub-record to be edited, stored on the client side, may be updated based on the received hierarchical description data and the predetermined identifier.

[0074] In embodiments of this disclosure, updating the hierarchical description data corresponding to the sub-record to be edited, which is stored on the client side, based on the received hierarchical description data and the predetermined identifier, may involve storing the received hierarchical description data on the client side and deleting the hierarchical description data to which the predetermined identifier has been added, or it may involve adopting the received hierarchical description data and replacing the hierarchical description data to which the predetermined identifier has been added.

[0075] S430: Based on the hierarchical description data, update the display data in the target interface of the target table.

[0076] In addition to the above embodiment, after receiving the hierarchical description data distributed by the service, it is determined whether the display data obtained based on the hierarchical description data distributed by the service matches the display data of the target table displayed on the client side at the current time. If NO, the display data of the target table at the target interface is updated based on the hierarchical description data distributed by the service. If YES, the hierarchical description data stored on the client side is updated when there is no detection, without performing any operations on the display data of the target table at the target interface based on the hierarchical description data distributed by the service.

[0077] According to the technical solution of the embodiment of this disclosure, a predetermined identifier is added to the hierarchical description data corresponding to the sub-record to be edited stored on the client side, and the hierarchical description data corresponding to the sub-record to be edited stored on the client side is updated based on the predetermined identifier, thereby enabling a quick and convenient update process for the hierarchical description data corresponding to the sub-record to be edited stored on the client side.

[0078] As one of the selectable embodiments of the embodiments of this disclosure, the specific steps of the table processing method of this embodiment may include the following steps:

[0079] 1. After receiving a data access request to the target table entered on the client side, the client-side target interface may display at least some of the records in the target table. The record refers to a single row of data in the target table. Referring to Figure 5, the records in the target table include parent record 1, sub-records 1.1, 2, parent record 3, 3.1, 4, 5, 6, and 7, all of which are subordinate to parent record 1.

[0080] Specifically, as shown in Figure 6, after receiving a table open operation for the target table entered by the operator on the client side, the client side may determine the hierarchical information (hierarchical description data) of the target table so as to retrieve some of the record data from the service side. After receiving some of the record data returned from the service side on the client side, the client side may calculate the hierarchical relationships of some of the records and cache the parent records and their sub-records in the target table on the client side. After the calculation is completed on the client side, the client side may notify the target table to re-render the record data. Here, the process by which the target table re-renders may specifically involve first retrieving the parent record from the client side's cache memory, and then retrieving the sub-records subordinate to the parent record from the client side's cache memory.

[0081] 2. The target interface receives sub-record editing operations on the target table, and these sub-record editing operations include sub-record movement operations. For example, as shown in Figure 7, the target interface may receive a sub-record drag operation on the target table, dragging sub-record 1.1 to parent record 3.

[0082] 3. Based on the drag operation of dragging sub-record 1.1 to parent record 3 in the target table, it may be determined that the record to be edited is sub-record 1.1, or it may be determined that the parent record to which sub-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.

[0083] 4. Subsequently, as shown in Figure 8, the client side may delete sub-record 1.1 in parent record 1 and add sub-record 1.1 to parent record 3. Local dirty mark processing may be performed on the hierarchical information of parent record 1 and parent record 3 stored on the client side. Furthermore, the service side may narrow down and render the target table based on the dirty mark hierarchical information so that the client side can render the target table preferentially without distributing the hierarchical information.

[0084] 5. The client may delete sub-record 1.1 included in parent record 1 and add sub-record 1.1 to parent record 3, then send a sub-record drag operation to the service side to drag sub-record 1.1 from the target table to parent record 3, so that the service side updates the hierarchical information corresponding to the sub-record drag operation and delivers the updated hierarchical information to the client side.

[0085] 6. After the client receives the updated hierarchy information, it may store the updated hierarchy information and determine whether the result of rendering the target table based on the updated hierarchy information matches the result of rendering the target table on the client side. If YES, the client may decide that it is not necessary to display the record of the target table displayed on the client side based on the updated hierarchy information. If NO, the client may render the target table displayed on the client side based on the updated hierarchy information in order to adjust the record of the target table displayed on the client side.

[0086] The technical solutions of the embodiments of this disclosure address the technical problem of low table processing efficiency inherent in conventional table processing, enabling the loading of table records as needed and the rapid and effective filtering and updating of modified records, thereby improving table processing efficiency and user experience.

[0087] Figure 9 is a schematic diagram of the structure of a table data processing device provided by an embodiment of the present disclosure, and as shown in Figure 9, the device includes a data access request module 510 and a table data display module 520. Here, the data access request module 510 is used to display at least a portion of the records of the target table on the client-side target interface in response to a data access request to the target table entered on the client side, where the record refers to a single row of data in the target table. The table data display module 520 is used to receive a sub-record editing operation on the target table via the target interface, determine hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and update the display data of the target table on the target interface based on the hierarchical description data, where the hierarchical description data is used to describe parent-child relationship data corresponding to the sub-records and parent records containing the sub-records in the target table.

[0088] According to the technical solution of the embodiment of this disclosure, the data access request module 510 responds to a data access request to the target table entered on the client side by displaying at least a portion of the records of the target table on the client-side target interface, where the record refers to a single row of data in the target table, and loads the records of the target table as needed. The table data display module 520 receives a sub-record editing operation for the target table via the target interface, determines hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and updates the display data of the target table on the target interface based on the hierarchical description data. In this technical solution, by defining hierarchical description data that describes parent-child relationship data corresponding to sub-records and parent records containing sub-records in the target table, the nesting hierarchy of records in the target table is reduced and the data structure of the target table is simplified. Then, based on the hierarchical description data, the display data of the target table on the target interface can be updated quickly and selectively. The technical solutions of the embodiments of this disclosure solve the technical problem of low table processing efficiency that exists in conventional table processing, load table records as needed, and enable rapid and effective filtering and updating of changed records without loading all the data in the target table, and support rapid editing and display of sub-records when displaying the table as needed, thereby improving the processing efficiency and user experience of the target table.

[0089] In addition to any of the selectable technical solutions of the embodiments of this disclosure, optionally, the hierarchical description data includes first description data and second description data, the first description data being used to describe the dependency relationship between the sub-record and the parent record to which the sub-record is dependent, and the second description data being used to describe the dependency relationship between the parent record and the sub-record contained within the parent record.

[0090] In addition to any of the selectable technical solutions of the embodiments of this disclosure, optionally, the sub-record editing operation includes a sub-record addition operation and / or a sub-record deletion operation, and the table data display module 520 includes a first hierarchical description data determination unit, which is used to add a first description data corresponding to a sub-record to be added, write the description data corresponding to the added sub-record to a second description data of the parent record to which the added sub-record belongs, and / or delete the first description data corresponding to a sub-record to be added, and delete 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, when the sub-record editing operation includes a sub-record deletion operation.

[0091] In addition to any of the selectable technical solutions of the embodiments of this disclosure, the sub-record editing operation optionally includes a sub-record movement operation. Furthermore, the table data display module 520 may include a second hierarchical description data determination unit, which is used to determine a sub-record to be edited based on the sub-record movement operation, to determine a first parent record that is dependent on the sub-record to be edited before the movement and a second parent record that is dependent on the sub-record to be edited after the movement, to change the parent record in the first description data corresponding to the sub-record to be edited from the first parent record to the second parent record, to delete the description data corresponding to the sub-record to be edited from the second description data corresponding to the first parent record, and to add the description data corresponding to the sub-record to be edited to the second description data corresponding to the second parent record.

[0092] In addition to any of the selectable technical solutions of the embodiments of this disclosure, optionally, the hierarchical description data is stored in the form of key-value pairs, wherein the first description data has 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 has the identifier of the parent record as the key and the identifier of the sub-record to which the parent record belongs as the value.

[0093] In addition to any of the selectable technical solutions of the embodiments of this disclosure, the client side optionally stores table data corresponding to the data access request. Furthermore, the table data display module 520 is used on the client side to determine hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation and the table data corresponding to the data access request stored on the client side, and to update the display data in the target interface of the target table based on the hierarchical description data determined by the client side.

[0094] In addition to any of the selectable technical solutions of the embodiments of this disclosure, the table data processing device optionally further includes a table data update module. The table data update module is used to update the hierarchical description data corresponding to the sub-records to be edited stored on the client side based on the received hierarchical description data, after the client side has updated the display data of the target table at the target interface based on the hierarchical description data determined by the client side, and when the client side receives hierarchical description data corresponding to the sub-records to be edited delivered by the service side, the client side updates the hierarchical description data corresponding to the sub-records to be edited stored on the client side based on the received hierarchical description data, and updates the display data of the target table at the target interface based on the updated hierarchical description data on the client side.

[0095] In addition to any of the selectable technical solutions of the embodiments of this disclosure, the table data display module 520 optionally includes a hierarchical description data update submodule, which is used to add a predetermined identifier to the hierarchical description data corresponding to the subrecord to be edited stored on the client side, and to update the hierarchical description data corresponding to the subrecord to be edited stored on the client side based on the predetermined identifier.

[0096] In addition to any of the selectable technical solutions of the embodiments of this disclosure, the hierarchical description data update submodule optionally includes a service-side hierarchical update unit and a client-side hierarchical update unit, wherein the service-side hierarchical update unit is used to transmit a sub-record editing operation to the service side so that the service side updates the hierarchical description data corresponding to the sub-record to be edited, which is stored on the service side, based on the sub-record editing operation, and the client-side hierarchical update unit is used to receive the hierarchical description data corresponding to the sub-record to be edited delivered by the service side and to update the hierarchical description data corresponding to the sub-record to be edited, which is stored on the client side, based on the received hierarchical description data and the predetermined identifier.

[0097] In addition to any of the selectable technical solutions of the embodiments of this disclosure, the data access request module 510 optionally includes a client-side data cache unit and a target table display unit. The client-side data cache unit is used to retrieve target data corresponding to the record being accessed from the table data of the target table stored on the service side in response to a data access request to a target table entered on the client side, and to cache the target data on the client side. The target table display unit is used to display the target table in the client-side target interface based on the target data cached on the client side.

[0098] The table data processing device according to the embodiment of this disclosure can execute the table data processing method provided by any embodiment of this disclosure and is equipped with a functional module and beneficial effects corresponding to the table data processing method.

[0099] Furthermore, the units and modules included in the above-mentioned device are merely divided according to functional logic and are not limited to the above division; they only need to be able to realize the corresponding function. Also, the specific names of each functional unit are merely for the purpose of making them easier to distinguish from one another and do not limit the scope of protection of the embodiments of this disclosure.

[0100] Hereinafter, refer to Figure 10, which shows a schematic diagram of the configuration of an electronic device (e.g., terminal device or server) 600 suitable for implementing the embodiments of this disclosure. The terminal devices in the embodiments of this disclosure may include, but are not limited to, mobile devices such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablets), PMPs (portable multimedia players), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. The electronic device shown in Figure 10 is merely an example and does not in any way limit the functions and scope of use of the embodiments of this disclosure.

[0101] As shown in Figure 10, the electronic device 600 may include a processing unit (e.g., a central processing unit, graphics processor, etc.) 601, which can perform its respective appropriate operations and processes by programs stored in read-only memory (ROM) 602 or by programs loaded from storage device 608 into random access memory (RAM) 603. RAM 603 stores the respective programs and data necessary for the operation of the electronic device 600. The processing unit 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0102] Generally, an input device 606, including, for example, a touchscreen, touch panel, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc., an output device 607, including, for example, a liquid crystal display (LCD), speaker, oscillator, etc., a storage device 608, including, for example, magnetic tape, hard disk, etc., and a communication device 609 may be connected to the I / O interface 605. The communication device 609 enables the electronic device 600 to exchange data with other devices via wireless or wired communication. Figure 10 shows an electronic device 600 equipped with various devices, but it should be understood that it is not required to implement or have all of the devices shown. Alternatively, it is possible to implement or have more or fewer devices.

[0103] In particular, according to embodiments of the present disclosure, the process described above can be implemented as a computer software program with reference to the flowchart. For example, embodiments of the present disclosure include a computer program product which includes a computer program mounted on a non-temporary computer-readable medium, and the computer program includes program code for performing the method shown in the flowchart. In such embodiments, the computer program may be downloaded and installed from a network via a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by a processing unit 601, it performs the functions described above, limited to the methods of embodiments of the present disclosure.

[0104] The names of messages or information that interact between multiple devices in embodiments of this disclosure are used for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0105] The electronic device and the table data processing method according to the embodiments of this disclosure belong to the same inventive concept, and for technical details not described in detail in these embodiments, the above embodiments can be referenced, and these disclosed embodiments have the same beneficial effects as the above embodiments.

[0106] The embodiments of this disclosure provide a computer storage medium that stores a computer program that implements the table data processing method according to the above embodiments when executed by a processor.

[0107] The computer-readable medium described above in this disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. The computer-readable storage medium may be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specifically, the computer-readable storage medium may include, but is not limited to, an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In embodiments of this disclosure, the computer-readable storage medium may be any tangible medium containing or storing a program, which can be used in or in combination with an instruction execution system, apparatus, or device. In embodiments of this disclosure, the computer-readable signal medium may contain a data signal propagated in the baseband or as part of a carrier wave, which contains computer-readable program code. The data signals propagated in this manner may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium may further be any computer-readable medium other than a computer-readable storage medium, and this computer-readable medium can transmit, propagate, or transmit programs used in or in combination with instruction execution systems, apparatus, or devices. The program code contained in the computer-readable medium can be transmitted by any suitable medium, including but not limited to electric wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0108] According to one or more embodiments of the present disclosure, [Example 1] provides a table data processing method that includes the steps of: displaying at least a portion of the records of a target table in a client-side target interface in response to a data access request to a target table entered on the client side, wherein the records refer to a row of data in the target table; and receiving a sub-record editing operation on the target table by the target interface, determining hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and updating the display data of the target table in the target interface based on the hierarchical description data, wherein the hierarchical description data is used to describe parent-child relationship data corresponding to sub-records and parent records containing sub-records in the target table.

[0109] According to one or more embodiments of the present disclosure, [Example 2] optionally provides a method of Example 1, further comprising the steps of the first description data being used to describe the dependency relationship between the sub-record and the parent record to which the sub-record is dependent, and the second description data being used to describe the dependency relationship between the parent record and the sub-record contained in the parent record.

[0110] According to one or more embodiments of the present disclosure, [Example 3] provides a method of Example 1, which optionally includes a sub-record editing operation including a sub-record addition operation and / or a sub-record deletion operation, and determining the hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, which further includes, if the sub-record editing operation includes a sub-record addition operation, adding a first description data corresponding to the sub-record to be added and writing the description data corresponding to the sub-record to be added to the second description data of the parent record to which the added sub-record belongs, and / or, if the sub-record editing operation includes a sub-record deletion operation, deleting the first description data corresponding to the sub-record to be added and deleting the description data corresponding to the sub-record to be added from the second description data of the parent record to which the added sub-record belongs.

[0111] According to one or more embodiments of the present disclosure, [Example 4] provides a method of Example 1, which optionally includes, the sub-record editing operation includes a sub-record move operation, and determining the hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, determining the sub-record to be edited based on the sub-record move operation, determining the first parent record to which the sub-record to be edited is subordinate before the move and the second parent record to which it is subordinate after the move, changing the parent record in the first description data corresponding to the sub-record to be edited from the first parent record to the second parent record, deleting the description data corresponding to the sub-record to be edited from the second description data corresponding to the first parent record, and adding the description data corresponding to the sub-record to be edited to the second description data corresponding to the second parent record.

[0112] According to one or more embodiments of the present disclosure, [Example 5] provides an example method comprising, optionally, the hierarchical description data being stored in the form of key-value pairs, wherein the first description data has 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 has the identifier of the parent record as the key and the identifier of the sub-record to which the parent record belongs as the value.

[0113] According to one or more embodiments of the present disclosure, [Example 6] provides a method of Example 1 which includes, selectively, having table data corresponding to the data access request stored on the client side, updating hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and updating the display data in the target interface of the target table based on the hierarchical description data, wherein on the client side, the client side determines the hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation and the table data corresponding to the data access request stored on the client side, and updates the display data in the target interface of the target table based on the hierarchical description data determined by the client side.

[0114] According to one or more embodiments of the present disclosure, [Example 7] provides a method of Example 1, which optionally includes updating the display data in the target interface of the target table based on the hierarchical description data determined by the client, and then, when the client receives hierarchical description data corresponding to a sub-record to be edited delivered by the service, updating the hierarchical description data corresponding to the sub-record to be edited stored on the client based on the received hierarchical description data, and updating the display data in the target interface of the target table based on the updated hierarchical description data on the client.

[0115] According to one or more embodiments of the present disclosure, [Example 8] provides a method of Example 1 in which, selectively determining hierarchical description data corresponding to a sub-record to be edited based on the sub-record editing operation, includes adding a predetermined identifier to the hierarchical description data corresponding to the sub-record to be edited stored on the client side, and updating the hierarchical description data corresponding to the sub-record to be edited stored on the client side based on the predetermined identifier.

[0116] According to one or more embodiments of the present disclosure, [Example 9] provides a method of Example 1 that selectively updates hierarchical description data corresponding to a sub-record to be edited stored on the client side based on a predetermined identifier, which includes transmitting a sub-record editing operation to the service side so that the service side updates the hierarchical description data corresponding to the sub-record to be edited stored on the service side based on the sub-record editing operation, and receiving hierarchical description data corresponding to the sub-record to be edited delivered by the service side, and updating the hierarchical description data corresponding to the sub-record to be edited stored on the client side based on the received hierarchical description data and the predetermined identifier.

[0117] According to one or more embodiments of the present disclosure, [Example 10] provides a method of Example 1 in which the step of selectively displaying at least a portion of the records of a target table in the client-side target interface in response to a data access request to the target table entered on the client side includes, in response to a data access request to the target table entered on the client side, retrieving target data corresponding to the record for which access is requested from the table data of the target table stored on the service side, caching the target data on the client side, and displaying the target table in the client-side target interface based on the target data cached on the client side.

[0118] According to one or more embodiments of the present disclosure, [Example 11] provides a table data processing device comprising: a data access request module that displays at least a portion of the records of a target table in a client-side target interface in response to a data access request to a target table entered on the client side, wherein the records refer to data in a single row in the target table; and a table data display module that receives a sub-record editing operation on the target table via the target interface, determines hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and updates the display data of the target table in the target interface based on the hierarchical description data, wherein the hierarchical description data is used to describe parent-child relationship data corresponding to sub-records and parent records containing sub-records in the target table.

[0119] In some embodiments, clients and servers can communicate using any known or future-to-be-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communications (e.g., communication networks) in any form or medium. Examples of communication networks include local area networks ("LANs"), wide area networks ("WANs"), the Internet (e.g., interconnected networks), peer-to-peer networks (e.g., ad hoc peer-to-peer networks), and any known or future-to-be-developed networks.

[0120] The computer-readable medium described above may be included in the electronic device described above, or it may exist independently without being attached to the electronic device.

[0121] The computer-readable medium described above carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device is instructed to perform the following steps: display at least a portion of the records of the target table on the client-side target interface in response to a data access request to the target table entered on the client side, wherein the record refers to a row of data in the target table; and receive a sub-record editing operation on the target table via the target interface, determine hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and update the display data of the target table on the target interface based on the hierarchical description data, wherein the hierarchical description data is used to describe parent-child relationship data corresponding to the sub-records and parent records containing the sub-records in the target table.

[0122] Computer program code for performing the operations disclosed herein may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java®, Smalltalk, and C++, and more specifically, general procedural programming languages ​​such as the "C" language or similar programming languages. The program code may run entirely on a user computer, partially on a user computer, run as a standalone software package, run partly on a user computer and partly on a remote computer, or run entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user computer by any network, including a local area network (LAN) or a wide area network (WAN), or it may be connected to an external computer (for example, via the Internet using an Internet service provider).

[0123] The flowcharts and block diagrams in the drawings illustrate the implementable system architectures, functions, and operations of systems, methods, and computer program products relating to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or part of code, which includes one or more executable instructions for implementing a given logical function. It should also be noted that in some alternative implementations, the functions represented in a block may be implemented in a different order than those shown in the drawings. For example, two consecutively shown blocks may be executed substantially in parallel, or they may be executed in reverse order depending on the function. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in a block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs a given function or operation, or by a combination of dedicated hardware and computer instructions.

[0124] The modules described in the embodiments of this disclosure may be implemented in software or in hardware. Herein, the names of the modules are not limited in any case to the module itself; for example, the data access request module may be further described as "a module that displays records of at least a portion of the target table in the client-side target interface."

[0125] The functions described herein may be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that may be used include, but are not limited to, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standards (ASSPs), systems on chips (SOCs), coupled programmable logic devices (CPLDs), and the like.

[0126] In the context of this disclosure, machine-readable media may be tangible storage media that contain or store programs used in or in combination with instruction execution systems, devices, or equipment. Machine-readable media may be machine-readable signal media or machine-readable storage media. Machine-readable media may include, but are not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination thereof. More specifically, machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0127] The above description is merely a description of preferred embodiments and applicable technical principles of the present disclosure. Those skilled in the art should understand that the scope of the present disclosure is not limited to technical solutions formed by specific combinations of the above technical features, but should also include other technical solutions formed by arbitrarily combining the above technical features or equivalent features without departing from the above-disclosed concept. For example, it also includes technical solutions formed by substituting the above features with (not limited to) similar functional technical features disclosed in the present disclosure.

[0128] Furthermore, although the operations have been described in a specific order, it should not be understood that these operations must be performed in a specific order or sequence as indicated. In certain environments, multitasking and parallel processing may be advantageous. Similarly, although the above description includes various specific implementation details, these should not be construed as limiting the scope of this disclosure. Some features described in the context of a single embodiment may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments, individually or in any appropriate partial combination.

[0129] Although this topic has been described using language specific to constituent features and / or methodological logic and operation, it should not be understood that the topic limited to the attached claims is limited to the specific features or operations described above. Rather, the specific features and operations described above are merely illustrative forms of realizing the claims.

Claims

1. A step in which, in response to a data access request to a target table entered on the client side, the client-side target interface displays records of at least a portion of the target table, wherein the record refers to a single row of data in the target table. A table data processing method characterized by the steps of: receiving a sub-record editing operation on the target table via the target interface; determining hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation; and updating the display data of the target table in the target interface based on 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 table data processing method according to claim 1, wherein the hierarchical description data includes 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 included in the parent record.

3. The aforementioned sub-record editing operation includes a sub-record addition operation and / or a sub-record deletion operation, and based on the aforementioned sub-record editing operation, the hierarchical description data corresponding to the sub-record to be edited is determined. If the sub-record editing operation includes a sub-record addition operation, the first description data corresponding to the added sub-record is added, and the description data corresponding to the added sub-record is written to the second description data of the parent record to which the added sub-record belongs, and / or The table data processing method according to claim 2, characterized in that, when the sub-record editing operation includes a sub-record deletion operation, the method includes 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.

4. The aforementioned sub-record editing operation includes a sub-record movement operation, and based on the aforementioned sub-record editing operation, the hierarchical description data corresponding to the sub-record to be edited is determined as follows: The sub-record to be edited is determined based on the sub-record move operation, and the first parent record that is subordinate to the sub-record to be edited before the move and the second parent record that is subordinate after the move are determined. The table data processing method according to claim 2, characterized by including changing the parent record in the first description data corresponding to the sub-record to be edited from the first parent record to the second parent record, deleting the description data corresponding to the sub-record to be edited from the second description data corresponding to the first parent record, and adding the description data corresponding to the sub-record to be edited to the second description data corresponding to the second parent record.

5. The table data processing method according to claim 2, characterized in that the hierarchical description data is stored in the form of key-value pairs, the first description data uses 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 uses the identifier of the parent record as the key and the identifier of the sub-record that belongs to the parent record as the value.

6. The client side stores table data corresponding to the data access request, updates the hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and updates the display data in the target interface of the target table based on the hierarchical description data, The table data processing method according to claim 1, characterized in that the client side determines hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation and the table data corresponding to the data access request stored on the client side, and updates the display data in the target interface of the target table based on the hierarchical description data determined by the client side.

7. After updating the display data in the target interface of the target table based on the hierarchical description data determined by the client, When the client receives hierarchical description data corresponding to the sub-record to be edited, distributed by the service, the client updates the hierarchical description data corresponding to the sub-record to be edited, which is stored on the client side, based on the received hierarchical description data. The table data processing method according to claim 6, further comprising updating the display data in the target interface of the target table based on the hierarchical description data updated on the client side.

8. Based on the aforementioned sub-record editing operation, determining the hierarchical description data corresponding to the sub-record to be edited is: The table data processing method according to claim 1, characterized in that it includes adding a predetermined identifier to the hierarchical description data corresponding to the sub-record to be edited stored on the client side, and updating the hierarchical description data corresponding to the sub-record to be edited stored on the client side based on the predetermined identifier.

9. Updating the hierarchical description data corresponding to the sub-record to be edited, which is stored on the client side based on the predetermined identifier, Sending the sub-record editing operation to the service so that the service updates the hierarchical description data corresponding to the sub-record to be edited, which is stored on the service side, based on the sub-record editing operation; The table data processing method according to claim 8, characterized in that it includes receiving hierarchical description data corresponding to the sub-record to be edited distributed by the service, and updating the hierarchical description data corresponding to the sub-record to be edited stored on the client side based on the received hierarchical description data and the predetermined identifier.

10. The step of displaying at least a portion of the records in the target table on the client side's target interface in response to a data access request to the target table entered on the client side is: In response to a data access request to the target table entered on the client side, the service retrieves the target data corresponding to the record being accessed from the table data of the target table stored on the service side, and caches the target data on the client side. The table data processing method according to claim 1, characterized in that it includes displaying the target table in the target interface on the client side based on the target data cached on the client side.

11. A data access request module that, in response to a data access request to a target table entered on the client side, displays records of at least a portion of the target table in the client-side target interface, wherein the record refers to a data access request module that points to a single row of data in the target table. A table data processing device comprising: a table data display module that receives a sub-record editing operation on the target table via the target interface, determines hierarchical description data corresponding to the sub-record to be edited based on the sub-record editing operation, and updates the display data of the target table in the target interface based on the hierarchical description data, wherein the hierarchical description data is a table data display module used to describe parent-child relationship data corresponding to sub-records and parent records containing sub-records in the target table.

12. One or more processors, A storage device that stores one or more programs, An electronic device characterized in that, when the one or more programs are executed by the one or more processors, the one or more processors are made to execute the table data processing method described in any one of claims 1 to 10.

13. A storage medium including a computer-executable instruction, characterized in that when the computer-executable instruction is executed by a computer processor, the table data processing method described in any one of claims 1 to 10 is executed.

14. A computer program product comprising a computer program, characterized in that the computer program implements the table data processing method described in any one of claims 1 to 10 when the computer program is executed by a processor.

Images