Information change record storage method and device, computer equipment, medium and product

Abstract

The invention relates to the technical field of customer information security, and particularly discloses an information change record storage method and device, computer equipment, a medium and a product. The method comprises the steps of determining the type of a first information change request according to first change data in response to the first information change request, and correspondingly storing the first change data and a first primary key value into a user information change table when the type of the first information change request indicates that the first information change request needs to be approved, and correspondingly storing the approval record identifier and the second primary key value in the user information change expansion table. Since the user information change table and the user information change expansion table have the same primary key, and the first primary key value and the second primary key value are the same, the approval information and the change record of the controlled customer information can be associated through the primary keys of the user information change table and the user information change expansion table, query information related to the change record is convenient to query, and the user experience is improved. And the convenience of querying the change record is improved.

Description

Technical Field

[0001] The present application relates to the technical field of customer information security, and in particular to an information change record storage method, device, computer equipment, medium and product. Background Art

[0002] The financial industry attaches great importance to the security of customer information. Therefore, any modification to customer information generally needs to be recorded. Usually, the information before and after the change is stored to keep a record of the change. For some controlled customer information with a higher degree of importance, a dedicated person is required to review and approve the change.

[0003] However, it is often difficult to associate the approval information of this part of the controlled customer information with the change record. Therefore, how to associate the approval information of the controlled customer information with the change record has become a technical problem to be solved in this field. Summary of the invention

[0004] Based on this, it is necessary to provide an information change record storage method, device, computer equipment, medium and product that can associate approval information and change records of controlled customer information in response to the above technical problems.

[0005] In a first aspect, the present application provides a method for storing information change records. The method comprises:

[0006] In response to a first information change request, determining a type of the first information change request according to the first change data, wherein the first information change request includes the first change data;

[0007] When the type of the first information change request indicates that the first information change request needs approval, the first change data is stored in a user information change table in correspondence with the first primary key value, and the approval record identifier is stored in a user information change extension table in correspondence with the second primary key value;

[0008] Among them, the primary key of the user information change table is the same as the primary key of the user information change extension table, and the first primary key value is the same as the second primary key value, and the approval record identifier is used to indicate the approval record corresponding to the first information change request.

[0009] In one embodiment, determining the type of the first information change request according to the first change data includes:

[0010] Determine a changed field corresponding to the first changed data;

[0011] If the change field is a controlled field, determining the type of the first information change request is that the first information change request requires approval;

[0012] If the change field is an uncontrolled field, it is determined that the type of the first information change request is that the first information change request does not require approval.

[0013] In one embodiment, the method further comprises:

[0014] If the type of the first information change request is that the first information change request does not require approval, the first change data is stored in the user information change table, and no data is stored in the user information change extension table.

[0015] In one embodiment, the method further comprises:

[0016] Determine the importance score of each field in the user information change table;

[0017] Determine the field whose importance score is greater than a preset threshold as the controlled field, and determine the field whose importance score is not greater than the preset threshold as the uncontrolled field;

[0018] The importance score of each field in the user information change table may be determined according to at least one of the following:

[0019] How often the field changes;

[0020] User attention to this field;

[0021] The degree of association between the field and other fields, where the other fields are other fields in the user information change table except the field;

[0022] The degree of security required for this field.

[0023] In one embodiment, the method further comprises:

[0024] In response to the information change query request, according to the information change query data, determining the first change data corresponding to the information change query data in the user information change table, and obtaining the first primary key value stored corresponding to the first change data, the information change query request including the information change query data;

[0025] If the user information change extension table includes the second primary key value that is the same as the first primary key value, then obtaining the approval record identifier stored corresponding to the second primary key value;

[0026] Get the approval record indicated by the approval record identifier.

[0027] In one embodiment, the method further comprises:

[0028] When it is determined based on the second change data that the second information change request to which the second change data belongs needs approval,

[0029] If the approval record identifier of the second information change request does not exist in the user information change extension table, a prompt message is displayed; the prompt message is used to indicate that the second information change request has not been approved.

[0030] In a second aspect, the present application also provides an information change record storage device. The device includes:

[0031] a first determining module, configured to, in response to a first information change request, determine a type of the first information change request according to the first change data, wherein the first information change request includes the first change data;

