CN112131240B - Dirty data processing method and device, storage medium and electronic equipment - Google Patents
Dirty data processing method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN112131240B CN112131240B CN202011069883.3A CN202011069883A CN112131240B CN 112131240 B CN112131240 B CN 112131240B CN 202011069883 A CN202011069883 A CN 202011069883A CN 112131240 B CN112131240 B CN 112131240B
- Authority
- CN
- China
- Prior art keywords
- data
- target
- field
- target field
- value
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Health & Medical Sciences (AREA)
- Databases & Information Systems (AREA)
- Health & Medical Sciences (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Bioethics (AREA)
- Medical Informatics (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a dirty data processing method and device, a storage medium and electronic equipment. Wherein the method comprises the following steps: and triggering to execute a first meta-table operation when a first target field in the target data table is requested to be modified, detecting whether the first target field belongs to sensitive data or not when the first meta-table operation is executed to detect that the first target field is dirty data, and writing the first target field into a dirty data list when the first target field is not sensitive data. The invention solves the technical problem of lower efficiency of the detection mode of the dirty data in the related technology.
Description
Technical Field
The present invention relates to the field of computers, and in particular, to a method and apparatus for processing dirty data, a storage medium, and an electronic device.
Background
In the related art, the processing of dirty data is usually written into the database in a timed and indiscriminate manner, for example, after reaching a preset time node, all data is written into the database, wherein the written data contains partial data which is not dirty data besides the dirty data, for example, sensitive data, because the accuracy requirement of the sensitive data is higher, the data cannot be checked and written through a timer, and the processing of the sensitive data is required to be manually executed, thus the technical problem of low efficiency of the detection mode of the dirty data is caused.
In view of the above problems, no effective solution has been proposed at present.
Disclosure of Invention
The embodiment of the invention provides a method and a device for processing dirty data, a storage medium and electronic equipment, which are used for at least solving the technical problem of low efficiency of a detection mode of the dirty data in the related technology.
According to an aspect of an embodiment of the present invention, there is provided a method for processing dirty data, including: triggering execution of a first meta-table operation in the case that a first target field in a target data table is requested to be modified, wherein the first meta-table operation is set to be triggered to be executed when the field in the target data table is requested to be modified, and the first meta-table operation is used for detecting whether the field in the target data table, which is requested to be modified, is dirty data or not; detecting whether the first target field belongs to sensitive data or not under the condition that the first meta-table operation is executed to detect that the first target field is dirty data; and writing the first target field into a dirty data list in the case that the first target field is not the sensitive data.
Optionally, the triggering performs a first table operation, including: detecting, by the first meta-table operation, whether a new value of the first target field after the modification is the same as an original value of the first target field before the modification; the first target field is marked as the dirty data if the new value of the first target field is different from the original value of the first target field.
Optionally, in a case that a first target field in the target data table is requested to be modified, triggering execution of the first meta-table operation includes: and triggering to execute the first meta-table operation under the condition that the value of the first target field is requested to be changed into a new value and the first target field is in a first data sub-table in the target data table.
Optionally, the method further comprises: setting the value of the first target field in the first data sub-table in the target data table to be the new value when the new value is not of the data table type; setting a second data sub-table in the first data sub-table, setting the first target field in the second data sub-table, and setting the value of the first target field in the second data sub-table as the new value when the new value is of the data table type.
Optionally, before the triggering to perform the first table operation, the method further includes: and setting the first data sub-table in an original data table in response to the acquired operation instruction, and setting the first target field in the original data table in the first data sub-table to obtain the target data table.
Optionally, the method further comprises: triggering execution of a second sub-table operation in the case that a second target field is requested to be accessed and the second target field is in a third data sub-table in the target data table, wherein the second sub-table operation is set to be triggered to be executed when a field in the target data table is accessed, and is used for querying a value of the second target field; and returning the value of the second target field in the third data sub-table obtained by executing the second table operation.
Optionally, the method further comprises: and writing the target data into a target database under the condition that the first target field is the sensitive data.
Optionally, the method further comprises: acquiring a first login instruction from a target application, wherein the first login instruction is used for requesting to login the target application by using a first account; under the condition that the first account is a newly created account, acquiring a first field with a value corresponding to the first account as an initialization value, and obtaining a first data table comprising the first field; and setting a fourth data sub-table in the first data table in response to the acquired operation instruction, and setting the first field in the first data table in the fourth data sub-table to obtain the target data table.
Optionally, the method further comprises: acquiring a second login instruction from a target application, wherein the second login instruction is used for requesting to login the target application by using a second account; under the condition that the second account is not a newly created account, acquiring a second field with the current value corresponding to the second account from a database to obtain a second data table comprising the second field; and setting a fifth data sub-table in the second data table in response to the acquired operation instruction, and setting the second field in the second data table in the fifth data sub-table to obtain the target data table.
According to another aspect of the embodiment of the present invention, there is also provided a device for processing dirty data, including:
a triggering module, configured to trigger, in a case where a first target field in a target data table is requested to be modified, to perform a first table operation, where the first table operation is configured to be triggered to be performed when a field in the target data table is requested to be modified, and the first table operation is configured to detect whether the field in the target data table, in which modification is requested, is dirty data;
The detection module is used for detecting whether the first target field belongs to sensitive data or not under the condition that the first table operation is executed to detect that the first target field is dirty data;
and the writing module is used for writing the first target field into a dirty data list when the first target field is not the sensitive data.
Optionally, the triggering module includes: a detection unit, configured to detect, through the first table operation, whether a new value of the first target field after the modification is the same as an original value of the first target field before the modification; and the marking unit is used for marking the first target field as the dirty data when the new value of the first target field is different from the original value of the first target field.
Optionally, the triggering module includes: and the triggering unit is used for triggering and executing the first meta-table operation under the condition that the value of the first target field is requested to be changed into a new value and the first target field is in a first data sub-table in the target data table.
Optionally, the device is further configured to: setting the value of the first target field in the first data sub-table in the target data table to be the new value when the new value is not of the data table type; setting a second data sub-table in the first data sub-table, setting the first target field in the second data sub-table, and setting the value of the first target field in the second data sub-table as the new value when the new value is of the data table type.
Optionally, the device is further configured to: before the trigger executes the first meta-table operation, responding to the acquired operation instruction, setting the first data sub-table in an original data table, and setting the first target field in the original data table in the first data sub-table to obtain the target data table.
Optionally, the device is further configured to: triggering execution of a second sub-table operation in the case that a second target field is requested to be accessed and the second target field is in a third data sub-table in the target data table, wherein the second sub-table operation is set to be triggered to be executed when a field in the target data table is accessed, and is used for querying a value of the second target field; and returning the value of the second target field in the third data sub-table obtained by executing the second table operation.
Optionally, the device is further configured to: and writing the target data into a target database under the condition that the first target field is the sensitive data.
Optionally, the device is further configured to: acquiring a first login instruction from a target application, wherein the first login instruction is used for requesting to login the target application by using a first account; under the condition that the first account is a newly created account, acquiring a first field with a value corresponding to the first account as an initialization value, and obtaining a first data table comprising the first field; and setting a fourth data sub-table in the first data table in response to the acquired operation instruction, and setting the first field in the first data table in the fourth data sub-table to obtain the target data table.
Optionally, the device is further configured to: acquiring a second login instruction from a target application, wherein the second login instruction is used for requesting to login the target application by using a second account; under the condition that the second account is not a newly created account, acquiring a second field with the current value corresponding to the second account from a database to obtain a second data table comprising the second field; and setting a fifth data sub-table in the second data table in response to the acquired operation instruction, and setting the second field in the second data table in the fifth data sub-table to obtain the target data table.
According to yet another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium having a computer program stored therein, wherein the computer program is configured to perform the above-described dirty data processing method when run.
According to still another aspect of the embodiments of the present invention, there is also provided an electronic device including a memory in which a computer program is stored, and a processor configured to execute the above-described dirty data processing method by the computer program.
In the embodiment of the invention, the first meta-table operation is triggered to be executed under the condition that the first target field in the target data table is requested to be modified, the technical scheme that whether the first target field belongs to sensitive data is detected under the condition that the first meta-table operation is executed to detect that the first target field is the dirty data is adopted, and the first target field is written into the dirty data list under the condition that the first target field is not sensitive data is adopted.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:
FIG. 1 is a schematic illustration of an application environment of an alternative dirty data processing method according to an embodiment of the present application;
FIG. 2 is a flow chart of a method for processing dirty data according to an embodiment of the present application;
FIG. 3 is a schematic view of an application scenario of a method for processing dirty data according to an embodiment of the present application;
FIG. 4 is a schematic view of an application scenario of another method for processing dirty data according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a method of processing dirty data according to an embodiment of the present application;
FIG. 6 is a schematic diagram of another method of processing dirty data according to an embodiment of the present application;
FIG. 7 is a flow chart of another method for processing dirty data according to an embodiment of the present application;
FIG. 8 is a flow chart of yet another method for processing dirty data according to an embodiment of the present application;
FIG. 9 is a flow chart of yet another method for processing dirty data according to an embodiment of the present application;
FIG. 10 is a flow chart of yet another method for processing dirty data according to an embodiment of the present invention;
FIG. 11 is a schematic diagram of an alternative dirty data processing apparatus according to an embodiment of the present invention;
fig. 12 is a schematic structural view of an alternative electronic device according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
First, partial terms or terminology appearing in the course of describing the embodiments of the application are applicable to the following explanation:
lua: an open-source, compact, extensible, and efficient weakly typed interpreted scripting language. Implementation complies with the C standard, which runs on almost all platforms (windows, linux, OS X, android, iOS, playStation, XBox, wii, etc.).
Metadata: meta-tables in Lua language, which are ordinary Lua tables, define the behavior of the original values under certain specific operations.
__ index the meta-method name of the meta-table in lua, and when the corresponding member is not found in the table, the __ index meta-method of the meta-table is called.
__ Newindex, the meta-method name of the meta-table in lua, when a value is assigned to an absent member in the table, the __ Newindex meta-method of its meta-table is called.
According to an aspect of the embodiment of the present application, there is provided a method for processing dirty data, optionally, in this embodiment, the method for processing dirty data may be applied to a hardware environment configured by a server 101, a network 102, and a user terminal 103 as shown in fig. 1. As shown in fig. 1, a server 101 is connected to a user terminal 103 via a network, where the server may be used, but is not limited to, to provide services to the user terminal or clients installed on the user terminal, which may include video clients, instant messaging clients, browser clients, game clients, shopping clients, and the like. The server 101 may be, but not limited to, provided with a database 105 for providing a data storage service for the server 101. Further, the network may include, but is not limited to: a wired network, a wireless network, wherein the wired network comprises: local area networks, metropolitan area networks, and wide area networks, the wireless network comprising: bluetooth, WIFI, and other wireless communication enabled networks, the user terminal 103 may be a terminal configured with a client of a target gaming application, which may include, but is not limited to, at least one of: the server 101 may be a single server, a server cluster including a plurality of servers, or a cloud server, and the application 107 providing the dirty data processing service may be, but not limited to, a user terminal 103, an entry of the application 107 configured on the terminal, and the dirty data processing service may be used, for example, a difference presented in the client by the modified content corresponding to the dirty data may be displayed through a display interface of the application 107 based on the processing method of the dirty data by the application 107, and the first target field may be, but not limited to, the present embodiment does not limit any limitation.
As shown in fig. 1, the above-mentioned dirty data processing method may be implemented in the user terminal 103 by the following steps:
s1, an application program 107 for executing the dirty data processing method is run on a user terminal 103, and the execution of a first meta-table operation is triggered;
s2, executing a first meta-table operation when a first target field in a target data table configured by the application program 107 is requested to be modified;
s3, when the application program 107 executes a first meta-table operation and detects that the first target field is dirty data, the application program 107 is controlled to detect whether the first target field belongs to sensitive data;
s4, in the case where the application 107 determines that the first target field is not sensitive data, the first target field is written into a dirty data list, where the dirty data list may be stored in the user terminal 103, or may be stored in a database configured by the server 101 through the network 102.
Alternatively, in this embodiment, as shown in fig. 1, the above-mentioned dirty data processing method may also be implemented in the server 101 by the following steps:
s1, executing the dirty data processing method on a server 101, and triggering to execute a first meta-table operation;
S2, executing a first meta-table operation when a first target field in a target data table configured by the server 101 is requested to be modified;
s3, executing a first meta-table operation on the server 101, and detecting whether the first target field belongs to sensitive data or not under the condition that the first target field is detected to be dirty data;
s4, in the case where the server 101 determines that the first target field is not sensitive data, the first target field is written into a dirty data list, where the dirty data list may be stored in the database shown in fig. 1, or may be stored in a storage device configured by the user terminal 107 through the network 102.
Optionally, in this embodiment, the above-mentioned dirty data processing method may further include, but is not limited to, synchronous or asynchronous processing by the user terminal 107 and the server 101, and data interaction through the network 102.
The above is merely an example, and the present embodiment is not particularly limited.
Optionally, as an optional embodiment, as shown in fig. 2, the method for processing dirty data includes:
s202, triggering and executing a first meta-table operation under the condition that a first target field in a target data table is requested to be modified, wherein the first meta-table operation is set to be triggered and executed when the field in the target data table is requested to be modified, and is used for detecting whether the field in the target data table, which is requested to be modified, is dirty data or not;
S204, detecting whether the first target field belongs to sensitive data or not under the condition that the first meta-table operation is executed to detect that the first target field is dirty data;
s206, writing the first target field into a dirty data list in the case that the first target field is not sensitive data.
Alternatively, in this embodiment, the application scenario of the dirty data processing method may include, but is not limited to, a service scenario that needs to perform data interaction and data modification, for example, a video service, an instant messaging service, a browser service, a game service, an online shopping service, and the like.
Taking the example that the application scenario is a game service, the following contents may be included but are not limited to:
alternatively, in the present embodiment, the above-described Game service may be applied to various Game applications, but is not limited to, wherein the above-described Game applications may be a multiplayer online tactical Game (Multiplayer Online Battle Arena abbreviated as MOBA) or a Single Player Game (SPG). The target game application may include, but is not limited to, a shooting application, a role playing application, an instant strategy application, etc., which may include, but is not limited to, a first person shooting application, a third person shooting application, and a shooting application capable of switching between a first person and a third person.
Fig. 3 is a schematic view of an application scenario of a method for processing dirty data according to an embodiment of the present invention, as shown in fig. 3, an application display interface may be divided into a first person display interface 301 and a third person display interface 303, and includes, but is not limited to, a display interface that switches between the first person and the third person using a view angle switching interaction button.
It should be noted that the above game application may include, but is not limited to, at least one of the following: two-dimensional (2D) game applications, three-dimensional (3D) game applications, virtual Reality (VR) game applications, augmented Reality (Augmented Reality AR) game applications, mixed Reality (MR) game applications. The above is merely an example, and the present embodiment is not limited in any way.
The first person display interface 301 and the third person display interface 303 are respectively configured with different display interfaces, the third person display interface 303 displays a virtual operation object 305, after the user switches the display interface from the third person display interface 303 to the first person display interface 301 through a visual angle switching interaction button, part of data associated with the third person display interface 303 is the dirty data, for example, appearance data of the virtual operation object 305, wherein the appearance data of the virtual prop 307 held by the virtual operation object 305 is the sensitive data, and after the user switches the display interface from the third person display interface 303 to the first person display interface 301, the appearance data of the virtual prop 307 is stored in a corresponding database for subsequent processing.
Fig. 4 is a schematic application scenario of another method for processing dirty data according to an embodiment of the present invention, where the application scenario is an online shopping service, as shown in fig. 4, may include, but is not limited to, the following:
optionally, in this embodiment, the online shopping service may include, but is not limited to, performing an offer, notifying that the user may enjoy the offer by displaying the identifier 404 on the display interface 402 of the user terminal, processing, after the user participates in the offer, the user information that participates in the offer and the identifier 404 configured for the user as the dirty data, and displaying, after the user participates in the offer, the identifier 406 that has completed the offer to notify the user, where the user information may be used as sensitive data in the dirty data, and after the user participates in the offer, storing the corresponding user information in the corresponding database for performing subsequent processing.
Optionally, in this embodiment, the setting of the sensitive data may be adjusted according to actual needs, and data that needs to be reserved in the dirty data and to be processed later is used as the sensitive data.
The above is merely an example, and the present embodiment is not limited in any way.
Alternatively, in the present embodiment, the above-described target data table may include, but is not limited to, a data table in the lua script language, a data table in the C language, and the like, and may also include, but is not limited to, a meta table set for a table (table), a meta table set for user data (userdata), and the like. The first target field may include, but is not limited to, a field for composing the target data table or a field for composing the user data, etc.
Alternatively, in this embodiment, the meta-table operation may include, but is not limited to, invoking a __ new index meta-method, a __ index meta-method, etc. in the lua scripting language.
Alternatively, in the present embodiment, the case where the above-described first target field is requested to be modified may include, but is not limited to, a game level of a virtual player, a virtual life value, a virtual gold coin, etc. being requested to be modified in a game application scenario, a preference of a shopper at the time of shopping, a virtual token, etc. being requested to be modified in a shopping application scenario, a release content of a user in an instant communication application, a reply content based on the release content, etc.
Alternatively, in this embodiment, the dirty data may include, but is not limited to, data in the source system that is not within a given range or is unambiguous to the actual service, or is in an illegal data format, and that has non-canonical encoding and ambiguous service logic in the source system.
For example, in database technology, dirty data is generated in a temporary update, transaction a updates a certain data item X, but for some reason transaction a rolls back, while another transaction B reads the value of data item X (after a update), a rolls back the transaction, the data item recovers the original value, and transaction B reads a temporary data of data item X, that is, the dirty data.
Alternatively, in this embodiment, the sensitive data may include, but is not limited to, dirty data that has a practical meaning and needs to be stored in a database.
For example, when a lottery is performed in a game application or a shopping application, corresponding lottery data is updated after a lottery is completed, and at this time, data representing the previous lottery content is the sensitive data, that is, dirty data which needs to be stored in a preset database, not redundant dirty data.
Taking the example that the first table operation is an operation performed based on the __ newindex method, this embodiment will be further described below:
FIG. 5 is a flow chart of an alternative dirty data processing method according to an embodiment of the present invention, as shown in FIG. 5, the flow includes the following steps:
S502, after receiving a request message needing data modification, modifying data corresponding to the request message;
s504, a __ new metadata table method (corresponding to the first metadata table operation;
s506, determining whether the data is sensitive data, executing step S508 if the data is not sensitive data, and executing step S510 if the data is sensitive data;
s508, adding the data to a dirty data list, wherein the data may include, but is not limited to, a table (table) or user data (userdata);
and S510, writing the data back to the database.
Optionally, in this embodiment, after receiving the request message that needs to modify data, all modifications of the table trigger __ newindex call by using the __ newindex metadata method, and these data are monitored and managed in the __ newindex metadata method, for example, marked as dirty data, put into a dirty data list, or immediately written into the data to complete persistence, so as to achieve the technical effect of monitoring the change of the table data.
According to the embodiment, under the condition that a first target field in the target data table is requested to be modified, triggering and executing the first meta-table operation, under the condition that the first meta-table operation is executed to detect that the first target field is dirty data, detecting whether the first target field belongs to the sensitive data, under the condition that the first target field is not the sensitive data, writing the first target field into the dirty data list, under the condition that the first target field is determined to be modified, determining that the first target field is the dirty data by utilizing the first meta-table operation, and then, under the condition that the first target field is not the sensitive operation, adding the first target field into the dirty data list, the technical scheme that all data can only be added into the dirty data list at fixed time or the dirty data needs to be manually processed in the related technology is replaced, so that automatic marking of the dirty data is achieved, different subsequent processing modes can be adopted according to the types (the types are divided into the sensitive data and the non-sensitive data) of the dirty data, the purposes of simplifying the dirty data processing is achieved, the dirty data detection flow is improved, and the technical problem that the related technical efficiency of the dirty data detection is lower is solved.
In an alternative embodiment, the triggering performs a first meta-table operation comprising: detecting, by the first meta-table operation, whether a new value of the first target field after the modification is the same as an original value of the first target field before the modification; the first target field is marked as the dirty data if the new value of the first target field is different from the original value of the first target field.
Optionally, in this embodiment, the new value of the first target field is a corresponding value in the first target field after modification, the original value of the first target field is a corresponding value in the first target field before modification, and the first target field is marked as the dirty data by comparing whether the new value and the original value are the same or not, if not, the new value and the original value are the same.
It should be noted that fig. 6 is a schematic diagram of still another alternative method for processing dirty data according to an embodiment of the present invention, as shown in fig. 6, the original value, that is, the original data may include, but is not limited to, data 602 shown in fig. 6, and the new value, that is, the modified data may include, but is not limited to, data 604 shown in fig. 6.
The lower layer of the "drop" in the data 602 is inserted into the intermediate layer "__ raw __" to modify the data, and further, the new value of the first target field is different from the original value of the first target field.
According to the method and the device for marking the dirty data, the dirty data can be automatically marked under the condition that the first target field is requested to be modified, so that the technical problems of huge workload and extremely low efficiency caused by manual marking or all timing marking of staff required for marking the dirty data in the related technology are solved, and the technical effects of improving the efficiency of processing the dirty data and reducing the cost of processing the dirty data are achieved.
In an alternative embodiment, in the event that a first target field in the target data table is requested to be modified, triggering the execution of the first meta-table operation includes: and triggering to execute the first meta-table operation under the condition that the value of the first target field is requested to be changed into a new value and the first target field is in a first data sub-table in the target data table.
Alternatively, in this embodiment, the first data sub-table may include, but is not limited to, as shown in fig. 6, where whether the first target field is in the first data sub-table is determined by checking whether the first target field is included in the first data sub-table 606.
For example, fig. 7 is a schematic diagram of an alternative method for processing dirty data according to an embodiment of the present invention, as shown in fig. 7, where the first target field 702 is in the first data sub-table 706 in the target data table 704, and if it is detected that the first target field 702 exists in the first data sub-table 706, the first meta-table operation, for example, the __ new element operation, is triggered to be executed.
According to the method and the device for marking the dirty data, when the value of the first target field is requested to be changed to a new value and the first target field is in the first data sub table in the target data table, the first meta table operation is triggered to be executed, dirty data can be automatically marked under the condition that the first target field is requested to be changed, and further the technical problems of huge workload and extremely low efficiency caused by the fact that staff is required to mark the dirty data manually or mark the dirty data regularly in the related art are solved, and the technical effects of improving the dirty data processing efficiency and reducing the dirty data processing cost are achieved.
In an alternative embodiment, the method further comprises: setting the value of the first target field in the first data sub-table in the target data table to be the new value when the new value is not of the data table type; setting a second data sub-table in the first data sub-table, setting the first target field in the second data sub-table, and setting the value of the first target field in the second data sub-table as the new value when the new value is of the data table type.
Alternatively, in the present embodiment, the type of the new value is not a data table type, and may include, but is not limited to, directly representing the data with a numerical value.
For example, when the value of "Level" is modified to 1, the first data sub-table corresponding to the first target field "Level" is determined to be "level=1", that is, the value of the first target field is set to be a new value 1.
Optionally, in this embodiment, the new value is of a data table type, which may include, but is not limited to, "__ raw __ = { level=1 }", that is, a data table manner is used as the second data table, so as to set the value of the first target field in the second data table to be the new value 1.
According to the embodiment, when the new value type is the data table, the value of the first target field corresponding to the data table is modified, and when the new value type is not the data table, the value of the first target field is directly modified so as to automatically mark the dirty data, so that the technical problems of huge workload and extremely low efficiency caused by manual marking or all timing marking of staff in the marking of the dirty data in the related technology are solved, and the technical effects of improving the efficiency of processing the dirty data and reducing the cost of processing the dirty data are achieved.
In an alternative embodiment, before said triggering to perform said first table operation, said method further comprises: and setting the first data sub-table in an original data table in response to the acquired operation instruction, and setting the first target field in the original data table in the first data sub-table to obtain the target data table.
Alternatively, in this embodiment, the operation instruction in response to the acquired operation instruction may include, but is not limited to, an instruction for inserting the first data sub-table, a processing instruction for dirty data, and the like.
For example, as shown in fig. 6, by configuring the first data sub-table as "__ raw __", that is, inserting the first data sub-table into the original data table, and executing the __ newindex __ element method, the first data sub-table can be set in the original data table in response to the obtained operation instruction, and the first target field in the original data table is set in the first data sub-table, so as to obtain the target data table, so as to realize transformation of the original data table, solve the technical problems of huge workload and extremely low efficiency caused by manual marking or timing full marking of marked dirty data by staff in the related art, and achieve the technical effects of improving the efficiency of processing the dirty data and reducing the cost of processing the dirty data.
In an alternative embodiment, the method further comprises: triggering execution of a second sub-table operation in the case that a second target field is requested to be accessed and the second target field is in a third data sub-table in the target data table, wherein the second sub-table operation is set to be triggered to be executed when a field in the target data table is accessed, and is used for querying a value of the second target field; and returning the value of the second target field in the third data sub-table obtained by executing the second table operation.
Optionally, in this embodiment, fig. 8 is a schematic flow chart of an optional dirty data processing method according to an embodiment of the present invention, where the flow includes the following steps:
s802, accessing a userdata. Level (corresponding to the original data table);
s804, determining whether a level field exists in userdata, and executing step S806 if no level field exists;
s806, calling a '__ index' element method to acquire the value of the second target field (corresponding to the second element table operation);
s808, returning userdata __ raw __ level.
According to the embodiment, under the condition that the second target field is requested to be accessed and the second target field is in the third data sub-table in the target data table, the second sub-table operation is triggered to be executed, and the value of the second target field in the third data sub-table obtained by executing the second sub-table operation is returned, so that the dirty data monitoring and management by using the meta-method of the meta-table is realized.
In an alternative embodiment, the method further comprises: and writing the target data into a target database under the condition that the first target field is the sensitive data.
Optionally, in this embodiment, determining that the first target field is sensitive data may further include, but is not limited to, by pre-configuring a corresponding field for the sensitive data, and determining whether the data is sensitive data according to the field.
For example, it is checked whether a target field is sensitive data, and it is determined whether the modified data is sensitive data according to the "__ cwd __" field in the current modified data.
By the embodiment, the sensitive data and the non-sensitive data can be separated, the data is landed by adopting different strategies, the sensitive data and the non-sensitive data can be automatically identified, and different write-back strategies are adopted for different types of dirty data. The database can be written regularly for non-sensitive data, and the database can be written in real time for sensitive data, so that no developer is needed to participate in both the sensitive data and the non-sensitive data. The method solves the problem that sensitive data in the prior art needs to be manually processed, and improves the technical effect of the robustness of the program.
In an alternative embodiment, the method further comprises: acquiring a first login instruction from a target application, wherein the first login instruction is used for requesting to login the target application by using a first account; under the condition that the first account is a newly created account, acquiring a first field with a value corresponding to the first account as an initialization value, and obtaining a first data table comprising the first field; and setting a fourth data sub-table in the first data table in response to the acquired operation instruction, and setting the first field in the first data table in the fourth data sub-table to obtain the target data table.
Optionally, in this embodiment, the account that the first account is newly created may include, but is not limited to, an account that the user registers with a corresponding server through the target application, and may also include, but is not limited to, an account that is newly created by performing data migration through other applications.
In an alternative embodiment, the method further comprises: acquiring a second login instruction from a target application, wherein the second login instruction is used for requesting to login the target application by using a second account; under the condition that the second account is not a newly created account, acquiring a second field with the current value corresponding to the second account from a database to obtain a second data table comprising the second field; and setting a fifth data sub-table in the second data table in response to the acquired operation instruction, and setting the second field in the second data table in the fifth data sub-table to obtain the target data table.
Fig. 9 is a schematic flow chart of an alternative dirty data processing method according to an embodiment of the present invention, taking the above target application as a game application as an example, the flow includes the following steps:
s902, logging in the target application according to the first login instruction;
s904, judging whether the account is a newly created account;
s906, in the case that the account is determined to be the newly created account, determining the account as the first account, and determining the value of the first field corresponding to the first account as the initialization value, where the first field may include, but is not limited to, game application character data, for example, appearance data of a game character, accessory data of a game character, equipment data of a game character, and the like.
S908, determining the account as the second account and acquiring the value of a second field corresponding to the second account from a database, wherein the database is used for storing the historical value of the second field corresponding to the second account when the account is determined not to be the newly created account;
s910, reforming the fourth data sub-table or the fifth data sub-table, setting a fourth data sub-table in the first data table, and setting a first field in the first data table in the fourth data sub-table to obtain a target data table, or setting a fifth data sub-table in the second data table, and setting a second field in the second data table in the fifth data sub-table to obtain the target data table.
S912, returning the target data table to the upper data processing module, and executing corresponding processing.
According to the embodiment, for the newly created account, the value of the first field corresponding to the newly created account is configured as the initialized value, and for the non-newly created account, the value of the second field corresponding to the non-newly created account is obtained from the database, so that the transformation of the data table can be rapidly realized, the collection and management of dirty data can be automatically completed later, the processing effect of the dirty data is improved, and the technical effect of reducing the processing cost of the dirty data is achieved.
The present embodiment is further described below with reference to specific examples:
FIG. 10 is a flow chart of an alternative dirty data processing method according to an embodiment of the present invention, the flow including the steps of:
s1002, assigning a value (corresponding to the aforementioned first target field) to userdata.
S1004, determining whether a level field exists in userdata (corresponding to the first data sub-table), if so, executing step S1006, and if not, executing step S1008;
s1006, assigning a value to userdata.
S1008, executing __ new element method to determine whether the original value and the new value are the same;
S1010, comparing whether the original value and the new value are the same, if the original value and the new value are the same, determining that the target field is not changed, executing step S1026, otherwise, executing step S1012 if the original value and the new value are different;
s1012, marking the level field as dirty data;
s1014, determining whether the dirty data is sensitive data, if the dirty data is sensitive data, executing step S1016, otherwise executing step S1018;
s1016, writing the sensitive data into a database for storing the sensitive data, and executing step S1020;
s1018, the dirty data is put into a dirty data list, and then step S1020 is executed;
s1020, determining whether the new value type is a data table (table), if so, executing step S1022, and if not, executing step S1024;
s1022, modifying the data table, inserting '__ raw __' into each layer of the data table, and executing step S1026;
s1024, assigning value to userdata __ raw __ level, and executing step S1026;
s1026, ending.
Optionally, in this embodiment, first, by checking whether the first layer of userdata has a level field, the first layer of userdata after transformation has only two data of "__ raw __" and "__ cwd __" that are newly added, so the __ newindex method of the meta table is directly called;
Secondly, checking whether the new value and the original value are equal or not, i.e. checking whether a modification is valid or not, by using "__ new;
thirdly, checking whether the data is sensitive data, wherein the application program can comprise, but is not limited to, maintaining a list of the sensitive data, storing paths of the sensitive data, and judging whether the modified data is sensitive data according to a '__ cwd __' field in the current modified data;
thirdly, checking whether the type of the new value is a table or not in the process of assigning, if the type of the new value is a table, performing data transformation on the table once (namely inserting '__ raw __' and '__ cwd __' into each layer), and then assigning the value;
finally, the new value is assigned to the level field under the "__ raw __" layer.
With this embodiment, after the data is modified, each layer of data is further "__ raw __", and the data is accessed by userdata __ raw __ level, and the data is processed in the __ index element method of the element table, for example, the value of the same field under __ raw __ is returned in the __ index element method.
In conclusion, through the transformation of the original data, the dirty data is monitored and managed by using the meta method of the meta table, and meanwhile, the type of the dirty data can be judged through a path, so that the strategies of real-time writing of sensitive data and timing writing of non-sensitive data are realized. Because the hierarchical structure of the original data is modified, the functional interfaces related to the table in the lua need to be rewritten, for example: the parameters, ipaires, foreach, foreachi, next, maxn, getn, sort, remove, insert, etc. In the function interfaces, the rewritten logic is basically similar, firstly, whether the name of the meta table of the parameter table is the meta table name in the realization process is judged, if so, the data under the layer of __ raw __ is transferred to the original function interface, and if not, the original function interface is directly called. The function interface after rewriting supports the data before and after transformation at the same time, and the calling mode is completely unchanged for the developer, so the invention is completely transparent for the developer, the developer does not need to modify any using mode, and the collection and management of dirty data are automatically completed on the premise of not changing the using mode. And simultaneously separating sensitive data from non-sensitive data, and finishing data landing by adopting different strategies.
It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present invention is not limited by the order of acts described, as some steps may be performed in other orders or concurrently in accordance with the present invention. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required for the present invention.
According to another aspect of the embodiment of the present invention, there is also provided a dirty data processing apparatus for implementing the above dirty data processing method. As shown in fig. 11, the apparatus includes:
a triggering module 1102, configured to trigger, in a case where a first target field in a target data table is requested to be modified, to perform a first table operation, where the first table operation is configured to be triggered to be performed when a field in the target data table is requested to be modified, and the first table operation is configured to detect whether the field in the target data table, in which modification is requested, is dirty data;
a detection module 1104, configured to detect whether the first target field belongs to sensitive data if the first table operation is performed to detect that the first target field is dirty data;
A writing module 1106, configured to write the first target field into a dirty data list if the first target field is not the sensitive data.
In an alternative embodiment, the triggering module 1102 includes: a detection unit, configured to detect, through the first table operation, whether a new value of the first target field after the modification is the same as an original value of the first target field before the modification; and the marking unit is used for marking the first target field as the dirty data when the new value of the first target field is different from the original value of the first target field.
In an alternative embodiment, the triggering module 1102 includes: and the triggering unit is used for triggering and executing the first meta-table operation under the condition that the value of the first target field is requested to be changed into a new value and the first target field is in a first data sub-table in the target data table.
In an alternative embodiment, the apparatus is further adapted to: setting the value of the first target field in the first data sub-table in the target data table to be the new value when the new value is not of the data table type; setting a second data sub-table in the first data sub-table, setting the first target field in the second data sub-table, and setting the value of the first target field in the second data sub-table as the new value when the new value is of the data table type.
In an alternative embodiment, the apparatus is further adapted to: before the trigger executes the first meta-table operation, responding to the acquired operation instruction, setting the first data sub-table in an original data table, and setting the first target field in the original data table in the first data sub-table to obtain the target data table.
In an alternative embodiment, the apparatus is further adapted to: triggering execution of a second sub-table operation in the case that a second target field is requested to be accessed and the second target field is in a third data sub-table in the target data table, wherein the second sub-table operation is set to be triggered to be executed when a field in the target data table is accessed, and is used for querying a value of the second target field; and returning the value of the second target field in the third data sub-table obtained by executing the second table operation.
In an alternative embodiment, the apparatus is further adapted to: and writing the target data into a target database under the condition that the first target field is the sensitive data.
In an alternative embodiment, the apparatus is further adapted to: acquiring a first login instruction from a target application, wherein the first login instruction is used for requesting to login the target application by using a first account; under the condition that the first account is a newly created account, acquiring a first field with a value corresponding to the first account as an initialization value, and obtaining a first data table comprising the first field; and setting a fourth data sub-table in the first data table in response to the acquired operation instruction, and setting the first field in the first data table in the fourth data sub-table to obtain the target data table.
In an alternative embodiment, the apparatus is further adapted to: acquiring a second login instruction from a target application, wherein the second login instruction is used for requesting to login the target application by using a second account; under the condition that the second account is not a newly created account, acquiring a second field with the current value corresponding to the second account from a database to obtain a second data table comprising the second field; and setting a fifth data sub-table in the second data table in response to the acquired operation instruction, and setting the second field in the second data table in the fifth data sub-table to obtain the target data table.
According to still another aspect of the embodiment of the present invention, there is also provided an electronic device for implementing the above-mentioned dirty data processing method, where the electronic device may be a terminal device or a server as shown in fig. 1. The present embodiment is described taking the electronic device as a server as an example. As shown in fig. 12, the electronic device comprises a memory 1202 and a processor 1204, the memory 1202 storing a computer program, the processor 1204 being arranged to perform the steps of any of the method embodiments described above by means of the computer program.
Alternatively, in this embodiment, the electronic device may be located in at least one network device of a plurality of network devices of the computer network.
Alternatively, in the present embodiment, the above-described processor may be configured to execute the following steps by a computer program:
s1, triggering and executing a first meta-table operation under the condition that a first target field in a target data table is requested to be modified, wherein the first meta-table operation is set to be triggered and executed when the field in the target data table is requested to be modified, and is used for detecting whether the field in the target data table, which is requested to be modified, is dirty data or not;
s2, under the condition that the first meta-table operation is executed to detect that the first target field is dirty data, detecting whether the first target field belongs to sensitive data;
and S3, writing the first target field into a dirty data list under the condition that the first target field is not sensitive data.
Alternatively, as will be appreciated by those skilled in the art, the structure shown in fig. 12 is merely illustrative, and the electronic device may be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a palmtop computer, a mobile internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Fig. 12 is not limited to the structure of the electronic device and the electronic apparatus described above. For example, the electronics can also include more or fewer components (e.g., network interfaces, etc.) than shown in fig. 12, or have a different configuration than shown in fig. 12.
The memory 1202 may be used to store software programs and modules, such as program instructions/modules corresponding to the methods and apparatuses for processing dirty data in the embodiments of the present invention, and the processor 1204 executes the software programs and modules stored in the memory 1202 to perform various functional applications and data processing, that is, implement the methods for processing dirty data. Memory 1202 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 1202 may further include memory located remotely from the processor 1204, which may be connected to the terminal via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof. Wherein the memory 1202 may be used for, but is not limited to, dirty data and sensitive data. As an example, as shown in fig. 12, the memory 1202 may include, but is not limited to, a trigger module 1102, a detection module 1104, and a writing module 1108 in the processing device including the dirty data. In addition, other module units in the dirty data processing apparatus may be included, but are not limited to, and are not described in detail in this example.
Optionally, the transmission device 1206 is configured to receive or transmit data via a network. Specific examples of the network described above may include wired networks and wireless networks. In one example, the transmission means 1206 comprises a network adapter (Network Interface Controller, NIC) that can be connected to other network devices and routers via a network cable to communicate with the internet or a local area network. In one example, the transmission device 1206 is a Radio Frequency (RF) module for communicating wirelessly with the internet.
In other embodiments, the terminal device or the server may be a node in a distributed system, where the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting the plurality of nodes through a network communication. Among them, the nodes may form a Peer-To-Peer (P2P) network, and any type of computing device, such as a server, a terminal, etc., may become a node in the blockchain system by joining the Peer-To-Peer network.
According to one aspect of the present application, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The computer instructions are read from a computer readable storage medium by a processor of a computer device, which computer instructions are executed by the processor, such that the computer device performs the processing of method dirty data provided in various alternative implementations of the processing aspect of dirty data or the monitoring aspect of sensitive data described above, wherein the computer program is arranged to perform the steps in any of the method embodiments described above when run.
Alternatively, in the present embodiment, the above-described computer-readable storage medium may be configured to store a computer program for executing the steps of:
s1, triggering and executing a first meta-table operation under the condition that a first target field in a target data table is requested to be modified, wherein the first meta-table operation is set to be triggered and executed when the field in the target data table is requested to be modified, and is used for detecting whether the field in the target data table, which is requested to be modified, is dirty data or not;
s2, under the condition that the first meta-table operation is executed to detect that the first target field is dirty data, detecting whether the first target field belongs to sensitive data;
and S3, writing the first target field into a dirty data list under the condition that the first target field is not sensitive data.
Alternatively, in this embodiment, it will be understood by those skilled in the art that all or part of the steps in the methods of the above embodiments may be performed by a program for instructing a terminal device to execute the steps, where the program may be stored in a computer readable storage medium, and the storage medium may include: flash disk, read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), magnetic or optical disk, and the like.
The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
The integrated units in the above embodiments may be stored in the above-described computer-readable storage medium if implemented in the form of software functional units and sold or used as separate products. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing one or more computer devices (which may be personal computers, servers or network devices, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
In the foregoing embodiments of the present application, the descriptions of the embodiments are emphasized, and for a portion of this disclosure that is not described in detail in this embodiment, reference is made to the related descriptions of other embodiments.
In several embodiments provided by the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely exemplary, and the division of the units, such as the division of the units, is merely a logical function division, and may be implemented in another manner, for example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interfaces, units or modules, or may be in electrical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The foregoing is merely a preferred embodiment of the present invention and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present invention, which are intended to be comprehended within the scope of the present invention.
Claims (15)
1. A method of processing dirty data, comprising:
triggering execution of a first meta-table operation in the case that a first target field in a target data table is requested to be modified, wherein the first meta-table operation is set to be triggered to be executed when the field in the target data table is requested to be modified, and the first meta-table operation is used for detecting whether the field in the target data table, which is requested to be modified, is dirty data or not;
Detecting whether the first target field belongs to sensitive data or not under the condition that the first meta-table operation is executed to detect that the first target field is dirty data;
and writing the first target field into a dirty data list in the case that the first target field is not the sensitive data.
2. The method of claim 1, wherein the triggering of the execution of the first meta-table operation comprises:
detecting, by the first meta-table operation, whether a new value of the first target field after the modification is the same as an original value of the first target field before the modification;
the first target field is marked as the dirty data if the new value of the first target field is different from the original value of the first target field.
3. The method of claim 1, wherein triggering execution of the first meta-table operation in the event that a first target field in the target data table is requested to be modified comprises:
and triggering to execute the first meta-table operation under the condition that the value of the first target field is requested to be changed into a new value and the first target field is in a first data sub-table in the target data table.
4. A method according to claim 3, characterized in that the method further comprises:
setting the value of the first target field in the first data sub-table in the target data table to be the new value when the new value is not of the data table type;
setting a second data sub-table in the first data sub-table, setting the first target field in the second data sub-table, and setting the value of the first target field in the second data sub-table as the new value when the new value is of the data table type.
5. A method according to claim 3, wherein prior to the triggering of the execution of the first meta-table operation, the method further comprises:
and setting the first data sub-table in an original data table in response to the acquired operation instruction, and setting the first target field in the original data table in the first data sub-table to obtain the target data table.
6. The method according to claim 1, wherein the method further comprises:
triggering execution of a second sub-table operation in the case that a second target field is requested to be accessed and the second target field is in a third data sub-table in the target data table, wherein the second sub-table operation is set to be triggered to be executed when a field in the target data table is accessed, and is used for querying a value of the second target field;
And returning the value of the second target field in the third data sub-table obtained by executing the second table operation.
7. The method according to any one of claims 1 to 6, further comprising:
and writing the sensitive data into a target database under the condition that the first target field is the sensitive data.
8. The method according to any one of claims 1 to 6, further comprising:
acquiring a first login instruction from a target application, wherein the first login instruction is used for requesting to login the target application by using a first account;
under the condition that the first account is a newly created account, acquiring a first field with a value corresponding to the first account as an initialization value, and obtaining a first data table comprising the first field; and setting a fourth data sub-table in the first data table in response to the acquired operation instruction, and setting the first field in the first data table in the fourth data sub-table to obtain the target data table.
9. The method according to any one of claims 1 to 6, further comprising:
Acquiring a second login instruction from a target application, wherein the second login instruction is used for requesting to login the target application by using a second account;
under the condition that the second account is not a newly created account, acquiring a second field with the current value corresponding to the second account from a database to obtain a second data table comprising the second field; and setting a fifth data sub-table in the second data table in response to the acquired operation instruction, and setting the second field in the second data table in the fifth data sub-table to obtain the target data table.
10. A dirty data processing apparatus, comprising:
a triggering module, configured to trigger, in a case where a first target field in a target data table is requested to be modified, to perform a first table operation, where the first table operation is configured to be triggered to be performed when a field in the target data table is requested to be modified, and the first table operation is configured to detect whether the field in the target data table, in which modification is requested, is dirty data;
the detection module is used for detecting whether the first target field belongs to sensitive data or not under the condition that the first table operation is executed to detect that the first target field is dirty data;
And the writing module is used for writing the first target field into a dirty data list when the first target field is not the sensitive data.
11. The apparatus of claim 10, wherein the trigger module comprises:
a detection unit, configured to detect, through the first table operation, whether a new value of the first target field after the modification is the same as an original value of the first target field before the modification;
and the marking unit is used for marking the first target field as the dirty data when the new value of the first target field is different from the original value of the first target field.
12. The apparatus of claim 10, wherein the trigger module comprises:
and the triggering unit is used for triggering and executing the first meta-table operation under the condition that the value of the first target field is requested to be changed into a new value and the first target field is in a first data sub-table in the target data table.
13. The apparatus of claim 12, wherein the apparatus is further configured to:
setting the value of the first target field in the first data sub-table in the target data table to be the new value when the new value is not of the data table type;
Setting a second data sub-table in the first data sub-table, setting the first target field in the second data sub-table, and setting the value of the first target field in the second data sub-table as the new value when the new value is of the data table type.
14. A computer readable storage medium comprising a stored program, wherein the program when run performs the method of any one of claims 1 to 9.
15. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method according to any of the claims 1 to 9 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011069883.3A CN112131240B (en) | 2020-09-30 | 2020-09-30 | Dirty data processing method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011069883.3A CN112131240B (en) | 2020-09-30 | 2020-09-30 | Dirty data processing method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112131240A CN112131240A (en) | 2020-12-25 |
| CN112131240B true CN112131240B (en) | 2023-09-26 |
Family
ID=73843808
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011069883.3A Active CN112131240B (en) | 2020-09-30 | 2020-09-30 | Dirty data processing method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112131240B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112633206A (en) * | 2020-12-28 | 2021-04-09 | 上海眼控科技股份有限公司 | Dirty data processing method, device, equipment and storage medium |
| CN113254962A (en) * | 2021-05-27 | 2021-08-13 | 平安普惠企业管理有限公司 | Sensitive data authority control method, device, equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102622310A (en) * | 2011-01-30 | 2012-08-01 | 成都市华为赛门铁克科技有限公司 | Invalid data erasing method, device and system |
| CN104007993A (en) * | 2014-06-11 | 2014-08-27 | 中国科学院信息工程研究所 | Method and device for eliminating sensitive data of Linux system memory |
| CN109871699A (en) * | 2019-01-28 | 2019-06-11 | 中国平安财产保险股份有限公司 | Method, apparatus, computer equipment and the storage medium of tables of data safe handling |
| CN110472036A (en) * | 2019-08-21 | 2019-11-19 | 恩亿科(北京)数据科技有限公司 | A kind of sensitive data based on big data determines method and device |
| CN110704468A (en) * | 2019-10-17 | 2020-01-17 | 武汉微派网络科技有限公司 | Data updating method and device and controller |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10353870B2 (en) * | 2016-02-17 | 2019-07-16 | Netapp Inc. | Tracking structure for data replication synchronization |
| CN110390184B (en) * | 2018-04-20 | 2022-12-20 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer program product for executing applications in the cloud |
-
2020
- 2020-09-30 CN CN202011069883.3A patent/CN112131240B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102622310A (en) * | 2011-01-30 | 2012-08-01 | 成都市华为赛门铁克科技有限公司 | Invalid data erasing method, device and system |
| CN104007993A (en) * | 2014-06-11 | 2014-08-27 | 中国科学院信息工程研究所 | Method and device for eliminating sensitive data of Linux system memory |
| CN109871699A (en) * | 2019-01-28 | 2019-06-11 | 中国平安财产保险股份有限公司 | Method, apparatus, computer equipment and the storage medium of tables of data safe handling |
| CN110472036A (en) * | 2019-08-21 | 2019-11-19 | 恩亿科(北京)数据科技有限公司 | A kind of sensitive data based on big data determines method and device |
| CN110704468A (en) * | 2019-10-17 | 2020-01-17 | 武汉微派网络科技有限公司 | Data updating method and device and controller |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112131240A (en) | 2020-12-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106528224B (en) | Content updating method, server and system for Docker container | |
| CN109731330B (en) | Method and device for displaying picture, storage medium and electronic device | |
| CN112131240B (en) | Dirty data processing method and device, storage medium and electronic equipment | |
| US20140325070A1 (en) | Usage consumption for an invitee of a cloud system | |
| US9868061B2 (en) | Information processing system, information processing method, information processing program, computer-readable recording medium on which information processing program is recorded, and information processing device | |
| CN111324275B (en) | Broadcasting method and device for elements in display picture | |
| CN112138381A (en) | Game data processing method and device, storage medium and electronic device | |
| CN111318014A (en) | Image display method and apparatus, storage medium, and electronic apparatus | |
| CN113244609A (en) | Multi-picture display method and device, storage medium and electronic equipment | |
| CN114073100B (en) | Mapping view of digital content | |
| CN113117339A (en) | Data processing method, device, server and storage medium | |
| US11782898B2 (en) | Content data holding system, storage medium, content data holding server, and data management method | |
| CN109992178B (en) | Control method and device of target component, storage medium and electronic device | |
| CN108650217B (en) | Synchronous method, device, storage medium and the electronic device of action state | |
| CN113244615B (en) | Chat panel display control method and device, storage medium and electronic equipment | |
| CN113064531B (en) | Virtual resource interaction method and device, storage medium and electronic equipment | |
| CN113595878B (en) | Data interaction method and device, storage medium and electronic equipment | |
| US11998838B2 (en) | Content data holding system, storage medium, content data holding server, and data management method | |
| CN112675533A (en) | User archive information acquisition method and device based on cloud game | |
| CN112473139A (en) | Object form switching method and device, storage medium and electronic device | |
| JP5855038B2 (en) | Service providing system, service providing control method, and computer program | |
| CN112891952A (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN112044061A (en) | Game picture processing method and device, electronic equipment and storage medium | |
| CN113041615A (en) | Scene presenting method, device, client, server, equipment and storage medium | |
| CN113542892B (en) | Target object locking method and device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |