Method and device for changing field of financial data table, electronic equipment and storage medium

Abstract

The application provides a field change method and device of a financial data table, an electronic device and a storage medium, the method comprising: receiving a field change request of a financial data table sent by a field change user; the field change request containing a change table identifier; storing data in a first financial data table corresponding to the change table identifier into a second financial data table corresponding to the first financial data table; performing field change on the first financial data table corresponding to the field change request; and receiving a financial data change request sent by a data change user; performing financial data change on the second financial data table corresponding to the financial data change request. The application stores data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table, and performs financial data change on the second financial data table corresponding to the financial data change request, thereby avoiding loss of financial data.

Description

Technical Field

[0001] This invention relates to the field of financial data processing technology, and more specifically, to methods, apparatus, electronic devices, and storage media for changing fields in financial data tables. Background Technology

[0002] As financial transactions increase, financial data becomes more complex, and financial data tables storing this data require corresponding field changes. When changing fields in a financial data table, the table needs to be locked to complete the change operation.

[0003] However, during the table locking process, financial data tables cannot be modified by adding or deleting financial data, resulting in a large amount of data loss. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide a method, apparatus, electronic device and storage medium for changing fields of a financial data table, which can modify the financial data table and avoid the loss of financial data.

[0005] Firstly, embodiments of this application provide a method for modifying fields in a financial data table, the method comprising:

[0006] Receive field change requests for financial data tables from users who have requested field changes; the field change requests contain the table identifier to be changed.

[0007] Store the data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table;

[0008] Perform field changes on the first financial data table corresponding to the field change request; and receive financial data change requests sent by users who want to change data.

[0009] Make the financial data changes to the second financial data table in accordance with the financial data change request.

[0010] In one possible implementation, before storing the data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table, the field modification method of the financial data table further includes:

[0011] A second financial data table corresponding to the first financial data table is determined in a preset table; the preset table stores the corresponding identifiers of the first financial data table and the second financial data table.

[0012] In one possible implementation, the method for changing the fields of the financial data table further includes:

[0013] After the changes to the first financial data table are completed, update the data in the second financial data table to the first financial data table;

[0014] Receive target financial data change requests sent by users who have experienced data changes;

[0015] Make changes to the first financial data table that correspond to the target financial data change request.

[0016] In one possible implementation, after updating the data in the second financial data table to the first financial data table, the method for changing the fields of the financial data table further includes:

[0017] Delete the second financial data table and the preset table.

[0018] In one possible implementation, before storing the data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table, the field modification method of the financial data table further includes:

[0019] Receive field change user sent second financial data table identifier corresponding to the first financial data table;

[0020] Create a second financial data table with the identifier of the second financial data table;

[0021] Store the corresponding identifiers of the first financial data table and the second financial data table in a preset table.

[0022] Secondly, embodiments of this application also provide a field modification device for a financial data table, the field modification device for the financial data table comprising:

[0023] The receiving module is used to receive field change requests for financial data tables sent by users who wish to change fields; the field change request contains the identifier of the changed table;

[0024] The storage module is used to store the data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table;

[0025] The field modification module is used to modify the fields in the first financial data table according to the field modification request.

[0026] The receiving module is also used to receive financial data change requests sent by users who have changed their data.

[0027] The financial data modification module is used to modify the financial data in the second financial data table in accordance with the financial data modification request.

[0028] In one possible implementation, the field modification device for the financial data table further includes: a determination module;

[0029] The determination module is used to determine the second financial data table corresponding to the first financial data table from a preset table; the preset table stores the corresponding identifiers of the first financial data table and the second financial data table.

[0030] In one possible implementation, the field modification device for the financial data table further includes: an update module;

[0031] The update module is used to update the data in the second financial data table to the first financial data table after the first financial data table has been modified.

[0032] The receiving module is also used to receive target financial data change requests sent by users who have changed their data.

[0033] The financial data modification module is also used to modify the first financial data table to match the target financial data modification request.

[0034] In one possible implementation, the field modification device for the financial data table further includes a deletion module;

[0035] The delete module is used to delete the second financial data table and the preset table.

[0036] In one possible implementation, the field modification device for the financial data table further includes: a creation module;