[0032] A first storage module is used to store the first change data and the first primary key value in a user information change table in correspondence with each other when the type of the first information change request indicates that the first information change request needs approval, and to store the approval record identifier and the second primary key value in a user information change extension table in correspondence with each other;

[0033] Among them, the primary key of the user information change table is the same as the primary key of the user information change extension table, and the first primary key value is the same as the primary key value, and the approval record identifier is used to indicate the approval record corresponding to the first information change request.

[0034] In a third aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of any of the above methods when executing the computer program.

[0035] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of any of the above methods when executed by a processor.

[0036] In a fifth aspect, the present application also provides a computer program product, including a computer program, which implements the steps of any of the above methods when executed by a processor.

[0037] The above-mentioned information change record storage method, device, computer equipment, medium and product, by responding to the first information change request, determine the type of the first information change request according to the first change data, and when the type of the first information change request indicates that the first information change request needs to be approved, store the first change data and the first primary key value in the user information change table in correspondence with each other, and store the approval record identifier and the second primary key value in the user information change extension table in correspondence with each other. Since in the embodiment of the present application, the primary key of the user information change table is the same as the primary key of the user information change extension table, and the first primary key value is the same as the second primary key value, it is possible to associate the approval information and change records of the controlled customer information through the primary key of the user information change table and the user information change extension table, so that users can query the query information related to the change record, which increases the convenience of change record query. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] FIG1 is an internal structure diagram of a computer device provided in an embodiment of the present application;

[0039] FIG2 is a flow chart of an information change record storage method provided in an embodiment of the present application;

[0040] 3 is a schematic flow chart of a method for determining the type of a first information change request provided in an embodiment of the present application;

[0041] FIG4 is a flow chart of a method for determining a controlled field according to an embodiment of the present application;

[0042] 5 is a flow chart of a method for querying change data and approval records provided in an embodiment of the present application;

[0043] 6 is a flow chart of a method for associating change data with approval records provided in an embodiment of the present application;

[0044] FIG. 7 is a structural block diagram of an information change record storage device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0046] The financial industry attaches great importance to the security of customer information. Therefore, any modification to customer information generally needs to be recorded. Usually, the information before and after the change is stored to keep a record of the change. For some controlled customer information with a higher degree of importance, a dedicated person is required to review and approve the change.

[0047] However, it is often difficult to associate the approval information of this part of the controlled customer information with the change record. Therefore, how to associate the approval information of the controlled customer information with the change record has become a technical problem to be solved in this field.

[0048] The information change record storage method provided in the embodiment of the present application can be applied in the application environment as shown in Figure 1. Figure 1 is an internal structure diagram of a computer device provided in the embodiment of the present application. The computer device can be a server, and its internal structure diagram can be as shown in Figure 1. The computer device includes a processor, a memory, and a network interface connected via a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, an information change record storage method is implemented.

[0049] Those skilled in the art will understand that the structure shown in FIG. 1 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0050] In one embodiment, as shown in FIG. 2 , FIG. 2 is a flow chart of an information change record storage method provided in an embodiment of the present application, and the method can be applied to the computer device in FIG. 1 , and the method includes the following steps:

[0051] S201, in response to a first information change request, determining a type of the first information change request according to first change data.

[0052] The first information change request includes first change data.

[0053] Exemplarily, when user information changes, a first information change request may be initiated, and then in response to the first information change request, first change data in the first information change request may be obtained, and then the type of the first information change request may be determined based on the first change data.

[0054] Optionally, the type of the first information change request may include, for example, the first information change request requiring approval and the first information change request not requiring approval.

[0055] Alternatively, the type of the first information change request may also include, for example, adding user information, deleting user information, modifying user information, and querying user information. When the type of the first information change request is adding user information or querying user information, it indicates that the first information change request does not require approval; when the type of the first information change request is deleting user information or modifying user information, it indicates that the first information change request requires approval.

[0056] Alternatively, the type of the first information change request may also include, for example, a controlled user's information change and an uncontrolled user's information change. When the type of the first information change request is a controlled user's information change, it indicates that the first information change request needs approval; when the type of the first information change request is an uncontrolled user's information change, it indicates that the first information change request does not need approval.

[0057] S202, when the type of the first information change request indicates that the first information change request requires approval, the first change data and the first primary key value are stored in the user information change table in correspondence, and the approval record identifier and the second primary key value are stored in the user information change extension table in correspondence.

