CN113505121A - Data processing method, device, server and storage medium - Google Patents

Data processing method, device, server and storage medium Download PDF

Info

Publication number
CN113505121A
CN113505121A CN202110571094.8A CN202110571094A CN113505121A CN 113505121 A CN113505121 A CN 113505121A CN 202110571094 A CN202110571094 A CN 202110571094A CN 113505121 A CN113505121 A CN 113505121A
Authority
CN
China
Prior art keywords
splicing
query
data
field
spliced
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.)
Pending
Application number
CN202110571094.8A
Other languages
Chinese (zh)
Inventor
邵帅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Dajia Internet Information Technology Co Ltd
Original Assignee
Beijing Dajia Internet Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Dajia Internet Information Technology Co Ltd filed Critical Beijing Dajia Internet Information Technology Co Ltd
Priority to CN202110571094.8A priority Critical patent/CN113505121A/en
Publication of CN113505121A publication Critical patent/CN113505121A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22Indexing; Data structures therefor; Storage structures
    • G06F16/2282Tablespace storage structures; Management thereof
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2457Query processing with adaptation to user needs

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The present disclosure relates to a data processing method, apparatus, server and storage medium, including: acquiring query fields to be spliced of each data generation condition; splicing the query fields to be spliced to obtain spliced query fields; correspondingly storing the splicing query field and the searched data in a cell of a data table; acquiring a user query field and splicing the user query field to obtain a user splicing query field; and determining target searched data fed back to the user according to the matching between the user splicing query field and the splicing query field stored in the cells of the data table. It can be seen that the splicing query field formed by splicing the query fields to be spliced of the data generation condition is stored in the cell of the data table, and when the query field to be spliced of the new generation condition is newly added subsequently, only the splicing query field in the cell is modified, that is, only the data row where the cell is located needs to be locked, and the data request of the user for other data rows is not affected.

Description