[0037] The receiving module is also used to receive the identifier of the second financial data table corresponding to the first financial data table sent by the user who changed the field.

[0038] The creation module is used to create a second financial data table identified as the second financial data table identifier;

[0039] The storage module is also used to store the identifiers corresponding to the first financial data table and the second financial data table into a preset table.

[0040] Thirdly, embodiments of this application also provide an electronic device, including: a processor, a storage medium, and a bus. The storage medium stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the field modification method for any of the financial data tables in the first aspect.

[0041] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the field modification method for any of the financial data tables in the first aspect.

[0042] This application provides a method, apparatus, electronic device, and storage medium for modifying fields in a financial data table. The method includes: receiving a field modification request for a financial data table sent by a user; the field modification request includes a modification table identifier; storing data from a first financial data table corresponding to the modification table identifier into a second financial data table corresponding to the first financial data table; performing field modifications on the first financial data table corresponding to the field modification request; and receiving a financial data modification request from a user; and performing financial data modifications on the second financial data table corresponding to the financial data modification request. This application avoids the loss of financial data by storing data from the first financial data table corresponding to the modification table identifier into the second financial data table corresponding to the first financial data table; and performing financial data modifications on the second financial data table corresponding to the financial data modification request. Attached Figure Description

[0043] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0044] Figure 1 This document illustrates a flowchart of a method for modifying fields in a financial data table, as provided in an embodiment of this application.

[0045] Figure 2 A flowchart illustrating another method for modifying fields in a financial data table, as provided in an embodiment of this application, is shown.

[0046] Figure 3 A flowchart illustrating another method for modifying fields in a financial data table, as provided in an embodiment of this application, is shown.

[0047] Figure 4 A flowchart illustrating another method for modifying fields in a financial data table, as provided in an embodiment of this application, is shown.

[0048] Figure 5 This illustration shows a structural diagram of a field modification device for a financial data table provided in an embodiment of this application;

[0049] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0050] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0051] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0052] To enable those skilled in the art to utilize the content of this application, and in conjunction with the specific application scenario of "financial data processing technology," the following implementation methods are provided. For those skilled in the art, the general principles defined herein can be applied to other embodiments and application scenarios without departing from the spirit and scope of this application. Although this application is primarily described within the "financial data processing technology field," it should be understood that this is merely an exemplary embodiment.

[0053] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.

[0054] The following is a detailed description of a method for changing fields in a financial data table provided in an embodiment of this application.

[0055] Reference Figure 1 The diagram shown is a flowchart illustrating a method for modifying fields in a financial data table according to an embodiment of this application. The specific execution process of this method is as follows:

[0056] S101. Receive a field change request for a financial data table sent by a user; the field change request contains a change table identifier.

[0057] S102. Store the data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table.

[0058] S103. Perform field changes on the first financial data table corresponding to the field change request; and receive financial data change requests sent by the data change user.

[0059] S104. Make financial data changes to the second financial data table corresponding to the financial data change request.

[0060] This application provides a method for modifying fields in a financial data table. The method includes: receiving a field modification request from a user; the field modification request includes a modification table identifier; storing data from a first financial data table corresponding to the modification table identifier into a second financial data table corresponding to the first financial data table; performing field modifications on the first financial data table corresponding to the field modification request; and receiving a financial data modification request from a user; and performing financial data modifications on the second financial data table corresponding to the financial data modification request. This application avoids the loss of financial data by storing data from the first financial data table corresponding to the modification table identifier into the second financial data table corresponding to the first financial data table; and performing financial data modifications on the second financial data table corresponding to the financial data modification request.

[0061] The exemplary steps of the embodiments of this application are described below:

[0062] S101. Receive a field change request for a financial data table sent by a user; the field change request contains a change table identifier.

[0063] In this embodiment, each financial data table contains multiple fields, meaning each piece of data in the financial data table corresponds to multiple attributes. For example, a user table contains username, contact information, gender, etc. As business becomes increasingly complex, the fields of the financial data tables also need to be changed. When a financial data table needs to be changed, a field change request is received from the user requesting the field change. The field change request includes a change table identifier, a change field identifier, and a field change type. The change table identifier refers to the identifier of the financial data table that needs to be changed. The change field identifier refers to the identifier of the field in the financial data table that needs to be changed corresponding to the change table identifier. The field change type can be either adding a field or deleting a field. Each financial data table has one identifier, and each field has one identifier.

[0064] S102. Store the data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table.

[0065] In this embodiment, when a field change is required in the first financial data table, the data in the first financial data table corresponding to the change table identifier is stored in the second financial data table corresponding to the first financial data table. The second financial data table serves as a candidate financial data table when a field change is required in the first financial data table. This way, when a field change is needed in the first financial data table, the financial data can be changed through the second financial data table, avoiding data loss due to table locking in the first financial data table caused by field changes. The first and second financial data tables have the same table structure.

[0066] S103. Perform field changes on the first financial data table corresponding to the field change request; and receive financial data change requests sent by the data change user.

[0067] In this embodiment of the application, the field modification of the first financial data table corresponding to the field modification request includes: if the field modification type in the field modification request is an "add field" type, then in the financial data table corresponding to the change table identifier in the field modification request, the field corresponding to the change field identifier in the field modification request is added. If the field modification type in the field modification request is a "delete field" type, then in the financial data table corresponding to the change table identifier in the field modification request, the field corresponding to the change field identifier in the field modification request is deleted.

[0068] It also receives financial data change requests from users whose data has been changed; financial data change requests can include adding, deleting, modifying, or querying financial data.

[0069] S104. Make financial data changes to the second financial data table corresponding to the financial data change request.

[0070] Furthermore, after the first financial data table is modified, the data in the second financial data table is updated in the first financial data table; the target financial data modification request sent by the user who changed the data is received; and the financial data modification corresponding to the target financial data modification request is performed on the first financial data table.

[0071] Furthermore, after updating the data in the second financial data table to the first financial data table, the method for changing the fields of the financial data table also includes: deleting the second financial data table and the preset table.

[0072] Reference Figure 2 The diagram shown is a flowchart illustrating another method for changing fields in a financial data table according to an embodiment of this application. The exemplary steps of this embodiment are described below:

[0073] S201. Receive a field change request for a financial data table sent by a user; the field change request contains a change table identifier.

[0074] In this embodiment, each financial data table contains multiple fields, meaning each piece of data in the financial data table corresponds to multiple attributes. For example, a user table contains username, contact information, gender, etc. As business becomes increasingly complex, the fields of the financial data tables also need to be changed. When a financial data table needs to be changed, a field change request is received from the user requesting the field change. The field change request includes a change table identifier, a change field identifier, and a field change type. The change table identifier refers to the identifier of the financial data table that needs to be changed. The change field identifier refers to the identifier of the field in the financial data table that needs to be changed corresponding to the change table identifier. The field change type can be either adding a field or deleting a field. Each financial data table has one identifier, and each field has one identifier.

[0075] S202. Determine the second financial data table corresponding to the first financial data table in the preset table.

[0076] In the embodiments of this application, the preset table stores the corresponding identifiers of the first financial data table and the second financial data table.

[0077] S203. Store the data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table.

[0078] In this embodiment, when a field change is required in the first financial data table, the data in the first financial data table corresponding to the change table identifier is stored in the second financial data table corresponding to the first financial data table. The second financial data table serves as a candidate financial data table when a field change is required in the first financial data table. This way, when a field change is required in the first financial data table, the financial data can be changed through the second financial data table, avoiding data loss due to table locking caused by field changes in the first financial data table.

[0079] S204. Perform field changes on the first financial data table corresponding to the field change request; and receive financial data change requests sent by the data change user.

[0080] In this embodiment of the application, the field modification of the first financial data table corresponding to the field modification request includes: if the field modification type in the field modification request is an "add field" type, then in the financial data table corresponding to the change table identifier in the field modification request, the field corresponding to the change field identifier in the field modification request is added. If the field modification type in the field modification request is a "delete field" type, then in the financial data table corresponding to the change table identifier in the field modification request, the field corresponding to the change field identifier in the field modification request is deleted.

[0081] It also receives financial data change requests from users whose data has been changed; financial data change requests can include adding, deleting, modifying, or querying financial data.

[0082] S205. Make financial data changes to the second financial data table corresponding to the financial data change request.