[0058] Among them, the primary key of the user information change table is the same as the primary key of the user information change extension table, and the first primary key value is the same as the second primary key value, and the approval record identifier is used to indicate the approval record corresponding to the first information change request.

[0059] In one embodiment, when the type of the first information change request indicates that the first information change request requires approval, the first change data and the first primary key value are stored in the user information change table in correspondence with each other. It should be noted that the first change data may include the first primary key value, or the first primary key value may be data independent of the first change data.

[0060] The first primary key value is the key value of the first primary key of the user information change table.

[0061] Exemplarily, the first primary key may be a serial number of the information change request, and the first primary key value is a self-increasing serial number value, and the first primary key value is data independent of the first change data.

[0062] Alternatively, the first primary key may be the change time in the first change data, and the first change data includes the first primary key value.

[0063] In an embodiment of the present application, the primary key of the user information change table is the same as the primary key of the user information change extension table. For example, when the first primary key of the user information change table is the serial number of the information change request, the second primary key of the user information change extension table is also the serial number of the information change request.

[0064] In addition, the first primary key value is the same as the second primary key value. Exemplarily, when the first primary key value is the change time in the first change data, the second primary key value is also the change time in the first change data.

[0065] In one embodiment, the approval record identifier may be at least one of the storage address, serial number, approval time, etc. of the approval record. It should be noted that the approval record identifier is a unique identifier of the approval record corresponding to the first information change request, that is, one approval record identifier is only used to indicate one approval record.

[0066] In the embodiment of the present application, by responding to the first information change request, the type of the first information change request is determined according to the first change data. When the type of the first information change request indicates that the first information change request needs approval, the first change data is stored in the user information change table corresponding to the first primary key value, and the approval record identifier is stored in the user information change extension table corresponding to the second primary key value. Since in the embodiment of the present application, the primary key of the user information change table is the same as the primary key of the user information change extension table, and the first primary key value is the same as the second primary key value, it is possible to associate the approval information and change records of the controlled customer information through the primary key of the user information change table and the user information change extension table, so that users can query the query information related to the change record, which increases the convenience of querying the change record.

[0067] Referring to FIG. 3 , FIG. 3 is a flow chart of a method for determining the type of a first information change request provided in an embodiment of the present application. This embodiment relates to a possible implementation method of how to determine the type of the first information change request based on the first change data. Based on the above embodiment, the above S201 includes the following steps:

[0068] S301: Determine a changed field corresponding to first changed data.

[0069] In the embodiment of the present application, the change field corresponding to the first change data is the data item that is modified or updated during the information change process.

[0070] S302: If the changed field is a controlled field, determine that the type of the first information change request is that the first information change request requires approval.

[0071] In the embodiment of the present application, the types of the first information change request include the first information change request requiring approval and the first information change request not requiring approval.

[0072] In a possible implementation, the user may preset a controlled field according to actual needs, and when the change field corresponding to the first change data is a controlled field, the type of the first information change request is determined to be that the first information change request requires approval.

[0073] Alternatively, in another possible implementation, it is also possible to determine whether a changed field is a controlled field based on the frequency of field changes, user attention to the field, the degree of association between the field and other fields, the degree of security requirements for the field, etc.

[0074] Exemplarily, if the change frequency of the change field is greater than the preset frequency, the change field is determined to be a controlled field, and the type of the first information change request is determined to be a first information change request requiring approval; or, if the user attention of the change field is greater than the preset attention, the change field is determined to be a controlled field, and the type of the first information change request is determined to be a first information change request requiring approval; or, if the degree of association between the change field and other fields is greater than the preset degree of association, the change field is determined to be a controlled field, and the type of the first information change request is determined to be a first information change request requiring approval; or, if the security requirement degree of the change field is greater than the preset security requirement degree, the change field is determined to be a controlled field, and the type of the first information change request is determined to be a first information change request requiring approval.

[0075] S303: If the changed field is a non-controlled field, determine that the type of the first information change request is that the first information change request does not require approval.

[0076] Optionally, the user can preset controlled fields according to actual needs, and the fields not set as controlled fields are uncontrolled fields. When the change field corresponding to the first change data is an uncontrolled field, the type of the first information change request is determined as the first information change request does not require approval.

[0077] In an embodiment of the present application, the change field corresponding to the first change data is determined. If the change field is a controlled field, the type of the first information change request is determined to be a first information change request requiring approval; if the change field is an uncontrolled field, the type of the first information change request is determined to be a first information change request that does not require approval. In this way, the type of the information change request can be determined according to the change field, so that the change data can be stored in different data tables according to different types of information change requests, thereby improving the flexibility of information change record storage.

[0078] Based on the above embodiment, the method further includes the following steps:

[0079] If the type of the first information change request is that the first information change request does not require approval, the first change data is stored in the user information change table, and the data is not stored in the user information change extension table.

[0080] In one embodiment, if the type of the first information change request is that the first information change request does not require approval, the first change data only needs to be stored in the user information change table, and when the first information change request does not require approval, there will be no approval record, so there is no need to store data in the user information change extension table.

[0081] In an embodiment of the present application, if the type of the first information change request is that the first information change request does not require approval, the first change data is stored in the user information change table, and the data is not stored in the user information change extension table. This can simplify the storage operation when the first information change request does not require approval, improve the storage efficiency of the information change record, and save storage resources.

[0082] Referring to Figure 4, Figure 4 is a flow chart of a method for determining a controlled field provided in an embodiment of the present application. Based on the above embodiment, the method further includes the following steps:

[0083] S401, determining the importance score of each field in the user information change table.

[0084] Optionally, the importance score of each field in the user information change table can be determined based on at least one of the following: the frequency of field changes, the user attention to the field, the degree of association between the field and other fields, and the degree of security requirements for the field. Among them, other fields are fields other than the field in the user information change table.

[0085] In a possible implementation, weights may be set respectively for the frequency of field changes, the user attention to the field, the degree of association between the field and other fields, and the degree of security requirements for the field. Then, a weighted sum is performed based on the frequency of field changes, the user attention to the field, the degree of association between the field and other fields, the degree of security requirements for the field, and each weight, and the sum result is determined as the importance score of the field.

[0086] In another possible implementation, the frequency of field changes may be determined as the importance score of the field; or, the user attention to the field may be determined as the importance score of the field; or, the degree of association between the field and other fields may be determined as the importance score of the field; or, the degree of security requirements for the field may be determined as the importance score of the field.

[0087] S402: Determine a field whose importance score is greater than a preset threshold as a controlled field, and determine a field whose importance score is not greater than the preset threshold as an uncontrolled field.

[0088] In one embodiment, a preset threshold may be set according to actual needs, and fields with importance scores greater than the preset threshold may be determined as controlled fields, and fields with importance scores less than the preset threshold may be determined as uncontrolled fields.

[0089] In an embodiment of the present application, the importance score of each field in the user information change table is determined, and the fields with an importance score greater than a preset threshold are determined as controlled fields, and the fields with an importance score not greater than the preset threshold are determined as uncontrolled fields. This allows the type of information change request to be determined based on the change field, so that the change data can be stored in different data tables according to different types of information change requests, thereby improving the flexibility of information change record storage.

[0090] Referring to Figure 5, Figure 5 is a flow chart of a method for querying change data and approval records provided by an embodiment of the present application. Based on the above embodiment, the method further includes the following steps:

[0091] S501, in response to an information change query request, determining first change data corresponding to the information change query data in a user information change table according to the information change query data, and obtaining a first primary key value stored corresponding to the first change data.

[0092] The information change query request includes information change query data.

[0093] Exemplarily, if the information change query data is the time of information change, the first change data corresponding to the time of the information change is determined in the user information change table, and then the first primary key value stored corresponding to the first change data is obtained.

[0094] S502: If the user information change extension table includes a second primary key value that is the same as the first primary key value, then obtain an approval record identifier stored corresponding to the second primary key value.

[0095] In a possible implementation, if the user information change extension table includes a second primary key value that is the same as the first primary key value, it means that there is an approval record corresponding to the first change data, and then the approval record identifier stored corresponding to the second primary key value is obtained.

[0096] Optionally, if there is no second primary key value that is the same as the first primary key value in the user information change extension table, the returned query result is empty.

[0097] S503: Acquire the approval record indicated by the approval record identifier.

[0098] Since the approval record identifier is a unique identifier of the approval record corresponding to the first information change request, the corresponding approval record can be obtained according to the approval record identifier.

[0099] Exemplarily, if the approval record identifier is a storage address of the approval record, the corresponding approval record can be obtained according to the storage address.

[0100] In a possible implementation, after the first change data or the approval record corresponding to the information change query data is acquired, the first change data or the approval record may be displayed for the user to view.

[0101] In an embodiment of the present application, in response to an information change query request, based on the information change query data, first change data corresponding to the information change query data is determined in the user information change table, and a first primary key value stored corresponding to the first change data is obtained. If the user information change table includes a second primary key value that is the same as the first primary key value, an approval record identifier stored corresponding to the second primary key value is obtained, and then the approval record indicated by the approval record identifier is obtained, so that the approval record corresponding to the information change record can be queried when the information change record is queried, which simplifies the operation of the approval record query and facilitates the synchronous management and analysis of the information change record and the corresponding approval record.

[0102] Based on the above embodiment, the method further includes the following steps:

[0103] When it is determined based on the second change data that the second information change request to which the second change data belongs requires approval, if there is no approval record identifier for the second information change request in the user information change extension table, a prompt message is displayed; the prompt message is used to indicate that the second information change request has not been approved.

[0104] In one embodiment, the change data stored in the user information change table can be checked. If it is determined based on the second change data that the second information change request to which the second change data belongs needs to be approved, it indicates that the approval record identifier corresponding to the second change data should be stored in the user information change extension table. At this time, if the approval record identifier of the second information change request does not exist in the user information change extension table, a prompt message is displayed to indicate that the second information change request has not been approved, or that the approval status of the second information change request is abnormal, thereby improving the accuracy of the information change record storage and reducing the probability of errors in the storage of information change records and approval records.

[0105] Referring to FIG. 6 , FIG. 6 is a flow chart of a method for associating change data with approval records provided in an embodiment of the present application. The method comprises the following steps:

[0106] S601: In response to a first information change request, determine a type of the first information change request according to first change data.

[0107] S602, when the type of the first information change request indicates that the first information change request requires approval, the first change data and the first primary key value are stored in the user information change table in correspondence, and the approval record identifier and the second primary key value are stored in the user information change extension table in correspondence.

[0108] S603: If the type of the first information change request is that the first information change request does not require approval, the first change data is stored in the user information change table, and the data is not stored in the user information change extension table.

[0109] S604, in response to the information change query request, determine first change data corresponding to the information change query data in the user information change table according to the information change query data, and obtain a first primary key value stored corresponding to the first change data.

[0110] S605: If the user information change extension table includes a second primary key value that is the same as the first primary key value, obtain the approval record identifier stored corresponding to the second primary key value.

[0111] S606: Acquire the approval record indicated by the approval record identifier.

[0112] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0113] Based on the same inventive concept, the embodiment of the present application also provides an information change record storage device for implementing the information change record storage method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more information change record storage device embodiments provided below can refer to the limitations of the information change record storage method above, and will not be repeated here.

[0114] In one embodiment, as shown in FIG. 7 , FIG. 7 is a structural block diagram of an information change record storage device provided in an embodiment of the present application, and the device 700 includes:

[0115] The first determination module 701 is configured to determine, in response to a first information change request, a type of the first information change request according to first change data, wherein the first information change request includes the first change data.

[0116] The first storage module 702 is used to store the first change data and the first primary key value in the user information change table in correspondence with each other when the type of the first information change request indicates that the first information change request requires approval, and to store the approval record identifier and the second primary key value in the user information change extension table in correspondence with each other.

[0117] Among them, the primary key of the user information change table is the same as the primary key of the user information change extension table, and the first primary key value is the same as the second primary key value, and the approval record identifier is used to indicate the approval record corresponding to the first information change request.

[0118] In one embodiment, the first determining module 701 includes:

[0119] The first determining unit is configured to determine a changed field corresponding to the first changed data.

[0120] The second determining unit is configured to determine, if the changed field is a controlled field, that the type of the first information change request is that the first information change request requires approval.

[0121] The third determining unit is configured to determine, if the changed field is an uncontrolled field, that the type of the first information change request is that the first information change request does not require approval.

[0122] In one embodiment, the apparatus 700 further includes:

