CN113704273A

CN113704273A - Data management method, device, storage medium and server

Info

Publication number: CN113704273A
Application number: CN202111241974.5A
Authority: CN
Inventors: 廖巍; 王同洋; 韩敏; 王慧强; 郭梓轩
Original assignee: Wuhan Huagong Anding Information Technology Co ltd
Current assignee: Wuhan Huagong Anding Information Technology Co ltd
Priority date: 2021-10-25
Filing date: 2021-10-25
Publication date: 2021-11-26

Abstract

The embodiment of the application discloses a data management method, a data management device, a storage medium and a server. The method comprises the following steps: the method comprises the steps of receiving a query request, constructing a query instruction according to query authority information in the query request, sending the query instruction to a database to trigger the database to determine a target data table corresponding to the query instruction, wherein the element content of at least one element in the target data table comprises effective data and label data, querying the target data table according to the target label parameter to obtain a query result, receiving the query result, and processing the query result according to the label data to obtain the target effective data. According to the embodiment of the application, the tag data and the effective data are combined to be used as element content to be stored, the reading speed and the query speed of the tag data are improved, and the tag data are added to the effective data by taking the elements as units, so that the data adding precision is improved.

Description

Data management method, device, storage medium and server

Technical Field

The present application relates to the field of information processing technologies, and in particular, to a data management method, an apparatus, a computer-readable storage medium, and a server.

Background

Tagging data with a tag, which may be a security tag, a sensitivity tag, etc., may allow for hierarchical classification of the data. For example, Microsoft's Power BI data analysis and visualization tools utilize tags that are custom-named, such as "personal", "public", or "confidential", to hierarchically classify data tables, which tags are created and defined by the associated security centers, primarily at the application level for coarse-grained management of data.

And label management is carried out on the data table, management of table granularity is supported, and the management granularity is relatively coarse. In an actual service scene, the situation that only part of data of a certain data table is sensitive data, most of information can be inquired to most of people is often caused, and management of data table-level tags in the service scene is clumsy and has insufficient precision, so that the requirements of users cannot be met.

Disclosure of Invention

Embodiments of the present application provide a data management method, an apparatus, a computer-readable storage medium, and a server, which can use an element as a tag unit, add tag data to valid data in the element, improve the accuracy of data tagging, and improve the reading speed of the tag data.

The embodiment of the application provides a data management method, which comprises the following steps:

receiving an operation request of a service system from a user terminal for data, wherein the operation request comprises a query request, and the query request carries query authority information;

generating a query instruction according to the query authority information, wherein the query instruction carries a target label parameter determined according to the query authority information;

sending the query instruction to a database to trigger the database to determine a target data table corresponding to the query instruction, wherein the element content of at least one element in the target data table comprises effective data and tag data, and querying the target data table according to the target tag parameter to obtain a query result;

receiving a query result fed back by the database, and processing the query result according to the tag data to obtain target effective data;

and sending the target effective data to the user terminal so as to trigger the user terminal to display the target effective data on a graphical interface of a service system of the user terminal.

An embodiment of the present application further provides a data management apparatus, including:

the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving an operation request of a service system from a user terminal to data, the operation request comprises a query request, and the query request carries query authority information;

the processing module is used for generating a query instruction according to the query authority information, and the query instruction carries a target label parameter determined according to the query authority information;

the sending module is used for sending the query instruction to a database so as to trigger the database to determine a target data table corresponding to the query instruction, wherein the element content of at least one element in the target data table comprises effective data and tag data, and querying the target data table according to the target tag parameter so as to obtain a query result;

the receiving module is also used for receiving the query result fed back by the database;

the result set generating module is used for processing the query result according to the tag data to obtain target effective data;

and the sending module is further used for sending the target effective data to the user terminal so as to trigger the user terminal to display the target effective data on a graphical interface of a service system of the user terminal.

An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, where the computer program is suitable for being loaded by a processor to perform the steps in the data management method according to any of the above embodiments.

An embodiment of the present application further provides a server, where the server includes a memory and a processor, where the memory stores a computer program, and the processor executes the steps in the data management method according to any of the above embodiments by calling the computer program stored in the memory.

According to the data management method, the data management device, the computer readable storage medium and the server, a query request is received, a query instruction is constructed according to query authority information carried in the query request, the query instruction carries a target label parameter determined according to the query authority information, the query instruction is sent to a database to trigger the database to determine a target data table corresponding to the query instruction, the element content of at least one element in the target data table comprises effective data and label data, the target data table is queried according to the target label parameter to obtain a query result, the query result fed back by the database is received, and the query result is processed according to the label data to obtain the target effective data. The element content of at least one element in the target data table in the embodiment of the application comprises effective data and tag data, so that the effective data and the corresponding tag data are stored in the elements of the target data table, the tag data and the effective data are combined to be used as the element content for storage, the reading speed of the tag data is improved, and the tag data and the effective data can be obtained only by inquiring once; in addition, in the embodiment of the application, the element is used as a marking unit, and the tag data is added to the effective data in the element, so that when the data is marked (the tag data is added), the marking granularity is small, and the data marking precision is improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic view of an application scenario of a data management method according to an embodiment of the present application.

Fig. 2 is a schematic flowchart of a data management method according to an embodiment of the present application.

Fig. 3 is another schematic flow chart of a data management method according to an embodiment of the present application.

Fig. 4 is a schematic flowchart of a data management method according to an embodiment of the present application.

Fig. 5 is a schematic structural diagram of a data management apparatus according to an embodiment of the present application.

Fig. 6 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The embodiment of the application provides a data management method, a data management device, a computer readable storage medium and a server. Specifically, the data management method of the embodiment of the present application may be executed by a server. The server may be a smart phone, a tablet Computer, a notebook Computer, a Personal Computer (PC), or the like. The server may be an independent physical server, a server cluster formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service and a cloud database.