[0083] Furthermore, after the first financial data table is modified, the data in the second financial data table is updated in the first financial data table; the target financial data modification request sent by the user who changed the data is received; and the financial data modification corresponding to the target financial data modification request is performed on the first financial data table.

[0084] Furthermore, after updating the data in the second financial data table to the first financial data table, the methods for changing the fields of the financial data table also include: deleting the second financial data table and the preset table.

[0085] This application provides another method for modifying fields in a financial data table. The method includes: receiving a field modification request for a financial data table sent by a user; the field modification request includes a modification table identifier; determining a second financial data table corresponding to a first financial data table in a preset table; storing data from the first financial data table corresponding to the modification table identifier into the second financial data table corresponding to the first financial data table; modifying the fields in the first financial data table according to the field modification request; and receiving a financial data modification request from a user; and modifying the financial data in the second financial data table according to the financial data modification request. This method can prevent the loss of financial data.

[0086] Reference Figure 3 The diagram shown is a flowchart illustrating another method for changing fields in a financial data table according to an embodiment of this application. The exemplary steps of this embodiment are described below:

[0087] S301. After the changes to the first financial data table are completed, update the data in the second financial data table to the first financial data table.

[0088] In this application embodiment, updating data from the second financial data table to the first financial data table includes: storing data that exists in the second financial data table but does not exist in the first financial data table into the first financial data table; and deleting data that exists in the first financial data table but does not exist in the second financial data table from the first financial data table.

[0089] Furthermore, delete the second financial data table and the preset table.

[0090] In this embodiment of the application, after the first financial data table is modified, the second financial data table and the preset table are deleted, thereby reducing the number of compatible data tables that need to be managed and improving the processing efficiency of financial data.

[0091] S302, Receive a request for change of target financial data sent by a user who has changed their data.

[0092] In this embodiment of the application, the target financial data change request can be the addition, deletion, modification, or query of financial data.

[0093] S303. Make financial data changes to the first financial data table corresponding to the target financial data change request.

[0094] In this application embodiment, after the first financial data table is modified, the financial data corresponding to the target financial data modification request is modified through the first financial data table.

[0095] This application provides another method for modifying fields in a financial data table. The method includes: after modifying a first financial data table, updating the first financial data table with data from a second financial data table; receiving a target financial data modification request sent by a user; and modifying the first financial data table to correspond to the target financial data modification request. Through this method, the first financial data table can be modified to reflect the target financial data modification request.

[0096] Reference Figure 4 The diagram shown is a flowchart illustrating another method for changing fields in a financial data table according to an embodiment of this application. The exemplary steps of this embodiment are described below:

[0097] S401: Receive a field change request for a financial data table sent by a user; the field change request contains a change table identifier.

[0098] In this embodiment, each financial data table contains multiple fields, meaning each piece of data in the financial data table corresponds to multiple attributes. For example, a user table contains username, contact information, gender, etc. As business becomes increasingly complex, the fields of the financial data tables also need to be changed. When a financial data table needs to be changed, a field change request is received from the user requesting the field change. The field change request includes a change table identifier, a change field identifier, and a field change type. The change table identifier refers to the identifier of the financial data table that needs to be changed. The change field identifier refers to the identifier of the field in the financial data table that needs to be changed corresponding to the change table identifier. The field change type can be either adding a field or deleting a field. Each financial data table has one identifier, and each field has one identifier.

[0099] S402, Receive the second financial data table identifier sent by the user who changed the field, which corresponds to the first financial data table.

[0100] In this embodiment, after receiving a field change request for a financial data table from a user who has changed fields, and before storing the data in the first financial data table corresponding to the changed table identifier into the second financial data table corresponding to the first financial data table, the system receives a second financial data table identifier corresponding to the first financial data table from the user who has changed fields. The system then stores the identifier corresponding to the first financial data table and the identifier corresponding to the second financial data table into a preset table.

[0101] S403. Create a second financial data table with the identifier of the second financial data table.

[0102] S404. Store the corresponding identifier of the first financial data table and the corresponding identifier of the second financial data table into a preset table.

[0103] S405. Store the data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table.