Data processing method, device, server and storage medium
Technical Field
The present disclosure relates to the field of computer device technologies, and in particular, to a data processing method, an apparatus, a server, and a storage medium.
Background
With the development of computer technology, data processing technology has emerged; one of the data processing technologies is to generate corresponding data according to data generation conditions selected by a user and return the data to the user; for example, in a scene that a user requests a festival greeting card, the user can select corresponding data generation conditions such as a card issuing object (e.g., dad, mom, brother, sister, coworkers, etc.) and a festival type (e.g., spring festival, morning festival), and the background server receives the data generation conditions selected by the user, generates the corresponding festival greeting card and feeds the festival greeting card back to the user. However, in the data processing technology provided in the conventional manner, if a new data generation condition is added, the response to the user data request is affected.
Disclosure of Invention
The present disclosure provides a data processing method, apparatus, server, and storage medium, to at least solve the problem in the related art that when a data generation condition is newly added, a response to a user data request is greatly affected. The technical scheme of the disclosure is as follows:
according to a first aspect of the embodiments of the present disclosure, there is provided a data processing method, including:
acquiring query fields to be spliced of each data generation condition;
splicing the query fields to be spliced to obtain spliced query fields;
correspondingly storing the splicing query field and the searched data in a cell of a data table; any data to be checked is formed according to the data generation condition corresponding to the splicing query field which is correspondingly stored;
acquiring a user query field and splicing the user query field to obtain a user splicing query field; the user query field is a query field selected by a user in the query fields to be spliced;
and determining target searched data fed back to the user according to the matching between the user splicing query field and the splicing query field stored in the cells of the data table.
In one embodiment, after the step of storing the concatenation query field in a cell of a data table corresponding to the data to be searched, the method further comprises:
determining a cell to be modified in the cells in which the splicing query field is stored;
splicing the newly-added query field to be spliced into the splicing query field of the cell to be modified to form a modified splicing query field; and the newly-added query field to be spliced is the query field to be spliced of the newly-added data generation condition.
In an embodiment, the step of splicing the newly added query field to be spliced into the splicing query field of the cell to be modified to form a modified splicing query field includes:
controlling the data line where the cell to be modified is located to be in a locked state;
and splicing the newly added query fields to be spliced into the splicing query fields of the cells to be modified when the data lines are in a locked state to form modified splicing query fields.
In one embodiment, after the step of splicing the newly added query field to be spliced into the splicing query field of the cell to be modified to form a modified splicing query field, the method further includes:
receiving a first user query field;
if the first user query field does not comprise the newly-added query field to be spliced, splicing the first user query field with a preset field to obtain a first user splicing query field; the preset field is a field aiming at the newly added query field to be spliced;
if the splicing query field of the first user is matched with the splicing query field, feeding back the searched data corresponding to the splicing query field to the first user; and the checked data corresponding to the modified splicing query field is the checked data corresponding to the splicing query field of the cell to be modified.
In one embodiment, after the step of storing the concatenation query field in a cell of a data table corresponding to the data to be searched, the method further comprises:
acquiring a newly added query field to be spliced of a newly added data generation condition;
splicing the newly-added query field to be spliced with the query field to be spliced to obtain a newly-added splicing query field;
correspondingly storing the newly added splicing query field and newly added checked data in cells of the data table; the cell for storing the newly added splicing inquiry field and the cell for storing the splicing inquiry field are in the same data column, and the cell for storing the newly added checked data and the cell for storing the checked data are in the same data column.
In an embodiment, the step of splicing the query fields to be spliced to obtain the spliced query fields includes:
determining the category of each data generation condition;
combining query fields to be spliced of the data generation conditions according to the categories of the data generation conditions to obtain a plurality of field groups; the fields to be spliced and inquired of the data generation conditions of the same category are located in different field groups;
splicing the query fields to be spliced included in the same field group to obtain the spliced query fields corresponding to the same field group.
In an embodiment, the step of splicing the query fields to be spliced included in the same field group to obtain the spliced query field corresponding to the same field group includes:
splicing the query fields to be spliced included in the same field group according to the category sequence of the data generation conditions to obtain spliced query fields corresponding to the same field group;
the step of splicing the user query fields to obtain the user spliced query fields comprises the following steps:
and splicing the user query fields according to the category sequence to obtain the user spliced query fields.
According to a second aspect of the embodiments of the present disclosure, there is provided a data processing apparatus including:
the field acquisition unit is configured to execute acquisition of the query fields to be spliced of the data generation conditions;
the first splicing unit is configured to splice the query fields to be spliced to obtain spliced query fields;
the storage unit is configured to store the splicing inquiry field and the checked data in a cell of a data table in a corresponding mode; any data to be checked is formed according to the data generation condition corresponding to the splicing query field which is correspondingly stored;
the second splicing unit is configured to execute obtaining of the user query field and splicing of the user query field to obtain a user splicing query field; the user query field is a query field selected by a user in the query fields to be spliced;
a first data feedback unit configured to perform determining target checked data fed back to the user according to matching between the user splicing query field and the splicing query field stored in the cell of the data table.
In one embodiment, the apparatus further includes a modification unit configured to perform determining a cell to be modified among the cells in which the concatenation query field is stored; splicing the newly-added query field to be spliced into the splicing query field of the cell to be modified to form a modified splicing query field; and the newly-added query field to be spliced is the query field to be spliced of the newly-added data generation condition.
In one embodiment, the modification unit is configured to perform control on a data line where the cell to be modified is located to be in a locked state; and splicing the newly added query fields to be spliced into the splicing query fields of the cells to be modified when the data lines are in a locked state to form modified splicing query fields.
In one embodiment, the apparatus further comprises a second data feedback unit configured to perform receiving the first user query field; if the first user query field does not comprise the newly-added query field to be spliced, splicing the first user query field with a preset field to obtain a first user splicing query field; the preset field is a field aiming at the newly added query field to be spliced; if the splicing query field of the first user is matched with the splicing query field, feeding back the searched data corresponding to the splicing query field to the first user; and the checked data corresponding to the modified splicing query field is the checked data corresponding to the splicing query field of the cell to be modified.
In one embodiment, the apparatus further includes a newly-added unit configured to execute a newly-added query field to be spliced for acquiring a newly-added data generation condition; splicing the newly-added query field to be spliced with the query field to be spliced to obtain a newly-added splicing query field; correspondingly storing the newly added splicing query field and newly added checked data in cells of the data table; the cell for storing the newly added splicing inquiry field and the cell for storing the splicing inquiry field are in the same data column, and the cell for storing the newly added checked data and the cell for storing the checked data are in the same data column.
In one embodiment, the first splicing unit is configured to determine a category to which each data generation condition belongs; combining query fields to be spliced of the data generation conditions according to the categories of the data generation conditions to obtain a plurality of field groups; the fields to be spliced and inquired of the data generation conditions of the same category are located in different field groups; splicing the query fields to be spliced included in the same field group to obtain the spliced query fields corresponding to the same field group.
In an embodiment, the first splicing unit is configured to splice the query fields to be spliced included in the same field group according to a category sequence of data generation conditions to obtain a spliced query field corresponding to the same field group;
and the second splicing unit is configured to splice the user query fields according to the category sequence to obtain the user spliced query fields.
According to a third aspect of the embodiments of the present disclosure, there is provided a server, including:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the above-described method.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium, wherein instructions, when executed by a processor of a server, enable the server to execute to implement the above method.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising computer programs/instructions which, when executed by a processor, implement the above method.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects: the splicing query field formed by splicing the query fields to be spliced of the data generation condition is stored in the cell of the data table, when the query field to be spliced of the new generation condition is added later, only the splicing query field in the cell is modified, namely only the data line where the cell is located needs to be locked, the data request of the user to other data lines is not influenced, the splicing query field of the user can be matched with the splicing query fields of the cells of other data lines, the searched data fed back to the user is determined, and the response influence on the data request of the user is reduced while the data generation condition is expanded.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
FIG. 1 is a diagram illustrating an application environment for a method of data processing, according to an exemplary embodiment.
FIG. 2 is a flow chart illustrating a method of data processing according to an exemplary embodiment.
FIG. 3 is a diagram illustrating a data table according to an exemplary embodiment.
FIG. 4 is a diagram illustrating a data table according to an exemplary embodiment.
FIG. 5 is a block diagram illustrating a data processing apparatus according to an example embodiment.
FIG. 6 is a block diagram illustrating a server in accordance with an example embodiment.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
The data processing method provided by the present disclosure may be applied to the application environment shown in fig. 1. Wherein the terminal 110 interacts with the server 120 through the network. The terminal 110 may be, but is not limited to, various mobile phones, tablet computers, wearable devices, notebook computers, and the like, and the server 120 may be implemented by an independent server or a server cluster formed by a plurality of servers.
Fig. 2 is a flowchart illustrating a data processing method according to an exemplary embodiment, where as shown in fig. 2, the data processing method is used in the server 120 of fig. 1, and includes the following steps:
in step S201, query fields to be spliced of each data generation condition are acquired.
The data generation condition mainly refers to a condition when data is generated, for example, in a scene of generating data such as a holiday greeting card, the data generation condition may be a card-issuing object (such as dad and mom), a holiday (such as spring festival and morning); for another example, in a scenario of generating data such as a letter template, the data generation condition may be a letter usage (e.g., thank you, job hunting letter, etc.), and a letter font (e.g., song style, regular style, etc.). The server may input the data generation condition into the data generation model so that the data generation model generates data that meets the input data generation condition based on the input data generation condition. For example, in a scene of generating data such as a holiday greeting card, the query field of the data generation condition with the card-issuing object being dad is a1, the query field of the data generation condition with the card-issuing object being mom is a2, and the query field of the data generation condition with the holiday being morning is B1. The query fields of the data generation conditions need to be spliced subsequently, so the query fields of the data generation conditions can also be called query fields to be spliced.
In step S202, the query fields to be spliced are spliced to obtain a spliced query field.
For example, if the query fields to be spliced of the data generation condition are a1, a2, B1 and B2, the server may splice the query fields to be spliced to obtain spliced query fields, such as a1-B1, a1-B2, a2-B1 and the like in fig. 1.
In step S203, the concatenation query field and the data to be searched are stored in a cell of a data table in a corresponding manner.
Any data to be checked is formed according to data generation conditions corresponding to the splicing query fields which are correspondingly stored; for example, the searched data (i) in fig. 1 is formed according to the data generation conditions corresponding to the concatenation query fields a1-B1, for example, the holiday greeting card is formed based on the data generation conditions that the card-issuing object is dad and the holiday is morning.
The server can store the spliced query field A1-B1 and the searched data corresponding to the spliced query field in the same data row/the same data column so as to realize the corresponding storage between the spliced query field and the searched data.
In step S204, obtaining a user query field and splicing the user query field to obtain a user splicing query field; and the user query field is a query field selected by the user in the query fields to be spliced.
The user query field may be a query field selected by a user from query fields (i.e., query fields to be spliced) of the data generation condition. For example, if the query fields selected by the user are a1 and B1 in the query fields to be spliced a1, a2, B1 and B2, the server receives the query fields selected by the user as a1 and B1, and splices the query fields selected by the user as a1 and B1 to obtain the user spliced query fields a 1-B1.
In step S205, target searched data fed back to the user is determined according to matching between the user concatenation query field and the concatenation query field stored in the cell of the data table.
After the server obtains the user splicing query fields A1-B1, the user splicing query fields A1-B1 are matched with the splicing query fields in the data table cells, and the target searched data fed back to the user is determined to be (r).
In the data processing method, the splicing query field formed by splicing the query fields to be spliced of the data generation conditions is stored in the cell of the data table, when the query field to be spliced of the new generation conditions is added later, only the splicing query field in the cell is modified, namely, only the data line where the cell is located needs to be locked, the data request of the user to other data lines is not influenced, the splicing query field of the user can be matched with the splicing query fields of the cells of other data lines, the searched data fed back to the user is determined, and the response influence on the data request of the user is reduced while the data generation conditions are expanded.
In an embodiment, after the server performs the above step of storing the concatenation query field and the data to be checked in the cells of the data table in a corresponding manner, the server may further perform the following steps: acquiring a newly added query field to be spliced of a newly added data generation condition; splicing the newly-added query field to be spliced with the query field to be spliced to obtain a newly-added splicing query field; correspondingly storing the newly added splicing query field and newly added checked data in cells of the data table; the cell for storing the newly added splicing inquiry field and the cell for storing the splicing inquiry field are in the same data column, and the cell for storing the newly added checked data and the cell for storing the checked data are in the same data column.
As shown in fig. 3, if the query fields to be spliced (which may be referred to as new query fields to be spliced) of the newly added data generation condition are C1 and C2, the server may splice C1 and C2 with the original query fields to be spliced a1, a2, B1 and B2, and the obtained newly added query fields are a1-B1-C1, a1-B2-C1, a2-B1-C1, a2-B2-C1, a1-B1-C2, a1-B2-C2, a2-B1-C2 and a 2-B2-C2; and the server acquires newly added checked data corresponding to the newly added splicing inquiry field, such as newly added splicing inquiry fields A1-B1-C1, A1-B2-C1, A2-B1-C1, A2-B2-C1, A1-B1-C2, A1-B2-C2, A2-B1-C2 and A2-B2-C2 which are respectively fifth, sixth, seventh, eight, ninth, seventh, ninth and ninth,
Figure BDA0003082622240000071
Then, the server determines the data column in which the cells storing the original splicing query fields A1-B1, A1-B2, A2-B1 and A2-B2 are located, and stores the newly added splicing query field into other cells of the data column; the server determines a data column for storing original searched data (i) to (iv), and stores the newly added searched data in other cells of the data column; the new splicing query field and the new data to be checked corresponding to the new splicing query field are stored in the same data line, for example, the new splicing query field a1-B1-C1 and the corresponding new data to be checked are stored in the same data line.
In the above embodiment, if a new data generation condition is added, the server may splice the corresponding new query field to be spliced with the original query field to be spliced to form a new splicing query field and store the new splicing query field in the cell of the data table; in the processing process, if the checked data requested by the user is (r), the data line where the data (r) is located is not operated and is in an unlocked state, the server can directly read the data (r) and return the data (r) to the user. In the processing method of the new data generation condition in the above embodiment, compared with the processing method of storing the query field to be spliced of the new data generation condition in the new data column, the new data column is not required to be generated while the data generation condition is expanded, so that the situation that all data rows (the whole data table) are locked due to the new data column is avoided, and the read-write operation on the original spliced query field and the corresponding data to be checked is not affected.
In an embodiment, after the server performs the above step of storing the concatenation query field and the data to be checked in the cells of the data table in a corresponding manner, the server may further perform the following steps: determining a cell to be modified in the cells in which the splicing query field is stored; splicing the newly-added query field to be spliced into the splicing query field of the cell to be modified to form a modified splicing query field; and the newly-added query field to be spliced is the query field to be spliced of the newly-added data generation condition.
For example, as shown in fig. 4, if the newly added concatenation query field of the newly added data generation condition is C1, the server may determine a cell to be modified from the cells in which the concatenation query field is stored, for example, the cell in which the concatenation query field a1-B1 is stored is used as the cell to be modified; next, the server may stitch the newly added stitching query field C1 into the stitching query field A1-B1, resulting in a modified stitching query field A1-B1-C1.
Further, if the newly added data generation conditions belong to the same class (if the card issuing object is a grandpa or a teacher, both the two data generation conditions are the same class as the card issuing object), the server may select one newly added splicing query field from the newly added query fields to be spliced of the newly added data generation conditions, and splice the newly added splicing query field with the splicing query field of the cell to be modified, if the newly added splicing query fields are C1 and C2, and the data generation conditions corresponding to the two newly added splicing query fields are the same class, the server may select C1 to splice the splicing query field of the cell to be modified.
In the above embodiment, if a new splicing query field needs to be added to an original splicing query field, the server may directly modify the splicing query field in the cell, and only the data row of the cell is locked without adding a new data column, so that the response influence on the user data request is reduced while the data generation condition is expanded.
Further, when the server performs the step of splicing the newly added query field to be spliced into the splicing query field of the cell to be modified to form the modified splicing query field, the server may further perform the following steps: controlling the data line where the cell to be modified is located to be in a locked state; and splicing the newly added query fields to be spliced into the splicing query fields of the cells to be modified when the data lines are in a locked state to form modified splicing query fields.
That is, when the splicing query field of the cell to be modified is modified, the server can only lock the data line where the cell to be modified is located, and does not need to lock other data lines, thereby reducing the response influence on the user data request.
Further, after the server performs the step of splicing the newly added query field to be spliced into the splicing query field of the cell to be modified to form the modified splicing query field, the following steps may be performed: receiving a first user query field; if the first user query field does not comprise the newly-added query field to be spliced, splicing the first user query field with a preset field to obtain a first user splicing query field; the preset field is a field aiming at the newly added query field to be spliced; if the splicing query field of the first user is matched with the splicing query field, feeding back the searched data corresponding to the splicing query field to the first user; and the checked data corresponding to the modified splicing query field is the checked data corresponding to the splicing query field of the cell to be modified.
Exemplarily, in a scenario of newly adding the query fields to be spliced C1 and C2 of the data generation condition, after modifying the original splicing query field in the data table and newly adding the splicing query field, the server obtains the data table as shown in fig. 4, and it can be seen that the queried data corresponding to the modified splicing query field a1-B1-C1 is the queried data corresponding to the splicing query field a1-B1 of the cell to be modified. At this time, if the query fields selected by the user (which may be referred to as a first user) are a1 and B1, and the first user query field does not include the newly added query-to-be-spliced field C1 or C2, it may be considered that the client used by the user is an old client, and the first user cannot select the newly added query-to-be-spliced field through the old client; therefore, the server may select any one of the newly added query fields to be spliced C1 and C2 as a preset field, and splice the first user query field with the preset field to obtain the first user splicing query field, such as a 1-B1-C1. Then, the server matches the first user splicing query field A1-B1-C1 with the splicing query field (which may be a modified splicing query field or a newly added splicing query field) in the data table, determines corresponding checked data (i) and (v), and optionally feeds back one checked data from the checked data (i) and (v) to the first user.
It can be seen that, in the above embodiment, after modifying the original splicing query field, if the user cannot select the newly added to-be-spliced query field of the newly added data generation condition through the old client, the server may splice the user query field with the preset field, and then determine the corresponding data to be searched, thereby implementing compatibility with the old client.
In an embodiment, when the server performs the step of splicing the query fields to be spliced to obtain the spliced query field, the server may perform the following steps: determining the category of each data generation condition; combining query fields to be spliced of the data generation conditions according to the categories of the data generation conditions to obtain a plurality of field groups; the fields to be spliced and inquired of the data generation conditions of the same category are located in different field groups; splicing the query fields to be spliced included in the same field group to obtain the spliced query fields corresponding to the same field group.
For example, in a scene of generating data such as a holiday greeting card, a data generation condition that a card issuing object is dad and a data generation condition that the card issuing object is mom both belong to the class of card issuing objects, so that the corresponding query fields a1 and a2 to be spliced are classified into different field groups; the data generation condition of the morning and the data generation condition of the spring festival, mom, belong to the festival category, so that the corresponding query fields B1 and B2 to be spliced are divided into different field groups. Thus, the servers may form field groups of (a1, B1), (a1, B2), (a2, B1), and (a2, B2). And then the server splices the query fields to be spliced of the same field group to obtain splicing query fields of A1-B1, A1-B2, A2-B1 and A2-B2.
In the above embodiment, when the data generation condition has the corresponding category to which the data generation condition belongs, the server splices the query fields to be spliced of the data generation conditions of different categories, so as to avoid that the query fields to be spliced of the data generation conditions of the same category are spliced into the same splicing query field, and the field matching cannot be normally performed due to condition errors.
Further, when the server performs the step of splicing the query fields to be spliced included in the same field group to obtain the spliced query field corresponding to the same field group, the server may further perform the following steps: and splicing the query fields to be spliced included in the same field group according to the category sequence of the data generation conditions to obtain the spliced query fields corresponding to the same field group. And when the server performs the step of splicing the user query fields to obtain the user spliced query fields, the server may further perform the following steps: and splicing the user query fields according to the category sequence to obtain the user spliced query fields.
That is, if the category order of the data generation conditions is the holiday-card-issuing object, the server splices the query fields to be spliced of each field group according to the category order, and the formed splicing query fields are B1-a1, B2-a1, B1-a2, and B2-a 2. Correspondingly, after receiving the user query field, the server may also perform concatenation according to the category order to form a user concatenation query field, such as B2-a 1. And matching the splicing query field of the user with the splicing query field in the data table to determine corresponding searched data.
In the above manner, the splicing query field and the user query field in the data table are formed according to the same category sequence, so that the normal operation of field matching is ensured.
In order to better understand the above method, an application example of the data processing method of the present disclosure is explained in detail below. The scene corresponding to the application example is a template for requesting a festival greeting card from a server by a user; the query fields of the original data generation conditions provided by the server to the user are A1-elder, A2-colleague, B1-spring festival and B2-afternoon festival; the query fields of the newly added data generation conditions are C1-cartoon style and C2-landscape style. In the data generation conditions, the data generation conditions corresponding to the query fields A1 and A2 belong to the class of card-issuing objects, the data generation conditions corresponding to the query fields B1 and B2 belong to the class of festivals, and the data generation conditions corresponding to the query fields C1 and C2 belong to the class of greeting card styles.
The server may include a database storing data tables;
the method comprises the steps that firstly, before new data generation conditions are added, a server splices query fields to be spliced of the different types of data generation conditions to obtain splicing query fields A1-B1, A1-B2, A2-B1 and A2-B2, and corresponding festival cards (firstly), (secondly), (thirdly) and (fourthly) are generated according to the splicing query fields; then, the server stores the splicing inquiry field and the festival greeting card in a cell of the data table correspondingly (as shown in fig. 3). The data table comprises a splicing query field data column, and the cells of the data column store each splicing query field.
If each query field is stored in different data columns, then when a new query field of a data generation condition is subsequently added, a data column needs to be added, the addition of the data column can cause all data rows to be locked, which is equivalent to the locking of the whole data table, and at this time, the server cannot perform read-write operation on any data row and cannot return a greeting card template required by a user to the user. In addition, when locking, complex operations such as copying a data table and synchronous updating need to be performed, which is too high in cost. In the processing mode, the query fields of the data generation conditions are spliced into one query field and stored in one cell, so that the spliced query fields are stored in one data column, and the data generation conditions are expanded conveniently.
And secondly, the server can generate a batch of festival greeting cards off line every day or at fixed time intervals and store the festival greeting cards in a database.
And thirdly, providing a plurality of query fields of the data generation conditions for the user by the client, and selecting the query fields from the query fields of the data generation conditions by the user at the client, wherein the categories of the data generation conditions corresponding to the query fields selected by the user are different, for example, the query fields selected by the user are A1 and B1. The query fields selected by the user are requested to the server through the online interface, the server splices the query fields selected by the user according to the splicing sequence of the spliced query fields in the data table, and the obtained spliced query fields of the user are A1-B1; then, the server matches the user splicing query field A1-B1 with the splicing query field in the data table, and determines a festival greeting card returned to the user; if the data table has a plurality of festival greeting cards corresponding to the user splicing query fields A1-B1, the server can randomly return one festival greeting card from the plurality of corresponding festival greeting cards to the user.
And fourthly, if the developers add the newly added query fields to be spliced C1 and C2 of the data generation conditions, splicing the newly added query fields to be spliced with the original query fields to be spliced by the server according to the mode of the first part to obtain the newly added query fields to be spliced, and correspondingly storing the newly added query fields to be spliced and the newly added data to be searched in the data table.
If the plurality of newly added data generation conditions belong to the same category and the category to which the newly added data generation condition belongs is not consistent with the category to which the original data generation condition belongs, the server may determine that any newly added concatenation query field in the newly added concatenation query fields of the newly added data generation conditions serves as a preset field, and concatenate the preset field into the original concatenation query field.
If the user query fields sent by the old client are a1 and B1 (equivalent to the request parameters), the server can splice the preset fields with the user query fields a1 and B1 sent by the old client to obtain user spliced query fields a1-B1-C1, and then perform query field matching.
The processing mode can enable the new client and the old client to meet the matching of the new data generation condition, and enable the server to be compatible with the new client and the old client.
In the application example, the online complex data generation algorithm is converted into simple database condition query, so that the interface performance is improved; moreover, the query fields of a plurality of data generation conditions are spliced and unified to the same query field, so that the later-stage data generation conditions are conveniently expanded, the addition, deletion and modification of the later-stage data generation conditions are supported, and the new and old client interface fields are compatible.
It should be understood that although the various steps in the flow charts of fig. 1-4 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 1-4 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
FIG. 5 is a block diagram illustrating a data processing apparatus according to an example embodiment. Referring to fig. 5, the apparatus includes:
a field obtaining unit 501 configured to perform obtaining of query fields to be spliced of each data generation condition;
a first splicing unit 502 configured to perform splicing on the query fields to be spliced to obtain spliced query fields;
a storage unit 503 configured to perform storing the concatenation query field and the data to be checked in a cell of a data table in a corresponding manner; any data to be checked is formed according to the data generation condition corresponding to the splicing query field which is correspondingly stored;
a second splicing unit 504, configured to perform obtaining of a user query field and splicing the user query field to obtain a user splicing query field; the user query field is a query field selected by a user in the query fields to be spliced;
a first data feedback unit 505 configured to perform determining target checked data fed back to the user according to matching between the user splicing query field and the splicing query field stored in the cell of the data table.
In one embodiment, the apparatus further includes a modification unit configured to perform determining a cell to be modified among the cells in which the concatenation query field is stored; splicing the newly-added query field to be spliced into the splicing query field of the cell to be modified to form a modified splicing query field; and the newly-added query field to be spliced is the query field to be spliced of the newly-added data generation condition.
In one embodiment, the modification unit is configured to perform control on a data line where the cell to be modified is located to be in a locked state; and splicing the newly added query fields to be spliced into the splicing query fields of the cells to be modified when the data lines are in a locked state to form modified splicing query fields.
In one embodiment, the apparatus further comprises a second data feedback unit configured to perform receiving the first user query field; if the first user query field does not comprise the newly-added query field to be spliced, splicing the first user query field with a preset field to obtain a first user splicing query field; the preset field is a field aiming at the newly added query field to be spliced; if the splicing query field of the first user is matched with the splicing query field, feeding back the searched data corresponding to the splicing query field to the first user; and the checked data corresponding to the modified splicing query field is the checked data corresponding to the splicing query field of the cell to be modified.
In one embodiment, the apparatus further includes a newly-added unit configured to execute a newly-added query field to be spliced for acquiring a newly-added data generation condition; splicing the newly-added query field to be spliced with the query field to be spliced to obtain a newly-added splicing query field; correspondingly storing the newly added splicing query field and newly added checked data in cells of the data table; the cell for storing the newly added splicing inquiry field and the cell for storing the splicing inquiry field are in the same data column, and the cell for storing the newly added checked data and the cell for storing the checked data are in the same data column.
In one embodiment, the first splicing unit is configured to determine a category to which each data generation condition belongs; combining query fields to be spliced of the data generation conditions according to the categories of the data generation conditions to obtain a plurality of field groups; the fields to be spliced and inquired of the data generation conditions of the same category are located in different field groups; splicing the query fields to be spliced included in the same field group to obtain the spliced query fields corresponding to the same field group.
In an embodiment, the first splicing unit is configured to splice the query fields to be spliced included in the same field group according to a category sequence of data generation conditions to obtain a spliced query field corresponding to the same field group;
and the second splicing unit is configured to splice the user query fields according to the category sequence to obtain the user spliced query fields.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Fig. 6 is a block diagram illustrating a server 600 for a data processing method according to an example embodiment. For example, the server 600 may be a server. Referring to fig. 6, server 600 includes a processing component 620 that further includes one or more processors and memory resources, represented by memory 622, for storing instructions, such as applications, that are executable by processing component 620. The application programs stored in memory 622 may include one or more modules that each correspond to a set of instructions. Further, the processing component 620 is configured to execute instructions to perform the above-described method of data processing.
The server 600 may also include a power component 624 configured to perform power management for the server 600, a wired or wireless network interface 626 configured to connect the server 600 to a network, and an input/output (I/O) interface 628. The server 600 may operate based on an operating system stored in memory 622, such as Window 88 over, Mac O8X, Unix, Linux, FreeB8D, or the like.
In an exemplary embodiment, a computer-readable storage medium comprising instructions, such as the memory 622 comprising instructions, executable by the processor of the server 600 to perform the above-described method is also provided. The storage medium may be a computer-readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, there is also provided a computer program product comprising computer programs/instructions which, when executed by a processor, implement the above-described method.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (10)