[0123] The second storage module is used to store the first change data in the user information change table and not store the data in the user information change extension table if the type of the first information change request is that the first information change request does not require approval.

[0124] In one embodiment, the apparatus 700 further includes:

[0125] The second determination module is used to determine the importance score of each field in the user information change table.

[0126] The third determination module is used to determine a field whose importance score is greater than a preset threshold as a controlled field, and to determine a field whose importance score is not greater than the preset threshold as an uncontrolled field.

[0127] Among them, the importance score of each field in the user information change table can be determined based on at least one of the following: the frequency of field changes; the user attention to the field; the degree of association between the field and other fields, where other fields are fields other than the field in the user information change table; the security requirement level of the field.

[0128] In one embodiment, the apparatus 700 further includes:

[0129] The first acquisition module is used to respond to the information change query request, determine the first change data corresponding to the information change query data in the user information change table according to the information change query data, and obtain the first primary key value stored corresponding to the first change data; wherein the information change query request includes the information change query data.

[0130] The second acquisition module is used to acquire the approval record identifier stored corresponding to the second primary key value if the user information change extension table includes a second primary key value that is the same as the first primary key value.

[0131] The third acquisition module is used to acquire the approval record indicated by the approval record identifier.

[0132] In one embodiment, the apparatus 700 further includes:

[0133] The display module is used to display a prompt message when it is determined based on the second change data that the second information change request to which the second change data belongs needs to be approved, if there is no approval record identifier for the second information change request in the user information change extension table; the prompt message is used to indicate that the second information change request has not been approved.

[0134] Each module in the above-mentioned information change record storage device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0135] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0136] In response to the first information change request, determining a type of the first information change request according to the first change data, wherein the first information change request includes the first change data;

[0137] When the type of the first information change request indicates that the first information change request requires approval, the first change data and the first primary key value are stored in the user information change table in correspondence, and the approval record identifier and the second primary key value are stored in the user information change extension table in correspondence;

[0138] Among them, the primary key of the user information change table is the same as the primary key of the user information change extension table, and the first primary key value is the same as the second primary key value, and the approval record identifier is used to indicate the approval record corresponding to the first information change request.

[0139] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0140] Determine a change field corresponding to the first change data;

[0141] If the changed field is a controlled field, determining the type of the first information change request is that the first information change request requires approval;

[0142] If the changed field is an uncontrolled field, it is determined that the type of the first information change request is that the first information change request does not require approval.

[0143] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0144] If the type of the first information change request is that the first information change request does not require approval, the first change data is stored in the user information change table, and the data is not stored in the user information change extension table.

[0145] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0146] Determine the importance score of each field in the user information change table;

[0147] Determine a field whose importance score is greater than a preset threshold as a controlled field, and determine a field whose importance score is not greater than the preset threshold as an uncontrolled field;

[0148] The importance score of each field in the user information change table may be determined based on at least one of the following:

[0149] Frequency of field changes;

[0150] User attention to the field;

[0151] The degree of association between the field and other fields. Other fields are fields other than the field in the user information change table.

[0152] The degree of security required for the field.

[0153] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0154] In response to the information change query request, according to the information change query data, determine the first change data corresponding to the information change query data in the user information change table, and obtain the first primary key value stored corresponding to the first change data; wherein the information change query request includes the information change query data;

[0155] If the user information change extension table includes a second primary key value that is the same as the first primary key value, then obtaining the approval record identifier stored corresponding to the second primary key value;

[0156] Gets the approval record indicated by the approval record ID.

[0157] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0158] When it is determined based on the second change data that the second information change request to which the second change data belongs requires approval, if there is no approval record identifier for the second information change request in the user information change extension table, a prompt message is displayed; the prompt message is used to indicate that the second information change request has not been approved.

[0159] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0160] In response to the first information change request, determining a type of the first information change request according to the first change data, wherein the first information change request includes the first change data;

[0161] When the type of the first information change request indicates that the first information change request requires approval, the first change data and the first primary key value are stored in the user information change table in correspondence, and the approval record identifier and the second primary key value are stored in the user information change extension table in correspondence;

[0162] Among them, the primary key of the user information change table is the same as the primary key of the user information change extension table, and the first primary key value is the same as the second primary key value, and the approval record identifier is used to indicate the approval record corresponding to the first information change request.

[0163] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0164] Determine a change field corresponding to the first change data;

[0165] If the changed field is a controlled field, determining the type of the first information change request is that the first information change request requires approval;

[0166] If the changed field is an uncontrolled field, it is determined that the type of the first information change request is that the first information change request does not require approval.

[0167] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0168] If the type of the first information change request is that the first information change request does not require approval, the first change data is stored in the user information change table, and the data is not stored in the user information change extension table.

[0169] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0170] Determine the importance score of each field in the user information change table;

[0171] Determine a field whose importance score is greater than a preset threshold as a controlled field, and determine a field whose importance score is not greater than the preset threshold as an uncontrolled field;

[0172] The importance score of each field in the user information change table may be determined based on at least one of the following:

[0173] Frequency of field changes;

[0174] User attention to the field;

[0175] The degree of association between the field and other fields. Other fields are fields other than the field in the user information change table.

[0176] The degree of security required for the field.

[0177] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0178] In response to the information change query request, according to the information change query data, determine the first change data corresponding to the information change query data in the user information change table, and obtain the first primary key value stored corresponding to the first change data; wherein the information change query request includes the information change query data;

[0179] If the user information change extension table includes a second primary key value that is the same as the first primary key value, then obtaining the approval record identifier stored corresponding to the second primary key value;

[0180] Gets the approval record indicated by the approval record ID.

[0181] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0182] When it is determined based on the second change data that the second information change request to which the second change data belongs needs to be approved,

[0183] If the approval record identifier of the second information change request does not exist in the user information change extension table, a prompt message is displayed; the prompt message is used to indicate that the second information change request has not been approved.

[0184] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0185] In response to the first information change request, determining a type of the first information change request according to the first change data, wherein the first information change request includes the first change data;

[0186] When the type of the first information change request indicates that the first information change request requires approval, the first change data and the first primary key value are stored in the user information change table in correspondence, and the approval record identifier and the second primary key value are stored in the user information change extension table in correspondence;

[0187] Among them, the primary key of the user information change table is the same as the primary key of the user information change extension table, and the first primary key value is the same as the second primary key value, and the approval record identifier is used to indicate the approval record corresponding to the first information change request.

[0188] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0189] Determine a change field corresponding to the first change data;

[0190] If the changed field is a controlled field, determining the type of the first information change request is that the first information change request requires approval;

[0191] If the changed field is an uncontrolled field, it is determined that the type of the first information change request is that the first information change request does not require approval.

[0192] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0193] If the type of the first information change request is that the first information change request does not require approval, the first change data is stored in the user information change table, and the data is not stored in the user information change extension table.

[0194] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0195] Determine the importance score of each field in the user information change table;

[0196] Determine a field whose importance score is greater than a preset threshold as a controlled field, and determine a field whose importance score is not greater than the preset threshold as an uncontrolled field;

[0197] The importance score of each field in the user information change table may be determined based on at least one of the following:

[0198] Frequency of field changes;

[0199] User attention to the field;

[0200] The degree of association between the field and other fields. Other fields are fields other than the field in the user information change table.

[0201] The degree of security required for the field.

[0202] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0203] In response to the information change query request, according to the information change query data, determine the first change data corresponding to the information change query data in the user information change table, and obtain the first primary key value stored corresponding to the first change data; wherein the information change query request includes the information change query data;

[0204] If the user information change extension table includes a second primary key value that is the same as the first primary key value, then obtaining the approval record identifier stored corresponding to the second primary key value;

[0205] Gets the approval record indicated by the approval record ID.

[0206] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0207] When it is determined based on the second change data that the second information change request to which the second change data belongs needs to be approved,

[0208] If there is no approval record mark for the second information change request in the user information change extension table, a prompt message is displayed; the prompt message is used to indicate that the second information change request has not been approved. It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0209] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0210] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0211] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for storing information change records, characterized in that: The method comprises: In response to a first information change request, determining a type of the first information change request according to first change data, wherein the first information change request includes the first change data; When the type of the first information change request indicates that the first information change request requires approval, the first change data is stored in a user information change table in correspondence with the first primary key value, and the approval record identifier is stored in a user information change extension table in correspondence with the second primary key value; Among them, the primary key of the user information change table is the same as the primary key of the user information change extension table, and the first primary key value is the same as the second primary key value, and the approval record identifier is used to indicate the approval record corresponding to the first information change request.