[0104] In this embodiment, when a field change is required in the first financial data table, the data in the first financial data table corresponding to the change table identifier is stored in the second financial data table corresponding to the first financial data table. The second financial data table serves as a candidate financial data table when a field change is required in the first financial data table. This way, when a field change is required in the first financial data table, the financial data can be changed through the second financial data table, avoiding data loss due to table locking caused by field changes in the first financial data table.

[0105] S406. Perform field changes on the first financial data table corresponding to the field change request; and receive financial data change requests sent by the data change user.

[0106] In this embodiment of the application, the field modification of the first financial data table corresponding to the field modification request includes: if the field modification type in the field modification request is an "add field" type, then in the financial data table corresponding to the change table identifier in the field modification request, the field corresponding to the change field identifier in the field modification request is added. If the field modification type in the field modification request is a "delete field" type, then in the financial data table corresponding to the change table identifier in the field modification request, the field corresponding to the change field identifier in the field modification request is deleted.

[0107] It also receives financial data change requests from users whose data has been changed; financial data change requests can include adding, deleting, modifying, or querying financial data.

[0108] S407. Make financial data changes to the second financial data table corresponding to the financial data change request.

[0109] Furthermore, after the first financial data table is modified, the data in the second financial data table is updated in the first financial data table; a target financial data modification request sent by the user who made the data modification is received; and the first financial data table is modified in accordance with the financial data modification request corresponding to the target financial data modification request.

[0110] Furthermore, after updating the data in the second financial data table to the first financial data table, the method for changing the fields of the financial data table further includes: deleting the second financial data table and the preset table.

[0111] By using this application, the loss of financial data can be avoided.

[0112] Based on the same inventive concept, this application also provides a field changing device for a financial data table corresponding to the field changing method of the financial data table. Since the principle of the device in this application is similar to the field changing method of the financial data table described above in this application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0113] Reference Figure 5 The diagram shown is a schematic of a field modification device for a financial data table provided in an embodiment of this application. The field modification device for the financial data table includes:

[0114] The receiving module 501 is used to receive field change requests for financial data tables sent by users who have changed fields; the field change requests contain a change table identifier;

[0115] Storage module 502 is used to store data from the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table;

[0116] The field modification module 503 is used to modify the fields in the first financial data table corresponding to the field modification request.

[0117] The receiving module 501 is also used to receive financial data change requests sent by users who have changed their data.

[0118] The financial data modification module 504 is used to modify the financial data in the second financial data table in accordance with the financial data modification request.

[0119] In one possible implementation, the field modification device for the financial data table further includes: a determination module 505;

[0120] The determination module 505 is used to determine the second financial data table corresponding to the first financial data table from a preset table; the preset table stores the corresponding identifiers of the first financial data table and the second financial data table.

[0121] In one possible implementation, the field modification device for the financial data table further includes: an update module 506;

[0122] The update module 506 is used to update the data in the second financial data table to the first financial data table after the first financial data table has been modified.

[0123] The receiving module 501 is also used to receive a target financial data change request sent by the user who changed the data.

[0124] The financial data modification module 504 is also used to modify the first financial data table in accordance with the target financial data modification request.

[0125] In one possible implementation, the field modification device for the financial data table further includes: a deletion module 507;

[0126] The deletion module 507 is used to delete the second financial data table and the preset table.

[0127] In one possible implementation, the field modification device for the financial data table further includes: a creation module 508;

[0128] The receiving module 501 is also used to receive the identifier of the second financial data table corresponding to the first financial data table sent by the user who changed the field.

[0129] Create module 508 to create a second financial data table identified as the second financial data table identifier;

[0130] The storage module 502 is also used to store the identifier corresponding to the first financial data table and the identifier corresponding to the second financial data table into a preset table.

[0131] This application provides a field modification device for a financial data table. The device includes: a receiving module 501 for receiving a field modification request for a financial data table sent by a user; the field modification request includes a modification table identifier; a storage module 502 for storing data from a first financial data table corresponding to the modification table identifier into a second financial data table corresponding to the first financial data table; a field modification module 503 for performing field modifications on the first financial data table corresponding to the field modification request; the receiving module 501 is also used to receive a financial data modification request sent by a user; and a financial data modification module 504 for performing financial data modifications on the second financial data table corresponding to the financial data modification request. This application avoids the loss of financial data by storing data from the first financial data table corresponding to the modification table identifier into the second financial data table corresponding to the first financial data table, and then performing financial data modifications on the second financial data table corresponding to the financial data modification request.