1. A data processing method, comprising:
acquiring query fields to be spliced of each data generation condition;
splicing the query fields to be spliced to obtain spliced query fields;
correspondingly storing the splicing query field and the searched data in a cell of a data table; any data to be checked is formed according to the data generation condition corresponding to the splicing query field which is correspondingly stored;
acquiring a user query field and splicing the user query field to obtain a user splicing query field; the user query field is a query field selected by a user in the query fields to be spliced;
and determining target searched data fed back to the user according to the matching between the user splicing query field and the splicing query field stored in the cells of the data table.
2. The data processing method according to claim 1, further comprising, after the step of storing the concatenation query field in a cell of a data table in correspondence with the data to be searched:
determining a cell to be modified in the cells in which the splicing query field is stored;
splicing the newly-added query field to be spliced into the splicing query field of the cell to be modified to form a modified splicing query field; and the newly-added query field to be spliced is the query field to be spliced of the newly-added data generation condition.
3. The data processing method according to claim 2, wherein the step of splicing the newly added query field to be spliced into the splicing query field of the cell to be modified to form a modified splicing query field comprises:
controlling the data line where the cell to be modified is located to be in a locked state;
and splicing the newly added query fields to be spliced into the splicing query fields of the cells to be modified when the data lines are in a locked state to form modified splicing query fields.
4. The data processing method according to claim 2, wherein after the step of splicing the newly added query field to be spliced into the splicing query field of the cell to be modified to form a modified splicing query field, the method further comprises:
receiving a first user query field;
if the first user query field does not comprise the newly-added query field to be spliced, splicing the first user query field with a preset field to obtain a first user splicing query field; the preset field is a field aiming at the newly added query field to be spliced;
if the splicing query field of the first user is matched with the splicing query field, feeding back the searched data corresponding to the splicing query field to the first user; and the checked data corresponding to the modified splicing query field is the checked data corresponding to the splicing query field of the cell to be modified.
5. The data processing method according to claim 1, further comprising, after the step of storing the concatenation query field in a cell of a data table in correspondence with the data to be searched:
acquiring a newly added query field to be spliced of a newly added data generation condition;
splicing the newly-added query field to be spliced with the query field to be spliced to obtain a newly-added splicing query field;
correspondingly storing the newly added splicing query field and newly added checked data in cells of the data table; the cell for storing the newly added splicing inquiry field and the cell for storing the splicing inquiry field are in the same data column, and the cell for storing the newly added checked data and the cell for storing the checked data are in the same data column.
6. The data processing method according to any one of claims 1 to 5, wherein the step of splicing the query fields to be spliced to obtain the spliced query fields comprises:
determining the category of each data generation condition;
combining query fields to be spliced of the data generation conditions according to the categories of the data generation conditions to obtain a plurality of field groups; the fields to be spliced and inquired of the data generation conditions of the same category are located in different field groups;
splicing the query fields to be spliced included in the same field group to obtain the spliced query fields corresponding to the same field group.
7. A data processing apparatus, comprising:
the field acquisition unit is configured to execute acquisition of the query fields to be spliced of the data generation conditions;
the first splicing unit is configured to splice the query fields to be spliced to obtain spliced query fields;
the storage unit is configured to store the splicing inquiry field and the checked data in a cell of a data table in a corresponding mode; any data to be checked is formed according to the data generation condition corresponding to the splicing query field which is correspondingly stored;
the second splicing unit is configured to execute obtaining of the user query field and splicing of the user query field to obtain a user splicing query field; the user query field is a query field selected by a user in the query fields to be spliced;
a first data feedback unit configured to perform determining target checked data fed back to the user according to matching between the user splicing query field and the splicing query field stored in the cell of the data table.
8. A server, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the method of any one of claims 1 to 6.
9. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of a server, enable the server to perform the method of any of claims 1-6.
10. A computer program product comprising computer instructions, characterized in that the computer instructions, when executed by a processor, implement the method of any of claims 1 to 6.
CN202110571094.8A 2021-05-25 2021-05-25 Data processing method, device, server and storage medium Pending CN113505121A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110571094.8A CN113505121A (en) 2021-05-25 2021-05-25 Data processing method, device, server and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110571094.8A CN113505121A (en) 2021-05-25 2021-05-25 Data processing method, device, server and storage medium