Fig. 1 is a schematic view of an application scenario of a data management method according to an embodiment of the present application. As shown in fig. 1, the user terminal sends an operation request to the server through the service system (client service system), where the operation request includes adding or deleting data in the data table, modifying or adding some attribute or tag data in some record (tag data can be understood as data flag/data flag), and so on.

A service processing module (not shown in the figure) of a service system (a server service system) of the server receives the operation request and generates a database operation statement according to the operation request, and a parsing processing module in the server performs a series of processing on the database operation statement, such as parsing the database operation statement and modifying the database operation statement, to generate an operation instruction, which can be represented in the manner of the database operation statement. And the server sends the operation instruction to the database so as to perform corresponding operation on the data in the data table or the data table and receive an operation result fed back by the database.

As shown in fig. 1, the server includes a service system (a server service system), an analysis processing module (which may also be understood as a database statement analysis and processing module), and a result set generating module.

The service system in the server is a system for implementing a specific service, and may be a certain server application program or the like. The service system is directly oriented to the user and receives the operation request of the user to the data. The business processing module of the business system is also used for generating a general database operation statement according to the operation request, such as Structured Query Language (SQL); and calls a corresponding interface in the analysis processing module.

The analysis processing module is integrated in the server, logically located between the business system and the database, and mainly used for analyzing the database operation statements generated by the business system and modifying the element content corresponding to each field to be marked in the database operation statements one by one (the element content corresponding to the field can also be understood as the attribute value of the field) according to the label data so as to generate the operation instruction. For example, when data is inserted, corresponding tag data is added to the valid data header corresponding to the corresponding field in the database insertion statement. The valid data refers to an attribute value corresponding to each field before the tag data is added, such as an age field, and if the corresponding attribute value is 16 (years), 16 is valid data.

The parsing processing module includes various interfaces, such as a data insertion interface, a data update interface, a table creation interface, a data deletion interface, a data query interface, and the like.

In an embodiment, after modifying the element content corresponding to the corresponding field to be marked in the database operation statement one by one according to the tag data, the parsing processing module further encrypts the modified element content (including valid data and tag data) to generate an operation instruction.

And the database receives the operation instruction obtained after the analysis processing module processes the operation instruction, and performs corresponding database operation according to the operation instruction to obtain an operation result.

And the result set generation module is integrated in the server, logically positioned between the service system and the database, and used for decrypting (decrypting after encryption) and demarking the query result output by the database query statement to obtain corresponding target effective data.

And the service system in the server receives the target effective data and sends the target effective data to the user terminal so as to display the target effective data on a graphical interface of the service system of the user terminal.

An application scenario of the present application is briefly introduced above. A data management method, an apparatus, a computer-readable storage medium, and a server provided in the embodiments of the present application will be described in detail below. The numbers in the following examples are not intended to limit the order of preference of the examples.

It should be noted that the tag data in the embodiment of the present application may be security level data indicating security level of data, and may also be other types of tag data. In addition, in the embodiment of the present application, unit data in the data table is taken as an element.

Fig. 2 is a schematic flowchart of a data management method according to an embodiment of the present application. The data management method is applied to the server, and the flow of the data management method comprises the following steps.

101, receiving an operation request of a service system from a user terminal for data, where the operation request includes an inquiry request, and the inquiry request carries inquiry authority information.

In this embodiment, the operation request includes a query request, and correspondingly, the database operation statement includes a database query statement, the operation on the data includes querying the data, and the operation result of the operation on the data includes a query result.

And receiving an inquiry request for inquiring the data from a service system of the user terminal. The inquiry request can be triggered by a user, the user triggers the inquiry request and then sends the inquiry request to the server through the service system of the user terminal, and the service system of the server receives the inquiry request.

The query request carries query authority information, which includes security level information of the user, and in some embodiments, may also be other information representing query authority.

And 102, generating a query instruction according to the query authority information, wherein the query instruction carries the target label parameters determined according to the query authority information.

And determining target label parameters according to the query authority information, and generating a query instruction according to the target label parameters.

In one embodiment, step 102 includes: generating a database query statement according to the query request, and analyzing the database query statement; determining target label parameters according to the inquiry authority information; and modifying the analyzed database query statement according to the target label parameter to generate a query instruction.

And a service processing module of a service system in the server generates a database query statement according to the query request. Such as converting the query request into a database query statement. For example, staff member information in which the user number (uid) in the staff member table (employees) is larger than 856 and smaller than 1200 is inquired. Correspondingly, the query statement is converted into a database query statement SELECET FROM components WHERE 856 and uid <1200, and the database query statement is taken as an example in the embodiment of the present application for description. It should be noted that, if the employee information in the employee number (uid) of the query employee table (employees) is greater than 856, the maximum value max of the user number needs to be obtained, and the maximum value max is converted into the database query statement SELECET FROM members WHERE the ue uid >856 and uid < max.

And the service processing module calls a data query interface in the analysis processing module and transmits the generated database query statement and the acquired query authority information to the data query interface.

And the analysis processing module generates a query instruction by using the data query interface according to the transmitted database query statement and the query authority information. Specifically, the database query statement is analyzed by using the data query interface to obtain a query condition, for example, the database query statement is analyzed to obtain a WHERE, the query condition is set after the WHERE, the target tag parameter is determined according to the query authority information, and the query condition is modified by using the target tag parameter to generate the query instruction.