[0132] like Figure 6 As shown in the embodiment of this application, an electronic device 600 includes a processor 601, a memory 602, and a bus. The memory 602 stores machine-readable instructions that can be executed by the processor 601. When the electronic device is running, the processor 601 and the memory 602 communicate through the bus. The processor 601 executes the machine-readable instructions to perform the steps of the field modification method of the financial data table described above.

[0133] Specifically, the memory 602 and processor 601 mentioned above can be general-purpose memory and processor, without any specific limitations. When the processor 601 runs the computer program stored in the memory 602, it can execute the field modification method of the financial data table mentioned above.

[0134] Corresponding to the above-mentioned method for changing the fields of the financial data table, this application embodiment also provides a computer-readable storage medium storing a computer program, which, when run by a processor, executes the steps of the above-mentioned method for changing the fields of the financial data table.

[0135] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some communication interfaces; the indirect coupling or communication connection of devices or modules can be electrical, mechanical, or other forms.

[0136] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0137] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0138] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the information processing methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0139] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for modifying fields in a financial data table, characterized in that, The methods for changing fields in the financial data table include: Receive field change requests for financial data tables sent by users who have changed fields; the field change requests contain a change table identifier; The data in the first financial data table corresponding to the change table identifier is stored in the second financial data table corresponding to the first financial data table; the second financial data table is a candidate financial data table when the first financial data table needs to be modified; the first financial data table and the second financial data table have the same table structure. Perform field changes on the first financial data table corresponding to the field change request; and receive financial data change requests sent by users who are changing data. Make financial data changes to the second financial data table in accordance with the financial data change request; After the first financial data table is modified, the data in the second financial data table is updated in the first financial data table; the target financial data modification request sent by the user who made the data modification is received; and the financial data modification corresponding to the target financial data modification request is performed on the first financial data table. Before storing the data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table, the field modification method of the financial data table further includes: determining the second financial data table corresponding to the first financial data table in a preset table; the preset table stores the corresponding identifier of the first financial data table and the corresponding identifier of the second financial data table.

2. The method for changing fields in a financial data table according to claim 1, characterized in that, After updating the data in the second financial data table to the first financial data table, the method for changing the fields of the financial data table further includes: Delete the second financial data table and the preset table.

3. The method for changing fields in a financial data table according to claim 1 or 2, characterized in that, Before storing the data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table, the field modification method of the financial data table further includes: Receive the second financial data table identifier corresponding to the first financial data table sent by the user who changed the field; Create a second financial data table with the identifier of the second financial data table; The identifiers corresponding to the first financial data table and the second financial data table are stored in the preset table.

4. A field modification device for a financial data table, characterized in that, The field modification device for the financial data table includes: The receiving module is used to receive field change requests for financial data tables sent by users who have changed fields; the field change requests include a change table identifier; The storage module is used to store data from the first financial data table corresponding to the change table identifier into a second financial data table corresponding to the first financial data table; the second financial data table is a candidate financial data table when the first financial data table needs to undergo field changes; the first financial data table and the second financial data table have the same table structure. The field modification module is used to modify the fields in the first financial data table corresponding to the field modification request. The receiving module is also used to receive financial data change requests sent by users who have changed their data. The financial data modification module is used to modify the second financial data table in accordance with the financial data modification request. The update module is used to update the data in the second financial data table to the first financial data table after the first financial data table has been modified; the receiving module is also used to receive the target financial data modification request sent by the data modification user; the financial data modification module is also used to perform financial data modification on the first financial data table corresponding to the target financial data modification request. Before storing the data in the first financial data table corresponding to the change table identifier into the second financial data table corresponding to the first financial data table, the determining module is used to determine the second financial data table corresponding to the first financial data table in a preset table; the preset table stores the corresponding identifiers of the first financial data table and the second financial data table.

5. An electronic device, characterized in that, include: The device includes a processor, a storage medium, and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device is in operation, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the field modification method for a financial data table as described in any one of claims 1 to 3.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the field modification method for a financial data table as described in any one of claims 1 to 3.

Images