2. The method according to claim 1, characterized in that The determining, according to the first change data, the type of the first information change request includes: Determining a change field corresponding to the first change data; If the change field is a controlled field, determining the type of the first information change request is that the first information change request requires approval; If the change field is an uncontrolled field, it is determined that the type of the first information change request is that the first information change request does not require approval.

3. The method according to claim 2, characterized in that The method further comprises: If the type of the first information change request is that the first information change request does not require approval, the first change data is stored in the user information change table, and no data is stored in the user information change extension table.

4. The method according to claim 2, characterized in that: The method further comprises: Determine the importance score of each field in the user information change table; Determine the fields whose importance scores are greater than a preset threshold as the controlled fields, and determine the fields whose importance scores are not greater than the preset threshold as the uncontrolled fields; The importance score of each field in the user information change table may be determined according to at least one of the following: the frequency of changes to the field; User attention to the field; The degree of association between the field and other fields, where the other fields are other fields in the user information change table except the field; The degree of security required for the field.

5. The method according to claim 1, characterized in that The method further comprises: In response to the information change query request, according to the information change query data, determining the first change data corresponding to the information change query data in the user information change table, and obtaining the first primary key value stored corresponding to the first change data; wherein the information change query request includes the information change query data; If the user information change extension table includes the second primary key value that is the same as the first primary key value, then obtaining the approval record identifier stored corresponding to the second primary key value; Acquire the approval record indicated by the approval record identifier.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: When it is determined based on the second change data that the second information change request to which the second change data belongs needs approval, If the approval record identifier of the second information change request does not exist in the user information change extension table, a prompt message is displayed; the prompt message is used to indicate that the second information change request has not been approved.

7. An information change record storage device, characterized in that: The device comprises: A first determining module, configured to determine, in response to a first information change request, a type of the first information change request according to first change data, wherein the first information change request includes the first change data; A first storage module is used to store the first change data and the first primary key value in a user information change table in correspondence with each other, and store the approval record identifier and the second primary key value in a user information change extension table in correspondence with each other when the type of the first information change request indicates that the first information change request needs approval; Among them, the primary key of the user information change table is the same as the primary key of the user information change extension table, and the first primary key value is the same as the second primary key value, and the approval record identifier is used to indicate the approval record corresponding to the first information change request.

8. The device according to claim 7, characterized in that The first determining module comprises: A first determining unit, configured to determine a changed field corresponding to the first changed data; a second determining unit, configured to determine, if the change field is a controlled field, that the type of the first information change request is that the first information change request requires approval; The third determining unit is configured to determine, if the changed field is an uncontrolled field, that the type of the first information change request is that the first information change request does not require approval.

9. The device according to claim 8, characterized in that The device also includes: The second storage module is used to store the first change data in the user information change table and not store data in the user information change extension table if the type of the first information change request is that the first information change request does not require approval.

10. The device according to claim 8, characterized in that The device also includes: A second determination module is used to determine the importance score of each field in the user information change table; A third determination module, configured to determine a field whose importance score is greater than a preset threshold as the controlled field, and to determine a field whose importance score is not greater than the preset threshold as the uncontrolled field; The importance score of each field in the user information change table may be determined according to at least one of the following: the frequency of changes to the field; User attention to the field; The degree of association between the field and other fields, where the other fields are other fields in the user information change table except the field; The degree of security required for the field.

11. The device according to claim 7, characterized in that The device also includes: A first acquisition module is used to respond to the information change query request, determine the first change data corresponding to the information change query data in the user information change table according to the information change query data, and acquire the first primary key value stored corresponding to the first change data; wherein the information change query request includes the information change query data; A second acquisition module, configured to acquire the approval record identifier stored corresponding to the second primary key value if the user information change extension table includes the second primary key value that is the same as the first primary key value; The third acquisition module is used to acquire the approval record indicated by the approval record identifier.

12. The device according to any one of claims 7 to 11, characterized in that: The device also includes: The display module is used for, when it is determined based on the second change data that the second information change request to which the second change data belongs needs to be approved, If the approval record identifier of the second information change request does not exist in the user information change extension table, a prompt message is displayed; the prompt message is used to indicate that the second information change request has not been approved.

13. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images