For example, the security level information corresponding to the query right information is the second security level, which means that the user can only view data not higher than the second security level, and determine that the tag data not higher than the second security level includes 1000, 1001, and determine the target tag parameter according to the query right information, valid data in the query condition, and the data type of the field in the query condition, such as determining (uid >856 and uid <1200) or (uid >10000856 and uid <10001200) or (uid >10010856 and uid <10011200) as the target tag parameter, where the valid data in the query condition includes 856, 1200, and so on. Tag data (such as security level data) is added to the query conditions to obtain target tag parameters, so that the sensitivity of the data can be rapidly judged in the query process, corresponding sensitive information is filtered, and the operating efficiency of the sensitive data is greatly improved.

The determination of the target tag parameter needs to be determined according to the data type of the field in the query condition, which is understood as: if the data type corresponding to the field uid is a shape, when determining the target tag parameter, directly adding tag data in front of the valid data corresponding to the uid, but not adding a connector, character or character string such as "-", that is, adding no corresponding connector, character or character string between the tag data and the valid data. The same is true when the data corresponding to the uid is stored in the database. If the data type corresponding to the field uid is a character type (e.g., string type), when the target tag parameter is determined, a connector such as "-" may be added between the tag data and the valid data in the query condition, and the same connector may be added when the data corresponding to the uid is stored.

The determined query condition is uid >856 and uid <1200, and the query condition is modified according to the target tag parameter to obtain a modified query condition (uid >856 and uid <1200) or (uid >10000856 and uid <10001200) or (uid >10010856 or uid < 10011200). Correspondingly, the modified database query statement is SELECET FROM employees WHERE (uid >856 and uid <1200) or (uid >10000856 and uid <10001200) or (uid >10010856 or uid < 10011200).

And determining the modified database query statement as a corresponding query instruction.

103, sending a query instruction to the database to trigger the database to determine a target data table corresponding to the query instruction, wherein the element content of at least one element in the target data table includes valid data and tag data, and querying the target data table according to the target tag parameter to obtain a query result.

The server is connected with the corresponding server through the database connection interface, and sends the query instruction to the database through the database connection interface so as to trigger the database to determine the target data table corresponding to the query instruction, for example, the database determines that the target data table corresponding to the query instruction is employees, and queries the target data table according to the target label parameter so as to obtain a query result.

Wherein the element content of at least one element in the target data table comprises valid data and tag data. It should be noted that, since the tag data is added to the element content of at least one element in the data table of the database, the database query statement needs to be modified according to the target tag parameter in step 102. Because the query instruction comprises the target label parameter, after the database receives the query instruction, the query result can be obtained only by executing the query instruction to query.

And 104, receiving the query result fed back by the database, and processing the query result according to the tag data to obtain target effective data.

And a result set generation module of the server receives a query result fed back by the database, the query result is in a memory of the server, the query result may be stored in an array or a list or an object, and the query result is processed according to the tag data to obtain target effective data.

In one embodiment, step 104 comprises: matching the query result according to the tag data to obtain the element content of the target element; label data in the element content of the target element is subjected to label removal processing to obtain effective data in the target element; and taking the valid data in the target element of the query result and the valid data in other elements as target valid data.

And matching the query result according to the tag data, and performing matching by using a wildcard corresponding to the tag data to obtain the element content of the target element including the tag data, for example, the element content of the target element includes the tag data and valid data. And performing label removal processing on the label data in the element content of the target element to obtain effective data in the target element. For example, the tag data in the element content of the target element is deleted to obtain valid data in the target element. And taking the valid data in the target element in the query result and the valid data in other elements as target valid data.

Understandably, some elements in the query result may include tag data and valid data in their element content, and some elements may include only valid data in their element content. Therefore, the target element in the query result is determined, label data in the element content of the target element is de-labeled to obtain effective data in the target element, and finally the effective data of all elements in the query result is used as the target effective data.

And after the result set generation module obtains the target effective data, sending the target effective data to a service system in the server.

And 105, sending the target effective data to the user terminal to trigger the user terminal to display the target effective data on a graphical interface of a business system of the user terminal.

And the server sends the target effective data to the user terminal through the service system so as to trigger the user terminal to display the target effective data.

The operation request in the above embodiment describes the processing flow of the data management method as an example of the query result.

It can be understood that, in the target data table in the embodiment of the present application, the element is used as a tag unit, and tag data is added to valid data in the element, so that when data is tagged (tag data is added), the granularity of the tag is used as the granularity of the element, and the granularity of the tag is small, thereby improving the precision of data tagging. Moreover, the effective data and the corresponding label data are stored in the elements of the target data table, so that the label data and the effective data are combined to be used as element contents for storage, the label data and the effective data exist in the same data table, the reading speed of the label data is improved, and the effective data and the label data can be obtained only by inquiring once. In addition, the tag data and the valid data are stored in the same data table, another data table does not need to be re-established to store the corresponding tag information, and compared with a new data table for storing the corresponding tag information, the scheme in the embodiment of the application does not need to be newly established, so that the storage speed of the tag data and the valid data and the reading speed of the tag data and the valid data are also improved.

Fig. 3 is another schematic flow chart of a data management method according to an embodiment of the present application. The data management method is applied to the server and comprises the following steps.

Receiving an operation request of a service system from a user terminal to data, where the operation request includes an insertion request or a modification request, and the operation request carries tag data for tagging the data and a tagging range for tagging the data.

In this embodiment, the operation request includes an insertion request and a modification request. When the operation request is an insertion request, correspondingly, the database operation statement comprises a database insertion statement, and the operation on the data comprises the insertion of the data; when the operation request is a modification request, correspondingly, the data operation statement comprises a database modification statement, and the operation on the data comprises the modification of the data.

The inserting request and the modifying request are also sent to the server through the service system of the user terminal, and the service system of the server receives the corresponding inserting request and the modifying request. The insertion request or the modification request carries tag data for marking data and a marking range for marking the data.

In this embodiment, the operation request includes an insertion request or a modification request, and the subsequent part in this embodiment is described by replacing the insertion request or the modification request with the operation request.

The tag data for marking data includes data representing security level information such as 1001, 1011, and 1100; the data representing the security level information may also be other types of data or strings of characters, etc. The tag range may include some or all fields in the operation request, which are referred to as tag fields, or may include tag fields and attribute value ranges of the tag fields in the operation request. In one embodiment, when there is tag data in the operation request, but there is no tag range, all fields are considered to be tagged, and correspondingly, the tag range is all fields.

When the marking range is all fields, it can also be understood as marking the whole record to be inserted/modified, i.e. marking the whole line of data to be inserted/modified.

And 202, generating an operation instruction according to the tag data and the mark range, wherein at least one element content to be operated in the operation instruction comprises the tag data and the valid data.

In one embodiment, step 202 comprises: generating a database operation statement according to the operation request, and determining a target marking field to be marked according to the marking range; analyzing a database operation statement to obtain an operation field, wherein the operation field comprises a target mark field; and modifying the element content of the element corresponding to the target mark field in the database operation statement according to the tag data to generate an operation instruction.

And the service processing module of the server generates a database operation statement according to the operation request. For example, the operation request is an insertion request, the insertion request inserts a record into the data table test _ table, the contents of the record are "datatime 1", "userid _ 1" and "content _ 1", respectively, and the database insertion statement is generated according to the insertion request: INSERT intotest _ table ('datetime', 'uid', 'content') VALUES ('datetime 1', 'userid _1', 'content _ 1').

And the service processing module determines a target marking field to be marked (and label data corresponding to the target marking field) according to the marking range.

After the target mark field (and the label data corresponding to the target mark field) is determined, the service processing module of the server calls a data insertion interface in the analysis processing module, and transmits the generated database insertion statement, the label data and the mark range to the data insertion interface.

And the analysis processing module generates an insertion instruction by using the data insertion interface according to the input database insertion statement, the tag data and the mark range. Specifically, the analysis processing module analyzes the database operation statement to obtain an operation field, wherein the operation field comprises a target mark field; and modifying the element content of the element corresponding to the target mark field in the database operation statement according to the tag data to generate an operation instruction.

For example, analyzing a database operation statement to obtain an INSERT INTO, and obtaining a data table test _ table after the INSERT INTO and before a VALUES, and corresponding operation fields datatime, uid and content; the data after the VALUES is acquired and corresponds to the attribute VALUES datatime1, userid _1, and content _1 of the fields datatime, uid, and content, respectively.

In an embodiment, when the tag range includes a tag field, the tag field may be at least one of a datetime, a uid, and a content. The step of determining the target mark field to be marked by the service processing module according to the mark range comprises the following steps: the business processing module determines a target operation field matched with the mark field according to the field of the generated database operation statement; and determining the target operation field as a target marking field to be marked, and determining the label data corresponding to the target marking field. And determining the target mark field and the label data corresponding to the target mark field according to a service processing module of the service system, so that the service system processes the corresponding service, and the analysis processing module only performs analysis and modification processing of SQL statements, does not mix any service, and realizes separation of the service and the analysis processing module.

After the target mark field (and the label data corresponding to the target mark field) is determined, the analysis processing module modifies the element content of the element corresponding to the target mark field in the database operation statement according to the label data. Specifically, the step of modifying, by the parsing processing module, the element content of an element corresponding to a target tag field in the database operation statement according to the tag data includes: tag data is added to the attribute value (namely, valid data) corresponding to the target mark field in the database operation statement, so that the element content of the element corresponding to the target mark field is modified. For example, tag data is added in front of the attribute value (i.e., valid data) corresponding to the target tag field.

The following description will take the target tag fields as datetime, uid, and content, and the corresponding tag data as 1011 as an example. In this embodiment, the tag data corresponding to each target tag field is the same, such as 1011. Modifying attribute VALUES (element contents of corresponding elements) corresponding to the datatime, uid and content fields according to the tag data 1011 to obtain modified database insertion statements INSERT _ table ('datatime', 'uid', 'content') VALUES ('1011-datatime 1', 1011userid _1', 1011-content _1'), and determining the modified database insertion statements as insertion instructions. After the corresponding data is inserted into the database, datatime1, userid _1, and content _1 are respectively valid data of the corresponding element, and 1011 is tag data of the corresponding element.

The following description will take examples in which the target tag field is datetime, uid, and content, and the corresponding tag data is 1011, 1101, and 1100. In this embodiment, the tag data corresponding to each target tag field is different, such as 1011, 1101, and 1100, respectively. Modifying attribute VALUES (element contents of corresponding elements) corresponding to the datatime, uid and content fields according to the tag data 1011, 1101 and 1100 to obtain modified database insertion statements INSERT _ table ('datatime', 'uid', 'content') VALUES ('1011-datatime 1', '1101userid _1', '1100-content _1'), and determining the modified database insertion statements as insertion instructions. Wherein, datatime1, userid _1, and content _1 are valid data of corresponding elements, and 1011, 1101, and 1100 are tag data of corresponding elements, respectively.

In an embodiment, when the tag range includes a tag field and a tag field attribute value range, the service system determines a target tag field to be tagged according to the tag range, including: the business system determines a target operation field matched with the mark field according to the field of the generated database operation statement; when the attribute value of the target operation field is in the corresponding attribute value range, determining the target operation field as a target mark field to be marked, and determining the label data corresponding to the target mark field; and when the attribute value of the target operation field is not in the corresponding attribute value range, not determining the target operation field as a target mark field to be marked.

For example, the flag field in the flag range includes uid and content, the attribute value range corresponding to the uid is uid >800, which indicates that the attribute value of uid >800 in the flag field uid is flagged, and the attribute value range corresponding to the content is: the "secret" is included in the content, which means that the attribute value including the "secret" is marked in the attribute value in the mark field content. Suppose that the data corresponding to the operation fields datatime, uid, and content to be currently inserted are "datatime 2", "860", "i am good", and the tag data is 1011, respectively. For the attribute value 860 of the uid field, it is determined 860>800, the service system determines the uid field as the target mark field, and for the attribute value "i am good" of the content field, it is determined that "secret" is not included in "i am good", the service system determines that the content field is not the target mark field, and it is not necessary to mark the attribute value of the content field.

After the target flag field uid (and the tag data 1011 corresponding to the target flag field) is determined, the parsing processing module modifies the attribute value of the target flag field uid in the database insertion statements INSERT _ table ('datetime', 'uid', 'content') VALUES ('datatime2', '860', 'good'), according to the tag data 1011, to obtain modified database insertion statements INSERT _ table ('datetime', 'uid', 'content'), value ('datetime 2', '10110860', 'good'), and determines the modified database insertion statements as insertion instructions. Here, the reason why 0 is added between the tag data "1011" and the valid data "856" is that the valid data cannot affect the tag considering that the data itself may be three-digit or four-digit data. The same principle is described below by taking as an example that the uid can reach four digits at maximum. It should be noted that if the uid can reach five bits at maximum, then two 0 s are added between the tag data "1011" and the valid data "856", and so on.

It is understood that the element content (attribute value of element content field of element) of at least one element to be operated in the above-mentioned resulting insertion instruction includes tag data and valid data.

It should be noted that, the above description is given by taking an insertion request as an example, the modification request and the insertion request are different only in SQL statements, and the manner of generating the operation instruction is similar to that of the insertion request, and specifically, please refer to the manner of generating the instruction corresponding to the insertion request.

And 203, sending the operation instruction to the database to trigger the database to determine a target data table corresponding to the operation instruction, and operating corresponding elements in the target data table according to the tag data and the effective data.

After the parsing processing module generates the operation instruction, the operation instruction is sent to the database, so that the database determines a target data table corresponding to the operation instruction, for example, determines that the target data table corresponding to the insertion instruction is a test _ table, and operates an element corresponding to the test _ table according to the tag data and the valid data, for example, inserting attribute values such as ('date 2', '10110860', 'i fine') into fields ('date 2', '10110860', 'i fine') in the test _ table, so as to respectively use the ('date 2', '10110860', 'i fine') as element contents of three corresponding elements.

And 204, receiving the operation result fed back by the database, and sending the operation result to the user terminal so as to trigger the user terminal to display the target effective data on a graphical interface of the service system of the user terminal.

After the database operation is completed, a corresponding operation result is sent to the server, for example: and the server forwards the operation result to the user terminal so as to display the corresponding operation result on a graphical interface of a service system of the user terminal and enable the user to know the condition of the request result of the operation request.

In this embodiment, the attribute value of the target flag field in the database operation statement is modified according to the tag data, so that the attribute value of the target flag field (element content of the corresponding element) includes not only valid data but also the tag data. On one hand, the tag data is added to the attribute value of the target tag field, or the tag data can be added to the effective data by taking the element as a unit, namely, the data is tagged by taking the element as a unit, so that the data tagging precision is improved; on the other hand, by processing the database operation statement to add the tag data in the attribute value of the target mark field, the tag data and the effective data are combined to be used as element content for storage, so that the tag data and the effective data are stored in the same data table, and the storage speed of the effective data and the tag data is improved; in addition, effective data and label data can be obtained only by inquiring once during inquiring, and the inquiring speed and the reading speed of the label data are improved. The embodiment of the application provides a brand-new mode for increasing and labeling data, and unexpected technical effects are achieved.

In an embodiment, the step of modifying the element content of the element corresponding to the target tag field in the database operation statement according to the tag data to generate the operation instruction includes: adding tag data in front of an attribute value (including valid data) corresponding to a target mark field in a database operation statement to obtain a modified attribute value (the attribute value is the element content of an element); encrypting the attribute values in the modified database operation statements; and determining the encrypted database operation statement as an operation instruction.

In this embodiment, the attribute values of the fields to be modified or the fields to be inserted (the attribute value of at least one field includes tag data and valid data) are encrypted, so that the encrypted attribute values are stored in the database. For example, if the (' datatime2', '10110860', ' i ' good ') is encrypted to obtain x1, x2, and x2, respectively, the encrypted database operation statement is INSERT intotest _ table (' datatime ', ' uid ', ' content ') VALUES (' x1', ' x2', ' x3'), and the database operation statement is determined as the operation instruction.

Different fields can be encrypted by using different encryption algorithms, and the like, and details are not repeated.

Correspondingly, after the database executes the operation instruction, the data stored in the database is also the corresponding encrypted data. Therefore, after the server receives the query instruction, the query instruction is obtained by using the analysis processing module, when the data in the target data table corresponding to the query instruction is detected to be encrypted data, the whole target data table is directly read from the database, the target data table is decrypted, and then the query instruction is used for querying to obtain a query result.

In an embodiment, when the operation request is not related to the service logic of the data tag, only the original database operation statement needs to be transferred when the interface corresponding to the parsing processing module is called, and further processing of the database operation statement is not needed in the parsing processing module. For example, when the server receives a table creation request for creating a data table, the service system generates a corresponding table creation statement, and then directly calls the table creation interface to send the corresponding database operation statement to the database, so as to trigger the database to execute.

In an embodiment, modifying tag data in a target field/target record in a target data table may also be implemented. Specifically, as shown in fig. 4, fig. 4 is a schematic flowchart of a data management method provided in an embodiment of the present application, where the data management method is applied to a server, and specifically includes the following steps.

301, receiving a tag modification request for the tag data from a service system of the user terminal, where the tag modification request is used to modify the tag data in the target field/target record of the target data table into the target tag data.

The tag modification request carries a target data table, a target field of the target data table or a target record and inquiry authority information in the target data table. When the tag modification request includes a target field of the target data table, it means that the tag data in the attribute column corresponding to the target field of the target data table is modified, and when the tag modification request includes a target record of the target data table, it means that the tag data in the target row corresponding to the target record of the target data table is modified.

It is noted that the data management method in this embodiment may also be used when no tag data is present in the target field/target record of the target data table, and thus the corresponding tag modification request is used to add a tag to the target field/target record of the target data table.

And 302, generating a tag query instruction according to the tag modification request, wherein the tag query request carries the primary key value of the target field/target record of the target data table.

The business processing module generates a database query statement according to the label modification request, calls a data query interface in the analysis processing module, and transmits the database query statement, the query authority information and the like into the value data query interface; and the analysis processing module receives the database query statement and the query authority information and generates a label query instruction according to the query authority information and the database query statement.

For example, the tag modification request is to modify tag data in professional information with a user number (uid) of 800 in an employee table (employees) (modify a target record in a target data table, wherein a primary key value of the target record is uid), and assume that all tag data existing in a business system of a server includes 1000, 1001, and 1011. Correspondingly, the tag query instruction generated by the tag modification request includes: SELECET FROM fans skins tier uid =800 or uid =10000800 or uid =10010800 or uid = 10110800; or the query may be performed in a wildcard manner, and the corresponding tag query instruction generated by the tag modification request, for example, SELECET FROM members WHERE cause uid = "% 0800".

303, sending a tag query instruction to the database, and receiving a tag query result fed back by the database based on the tag query instruction.

And 304, generating a data modification instruction according to the label query result and the target label data.

The service processing module generates a database modification statement according to the tag query result, the target field/target record, and the like (note that the tag modification request may also include modification of valid data, and thus, the database modification statement includes modification of valid data), and sends the database modification statement, the target field/target record, the target tag data, and the like to a data modification interface of the parsing processing module, and the parsing processing module receives the database modification statement, the target field/target record, and the target tag data, and adds the target tag data to an attribute value (i.e., valid data) corresponding to the target field/target record in the database modification statement, so as to modify the element content of an element corresponding to the target tag field. For example, the target tag data is added in front of the attribute value (i.e., valid data) corresponding to the target field/target record.

Assuming that the employee table includes fields of uid, name, gender, etc., the target tag data is 1101, and the corresponding tag query result includes 10110800, wang, maid. Generating a data modification instruction according to the label query result and the target label data, wherein the data modification instruction comprises the following steps: UPDATE employees SET uid =11010800, name = 1101-king, gender = female WHERE uid = 10110800.

And 305, sending a data modification instruction to the database to trigger the database to update the tag data in the target field/target record into the target tag data according to the data modification instruction.

And 306, receiving the update result fed back by the database, and sending the update result to the user terminal to trigger the user terminal to display the update result on a graphical interface of the service system of the user terminal.

The feedback updating result comprises: and if the modification is successful or fails and other prompt information is received, the server forwards the update result to the user terminal, so that the corresponding update result is displayed on a graphical interface of a service system of the user terminal, and the user can know the condition of the request result of the label modification request.

The generated data query instruction in this embodiment is similar to the generated query instruction described above, and the generated data modification instruction is similar to the generated insertion request, which is specifically referred to the corresponding description above.

All the above technical solutions can be combined arbitrarily to form the optional embodiments of the present application, and are not described herein again.

In order to better implement the data management method according to the embodiment of the present application, an embodiment of the present application further provides a data management device, where the data management device is integrated in a server. Referring to fig. 5, fig. 5 is a schematic structural diagram of a data management device according to an embodiment of the present disclosure. The data management apparatus may include a receiving module 401, a processing module 402, a transmitting module 403, and a result set generating module 404.

A receiving module 401, configured to receive an operation request for data from a service system of a user terminal, where the operation request includes a query request, and the query request carries query permission information.

A processing module 402, configured to generate a query instruction according to the query permission information, where the query instruction carries a target tag parameter determined according to the query permission information.

A sending module 403, configured to send the query instruction to a database, so as to trigger the database to determine a target data table corresponding to the query instruction, where element content of at least one element in the target data table includes valid data and tag data, and query the target data table according to the target tag parameter, so as to obtain a query result.

The receiving module 401 is configured to receive a query result fed back by the database.

And a result set generating module 404, configured to process the query result according to the tag data to obtain target valid data.

The sending module 403 is further configured to send the target valid data to the user terminal, so as to trigger the user terminal to display the target valid data on a graphical interface of a service system of the user terminal.

In an embodiment, the processing module 402 includes a service processing module and an analysis processing module, and when the processing module 402 executes the step of generating the query instruction according to the query authority information, the following steps are specifically executed: the business processing module generates a database query statement according to the query request; the analysis processing module analyzes the database query statement and determines a target label parameter according to the query authority information; and modifying the analyzed database query statement according to the target label parameter to generate a query instruction.

In an embodiment, when the step of processing the query result according to the tag data to obtain the target valid data is executed, the result set generating module 404 specifically executes: matching the query result according to the tag data to obtain the element content of the target element; label data in the element content of the target element is subjected to label removal processing to obtain effective data in the target element; and taking the valid data in the target element of the query result and the valid data in other elements as target valid data.

In an embodiment, the operation request further includes an insertion request or a modification request, and the operation request carries tag data for tagging data and a tag range for tagging the data. Correspondingly, the processing module 402 is further configured to generate an operation instruction according to the tag data and the tag range, where element content of at least one element to be operated in the operation instruction includes the tag data and valid data. The sending module 403 is further configured to send the operation instruction to a database, so as to trigger the database to determine a target data table corresponding to the operation instruction, and operate the target data table according to the tag data and the valid data. The receiving module 401 is further configured to receive an operation result fed back by the database, and send the operation result to the user terminal, so as to trigger the user terminal to display the operation result on a graphical interface of the service system of the user terminal.

In an embodiment, when the processing module 402 executes the step of generating the operation instruction according to the tag data and the tag range, it specifically executes: generating a database operation statement according to the operation request, and determining a target marking field to be marked according to the marking range; analyzing a database operation statement to obtain an operation field, wherein the operation field comprises a target mark field, and modifying the element content of an element corresponding to the target mark field in the database operation statement according to the tag data to generate an operation instruction.

In an embodiment, the tag range includes a tag field, and when the processing module 402 performs the step of determining the target tag field to be tagged according to the tag range, the processing module specifically performs: determining a target operation field matched with the mark field from the fields of the database operation statement; and determining the target operation field as a target marking field to be marked.

In an embodiment, the tag range includes a tag field and an attribute value range of the tag field, and when the processing module 402 determines the target tag field to be tagged according to the tag range, the processing module specifically performs: determining a target operation field matched with the mark field from the fields of the database operation statement; when the attribute value of the target operation field is in the attribute value range, determining the target operation field as a target mark field to be marked; when the attribute value of the target operation field is not in the attribute value range, the target operation field is not determined as a target mark field to be marked.

In an embodiment, the receiving module 401 is further configured to receive a tag modification request for the tag data from a service system of the user terminal, where the tag modification request is used to modify the tag data in the target field/target record of the target data table into the target tag data. The processing module 402 is further configured to generate a tag query instruction according to the tag modification request, where the tag query request carries a primary key value of a target field/target record of a target data table. The sending module 403 is further configured to send the tag query instruction to a database. The receiving module 401 is further configured to receive a tag query result fed back by the database based on the tag query instruction. The processing module 402 is further configured to generate a data modification instruction according to the tag query result and the target tag data. The sending module 403 is further configured to send the data modification instruction to the database, so as to trigger the database to update the tag data in the target field/the target record into the target tag data according to the data modification instruction. The receiving module 401 is further configured to receive an update result fed back by the database, and send the update result to the user terminal, so as to trigger the user terminal to display the update result on a graphical interface of the service system of the user terminal.

Correspondingly, the embodiment of the application also provides a server. It should be noted that the method provided in the embodiment of the present application may also be executed in a terminal, and a server is taken as an example for description herein. As shown in fig. 6, fig. 6 is a schematic structural diagram of a server provided in the embodiment of the present application. The server 500 includes a processor 501 having one or more processing cores, memory 502 having one or more computer-readable storage media, and a computer program stored on the memory 502 and executable on the processor. The processor 501 is electrically connected to the memory 502. Those skilled in the art will appreciate that the server architectures depicted in the figures are not meant to be limiting with respect to the servers, and may include more or fewer components than those illustrated, or some components may be combined, or a different arrangement of components.

The processor 501 is a control center of the server 500, connects various parts of the entire server 500 using various interfaces and lines, performs various functions of the server 500 and processes data by running or loading software programs (computer programs) and/or modules stored in the memory 502, and calling data stored in the memory 502, thereby monitoring the server 500 as a whole.

In this embodiment of the present application, the processor 501 in the server 500 loads instructions corresponding to processes of one or more application programs into the memory 502, and the processor 501 runs the application programs stored in the memory 502 according to the following steps, so as to implement various functions:

receiving an operation request of a service system from a user terminal for data, wherein the operation request comprises a query request, and the query request carries query authority information; generating a query instruction according to the query authority information, wherein the query instruction carries a target label parameter determined according to the query authority information; sending the query instruction to a database to trigger the database to determine a target data table corresponding to the query instruction, wherein the element content of at least one element in the target data table comprises effective data and tag data, and querying the target data table according to the target tag parameter to obtain a query result; receiving a query result fed back by the database, and processing the query result according to the tag data to obtain target effective data; and sending the target effective data to the user terminal so as to trigger the user terminal to display the target effective data on a graphical interface of a service system of the user terminal.

The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.

Optionally, as shown in fig. 6, the server 500 further includes: touch-sensitive display screen 503, radio frequency circuit 504, audio circuit 505, input unit 506 and power 507. The processor 501 is electrically connected to the touch display screen 503, the radio frequency circuit 504, the audio circuit 505, the input unit 506, and the power supply 507, respectively. Those skilled in the art will appreciate that the server architecture shown in FIG. 6 is not meant to be limiting, and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The touch display screen 503 can be used for displaying a graphical user interface and receiving an operation instruction generated by a user acting on the graphical user interface. The touch display screen 503 may include a display panel and a touch panel. The display panel may be used, among other things, to display information entered by or provided to the user and various graphical user interfaces of the server, which may be made up of graphics, text, icons, video, and any combination thereof. Alternatively, the Display panel may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. The touch panel may be used to collect touch operations of a user on or near the touch panel (for example, operations of the user on or near the touch panel using any suitable object or accessory such as a finger, a stylus pen, and the like), and generate corresponding operation instructions, and the operation instructions execute corresponding programs. The touch panel may overlay the display panel, and when the touch panel detects a touch operation thereon or nearby, the touch panel transmits the touch operation to the processor 501 to determine the type of the touch event, and then the processor 501 provides a corresponding visual output on the display panel according to the type of the touch event. In the embodiment of the present application, the touch panel and the display panel may be integrated into the touch display screen 503 to implement input and output functions. However, in some embodiments, the touch panel and the touch panel can be implemented as two separate components to perform the input and output functions. That is, the touch display 503 can also be used as a part of the input unit 506 to implement an input function.

In the embodiment of the present application, the touch display screen 503 is used for presenting a graphical user interface and receiving an operation instruction generated by a user acting on the graphical user interface.

The rf circuit 504 may be configured to transmit and receive rf signals to establish wireless communication with a network device or other server via wireless communication, and transmit and receive signals with the network device or other server.

The audio circuit 505 may be used to provide an audio interface between the user and the server through speakers, microphones. The audio circuit 505 may transmit the electrical signal converted from the received audio data to a speaker, and convert the electrical signal into a sound signal for output; on the other hand, the microphone converts the collected sound signal into an electrical signal, which is received by the audio circuit 505 and converted into audio data, and the audio data is processed by the audio data output processor 501, and then sent to another server via the rf circuit 504, or output to the memory 502 for further processing. The audio circuitry 505 may also include an earpiece jack to provide communication of a peripheral headset with the server.

The input unit 506 may be used to receive input numbers, character information, or user characteristic information (e.g., fingerprint, iris, facial information, etc.), and generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.

Power supply 507 is used to power the various components of server 500. Optionally, the power supply 507 may be logically connected to the processor 501 through a power management system, so as to implement functions of managing charging, discharging, power consumption management, and the like through the power management system. The power supply 507 may also include any component including one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.

Although not shown in fig. 6, the server 500 may further include a camera, a sensor, a wireless fidelity module, a bluetooth module, etc., which are not described in detail herein.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.

To this end, embodiments of the present application provide a computer-readable storage medium, in which a plurality of computer programs are stored, and the computer programs can be loaded by a processor to execute the steps in any data management method provided by the embodiments of the present application. For example, the computer program may perform the steps of:

Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.

Since the computer program stored in the storage medium can execute the steps in any data management method provided in the embodiments of the present application, beneficial effects that can be achieved by any data management method provided in the embodiments of the present application can be achieved, and detailed descriptions are omitted herein for the sake of detail in the foregoing embodiments.

The data management method, the data management device, the storage medium, and the server provided in the embodiments of the present application are described in detail above, and a specific example is applied in the present application to explain the principles and embodiments of the present application, and the description of the above embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A data management method, characterized in that the data management method comprises:

2. The data management method according to claim 1, wherein the step of generating the query instruction according to the query authority information includes:

generating a database query statement according to the query request;

analyzing the database query statement, and determining a target label parameter according to the query authority information;

and modifying the analyzed database query statement according to the target label parameter to generate a query instruction.

3. The data management method according to claim 1, wherein the step of processing the query result according to the tag data to obtain target valid data comprises:

matching the query result according to the tag data to obtain the element content of the target element;

label data in the element content of the target element is subjected to label removal processing to obtain effective data in the target element;

and taking the valid data in the target element of the query result and the valid data in other elements as target valid data.

4. The data management method according to claim 1, wherein the operation request further includes an insertion request or a modification request, and the operation request carries tag data for tagging data and a tag range for tagging the data, and the data management method further includes:

generating an operation instruction according to the tag data and the marking range, wherein the element content of at least one element to be operated in the operation instruction comprises the tag data and effective data;

sending the operation instruction to a database to trigger the database to determine a target data table corresponding to the operation instruction, and operating the target data table according to the tag data and the effective data;

and receiving an operation result fed back by the database, and sending the operation result to the user terminal so as to trigger the user terminal to display the operation result on a graphical interface of a service system of the user terminal.

5. The data management method of claim 4, wherein the step of generating an operation instruction according to the tag data and the tag range comprises:

generating a database operation statement according to the operation request;

determining a target marking field to be marked according to the marking range;

analyzing the database operation statement to obtain an operation field, wherein the operation field comprises a target mark field;

and modifying the element content of the element corresponding to the target mark field in the database operation statement according to the tag data to generate an operation instruction.

6. The data management method of claim 5, wherein the tag range includes a tag field; the step of determining a target mark field to be marked according to the mark range comprises the following steps:

determining a target operation field matched with the mark field from the field corresponding to the generated database operation statement;

and determining the target operation field as a target marking field to be marked.

7. The data management method of claim 6, wherein the tag range further comprises an attribute value range of the tag field; after the step of determining a target operation field matching the tag field from the field corresponding to the generated database operation statement, the data management method further includes:

when the attribute value of the target operation field is in the attribute value range, executing the step of determining the target operation field as a target mark field to be marked;

when the attribute value of the target operation field is not in the attribute value range, the target operation field is not determined as a target mark field to be marked.

8. The data management method according to claim 1, wherein the operation request further includes a tag modification request for tag data, the tag modification request being used to modify the tag data in a target field or a target record of a target data table into the target tag data, the data management method further comprising:

generating a tag query instruction according to the tag modification request, wherein the tag query request carries a target field of a target data table or a primary key value of a target record;

sending the label query instruction to a database, and receiving a label query result fed back by the database based on the label query instruction;

generating a data modification instruction according to the label query result and the target label data;

sending the data modification instruction to the database to trigger the database to update the tag data in the target field or the target record into the target tag data according to the data modification instruction;

and receiving an updating result fed back by the database, and sending the updating result to the user terminal so as to trigger the user terminal to display the updating result on a graphical interface of a service system of the user terminal.

9. A data management apparatus, comprising:

10. A server, characterized in that the server comprises a memory in which a computer program is stored and a processor which performs the steps in the data management method according to any one of claims 1 to 8 by calling the computer program stored in the memory.