Publications (1)

Publication Number Publication Date
CN113505121A true CN113505121A (en) 2021-10-15

Family

ID=78009363

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110571094.8A Pending CN113505121A (en) 2021-05-25 2021-05-25 Data processing method, device, server and storage medium

Country Status (1)

Country Link
CN (1) CN113505121A (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106776809A (en) * 2016-11-24 2017-05-31 中国银联股份有限公司 A kind of data query method and system
CN107766381A (en) * 2016-08-22 2018-03-06 北京京东尚科信息技术有限公司 Data query method, system and electronic equipment
CN108228916A (en) * 2018-04-08 2018-06-29 中国联合网络通信集团有限公司 The querying method and device of data
CN109271411A (en) * 2018-09-28 2019-01-25 中国平安财产保险股份有限公司 Report form generation method, device, computer equipment and storage medium
CN109558432A (en) * 2017-09-27 2019-04-02 北京国双科技有限公司 Data processing method and device
JP2019125346A (en) * 2018-01-17 2019-07-25 株式会社 ビーアイマトリックスBi Matrix Co.,Ltd Data input/output system based on grid interface
CN111008191A (en) * 2019-10-30 2020-04-14 深圳震有科技股份有限公司 Completion method and device for database query and computer equipment

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107766381A (en) * 2016-08-22 2018-03-06 北京京东尚科信息技术有限公司 Data query method, system and electronic equipment
CN106776809A (en) * 2016-11-24 2017-05-31 中国银联股份有限公司 A kind of data query method and system
CN109558432A (en) * 2017-09-27 2019-04-02 北京国双科技有限公司 Data processing method and device
JP2019125346A (en) * 2018-01-17 2019-07-25 株式会社 ビーアイマトリックスBi Matrix Co.,Ltd Data input/output system based on grid interface
CN108228916A (en) * 2018-04-08 2018-06-29 中国联合网络通信集团有限公司 The querying method and device of data
CN109271411A (en) * 2018-09-28 2019-01-25 中国平安财产保险股份有限公司 Report form generation method, device, computer equipment and storage medium
CN111008191A (en) * 2019-10-30 2020-04-14 深圳震有科技股份有限公司 Completion method and device for database query and computer equipment

Similar Documents

Publication Publication Date Title
CN109558440B (en) Data batch processing method and device, computer equipment and storage medium
US7200806B2 (en) System and method for generating pre-populated forms
CN111177081B (en) Game log content query method, device, computer equipment and storage medium
CN111008521B (en) Method, device and computer storage medium for generating wide table
CN110427386B (en) Data processing method, device and computer storage medium
CN109788031A (en) Business datum acquisition methods, device, computer equipment and storage medium
CN111400246B (en) Asynchronous file import method, device, computer equipment and storage medium
CN112286934A (en) Database table importing method, device, equipment and medium
CN116452123A (en) Method and device for generating characteristic value of inventory item and computer equipment
US11151088B2 (en) Systems and methods for verifying performance of a modification request in a database system
CN107066522B (en) Database access method and device
CN111274004B (en) Process instance management method and device and computer storage medium
CN111522881B (en) Service data processing method, device, server and storage medium
CN108345699B (en) Method, device and storage medium for acquiring multimedia data
CN113505121A (en) Data processing method, device, server and storage medium
CN111538672A (en) Test case layered test method, computer device and computer-readable storage medium
CN112783866B (en) Data reading method, device, computer equipment and storage medium
US10042957B2 (en) Devices and methods for implementing dynamic collaborative workflow systems
EP3046307B1 (en) Processing method, device and system for data of distributed storage system
CN114489772A (en) Workflow execution method and device, storage medium and equipment
CN112231377A (en) Data mapping method, system, device, server and storage medium
CN111597240A (en) Data export method, data export device, computer equipment and storage medium
CN110737662A (en) data analysis method, device, server and computer storage medium
US20190370259A1 (en) Devices and methods for implementing dynamic collaborative workflow systems
CN113449003B (en) Information query method, device, electronic equipment and medium

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