CN112989138B - Data query method, device, equipment and readable storage medium - Google Patents
Data query method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN112989138B CN112989138B CN201911272784.2A CN201911272784A CN112989138B CN 112989138 B CN112989138 B CN 112989138B CN 201911272784 A CN201911272784 A CN 201911272784A CN 112989138 B CN112989138 B CN 112989138B
- Authority
- CN
- China
- Prior art keywords
- account
- target
- data
- group
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/90335—Query processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/9035—Filtering based on additional data, e.g. user or group profiles
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/9038—Presentation of query results
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application discloses a data query method, a device, equipment and a readable storage medium, and relates to the field of data processing. The method comprises the following steps: receiving a data query request of a first account sent by a client; acquiring a target account group corresponding to the first account according to the data query request, wherein the target account group comprises at least two associated accounts, and a binding relation is arranged between the at least two associated accounts; obtaining result data corresponding to at least two associated accounts respectively; and feeding back the result data set to the client. When a data query request sent by a first account is received, a target account group corresponding to the first account is determined first, so that result data are obtained for all associated accounts in the target account group, a result data set is obtained, and a client displays the result data of the associated accounts, so that the result data of a plurality of associated accounts can be queried through single query, the data query efficiency is improved, and the data interaction process of the data query is simplified.
Description
Technical Field
The embodiment of the application relates to the field of data processing, in particular to a data query method, a device, equipment and a readable storage medium.
Background
With the development of terminal devices and applications in terminal devices, some applications for retrieving data in a server and querying the data by a user are more widely used, for example, game achievement querying application software is software installed on a terminal for querying game achievement.
In the related art, when a first account is logged in an application program, a data acquisition request with an identifier of the first account is sent to a server, the server acquires game data of the first account according to the data acquisition request, feeds back the game data to a terminal, and the terminal displays the game data.
However, when the game data is displayed in the above manner, when the user needs to switch the account to query, the user needs to switch the second account again and log in, and send a data acquisition request with the identifier of the second account to the server to query, so that the process of switching the account to query the data is complicated, and the query efficiency is low.
Disclosure of Invention
The embodiment of the application provides a data query method, a device, equipment and a readable storage medium, which can solve the problems of complicated process of switching account query data and low query efficiency. The technical scheme is as follows:
In one aspect, a data query method is provided, the method including:
receiving a data query request of a first account sent by a client;
acquiring a target account group corresponding to the first account according to the data query request, wherein the target account group comprises at least two associated accounts, the at least two associated accounts comprise the first account, and a binding relationship is arranged between the at least two associated accounts;
obtaining result data corresponding to each of the at least two associated accounts to obtain a result data set;
and feeding back the result data set to the client, wherein the client is used for displaying the result data corresponding to the at least two associated accounts.
In another aspect, a data query method is provided, the method including:
sending a data query request of a first account to a server;
receiving a result data set fed back by the server, wherein the result data set comprises result data corresponding to at least two associated accounts respectively, and the at least two associated accounts are accounts in a target account group corresponding to the first account and have a binding relationship with the at least two associated accounts;
And displaying the result data corresponding to the at least two associated accounts.
In another aspect, there is provided a data query apparatus, the apparatus comprising:
the receiving module is used for receiving a data query request of a first account sent by the client;
the acquisition module is used for acquiring a target account group corresponding to the first account according to the data query request, wherein the target account group comprises at least two associated accounts, the at least two associated accounts comprise the first account, and a binding relationship is arranged between the at least two associated accounts;
the acquisition module is further used for acquiring result data corresponding to each of the at least two associated accounts to obtain a result data set;
and the sending module is used for feeding back the result data set to the client, and the client is used for displaying the result data corresponding to the at least two associated accounts.
In another aspect, there is provided a data query apparatus, the apparatus comprising:
the sending module is used for sending a data query request of the first account to the server;
the receiving module is used for receiving a result data set fed back by the server, wherein the result data set comprises result data corresponding to at least two associated accounts respectively, and the at least two associated accounts are accounts in a target account group corresponding to the first account and have a binding relation with the at least two associated accounts;
And the display module is used for displaying the result data corresponding to the at least two associated accounts.
In another aspect, a computer device is provided, where the computer device includes a processor and a memory, where the memory stores at least one instruction, at least one program, a set of codes, or a set of instructions, where the at least one instruction, the at least one program, the set of codes, or the set of instructions are loaded and executed by the processor to implement a data query method according to any one of the embodiments of the present application.
In another aspect, a computer readable storage medium is provided, where at least one instruction, at least one program, a set of codes, or a set of instructions is stored, where the at least one instruction, the at least one program, the set of codes, or the set of instructions are loaded and executed by the processor to implement a data query method according to any one of the embodiments of the present application.
In another aspect, a computer program product is provided, which when run on a computer causes the computer to perform the data query method according to any of the embodiments of the application as described above.
The technical scheme provided by the embodiment of the application has the beneficial effects that at least:
When a data query request sent by a first account is received, a target account group corresponding to the first account is determined first, so that result data are obtained for all associated accounts in the target account group, a result data set is obtained, and a client displays the result data of the associated accounts, so that the result data of a plurality of associated accounts can be queried through single query, the data query efficiency is improved, and the data interaction process of the data query is simplified.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a related art data query system;
FIG. 2 is a schematic diagram of a related art process for performing data query by a data query system;
FIG. 3 is a block diagram of a data query system provided in accordance with an exemplary embodiment of the present application;
FIG. 4 is a flow chart of a method of querying data provided by an exemplary embodiment of the present application;
FIG. 5 is a flow chart of a method of querying data provided in another exemplary embodiment of the application;
FIG. 6 is a schematic diagram of an account group provided based on the embodiment shown in FIG. 5;
FIG. 7 is a flow chart of a method of querying data provided in another exemplary embodiment of the application;
FIG. 8 is a schematic diagram of a data setup interface and a data presentation interface provided based on the embodiment shown in FIG. 7;
FIG. 9 is an overall flow chart of a data query method provided by an exemplary embodiment of the present application;
FIG. 10 is a block diagram of a data querying device provided in an exemplary embodiment of the present application;
FIG. 11 is a block diagram of a data querying device provided in accordance with another exemplary embodiment of the present application;
FIG. 12 is a block diagram of a data querying device provided in an exemplary embodiment of the present application;
fig. 13 is a block diagram of a server according to an exemplary embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.
First, a process of switching data query between account a and account B in the related art is schematically described, and fig. 1 is a schematic structural diagram of a data query system in the related art, as shown in fig. 1, where the system includes a client 110 and a data query server 120, where the data query server 120 is configured to provide a data query service to the client 110.
Optionally, the data query server 120 includes a login server 121, a community database server 122, a logic server 123, and a game database server 124;
the login server 121 is configured to manage a login procedure of the client 110, and the login server 121 manages the login procedure of the client 110 according to account data stored in the community database server 122. After the client 110 sends a login request including the account a to the login server 121, the login server 121 sends a first data request to the community database server 122, where the first data request is used to request to obtain login information of the account a, and after the community database server 122 feeds back the login information to the login server 121, the login server 121 feeds back a login result to the client 110.
Optionally, after the client 110 logs in the account a, the client 110 sends a game data query request to the logic server 123, the logic server 123 sends a second data request to the game database server 124, where the second data request is used to request to obtain the game data of the account a, and after the logic server 123 receives the game data fed back by the game database server 124, the game data is fed back to the client 110 for display.
Illustratively, in connection with the above data query system, the data query process please refer to fig. 2, and the query process includes: in step 201, the client determines whether to log in. In step 202, the client sends a request for logging in account a to the login server. In step 203, the login server sends a first data request to the community database server. In step 204, the community database server feeds back the login result. In step 205, the login server feeds back the login result to the client. In step 206, the client sends a game data query request for account a to the logical server. The logic server sends a second data request to the game database server, step 207. In step 208, the game database server feeds back the game data of account a to the logical server. In step 209, the logic server feeds back the game data of account a to the client. In step 210, the client sends a request to login server to login account B. Step 211, the login server sends a third data request to the community database server. In step 212, the community database server feeds back the login result. In step 213, the login server feeds back the login result to the client. In step 214, the client sends a game data query request for account B to the logical server. The logic server sends a fourth data request to the game database server, step 215. In step 216, the game database server feeds back the game data of account B to the logical server. In step 217, the logic server feeds back the game data of account B to the client.
As can be seen from the above process, in the related art, when the game data of the account a and the account B are queried, after logging in to the account a and the account B, the game data are queried respectively, the query process is complicated, and the query efficiency is low.
FIG. 3 is a block diagram of a data query system according to an exemplary embodiment of the present application, including a client 300 and a data query server 320, as shown in FIG. 3;
optionally, the data query server 320 provides functions of account login, account data query, etc. to the client 300, in this embodiment, the data query server 320 provides functions of account login and account data query to the client 300, which is described by taking an example, where the data query server 320 may be implemented as a server or may be implemented as a server cluster formed by multiple servers, and optionally, the data query server 320 may be implemented as a physical server or may be implemented as a cloud server, which is not limited in this embodiment of the present application.
Optionally, in the embodiment of the present application, a server cluster formed by implementing the data query server 320 as a plurality of servers is taken as an example for explanation, as shown in fig. 3, the data query server 320 includes a login server 321, a community database server 322, a logic server 323, a game database server 324, and an account server 325;
The login server 321 is configured to manage a login procedure of the client 300, and the login server 321 manages the login procedure of the client 300 according to account data stored in the community database server 322. After the client 300 sends a login request including the account a to the login server 321, the login server 321 sends a first data request to the community database server 322, where the first data request is used to request to obtain login information of the account a, and after the community database server 322 feeds back the login information to the login server 321, the login server 321 feeds back a login result to the client 300.
Optionally, the account data stored in the community database server 322 is account data having a binding relationship, the community database server 322 stores account data of at least one account group, the account group includes at least two associated accounts, the at least two associated accounts includes a main account and a binding account, and the binding relationship exists between the main account and the binding account.
Optionally, after the account a is logged on the client 300, the client 300 sends a game data query request to the logic server 323, the logic server 323 firstly performs an account query to the account server 325 according to the data query request, the account server 325 sends a second data request to the community database server 322, the second data request is used for requesting to obtain all associated accounts in the account group corresponding to the account a, the community database server 322 feeds back the associated accounts to the account server 325, the account server 325 feeds back the associated accounts to the logic server 323, so that the logic server 323 sends a third data request to the game database server 324, the third data request is used for requesting to obtain game data of all associated accounts, the logic server 323 feeds back the game data to the client 300 after the game database server 324 feeds back the game data to the logic server 323, and the client 300 displays the game data of all associated accounts.
The data query method according to the embodiment of the present application will be described with reference to the above data query system. Fig. 4 is a flowchart of a data query method according to an exemplary embodiment of the present application, and the method is applied to the data query server shown in fig. 3, and as shown in fig. 4, the method includes:
step 401, receiving a data query request of a first account sent by a client.
Optionally, the first account is logged on the client, and the data query request is sent according to the first account logged on the client, or other accounts are logged on the client, and the data of the first account is queried by inputting the account identifier of the first account.
Optionally, taking the client having the first account logged in as an example, the client is provided with a data query function, and when the user selects the data query function, the data query request is sent to the server; or when the first account is logged in the client and started, the data query request is automatically sent to the server.
Optionally, the data query request includes an account identifier of the first account.
Alternatively, the first account may be an account applied when the user logs in to the target game, or an account applied when the user logs in to a target partition in the target game, that is, the user may be different when logging in to a different partition in the target game.
Illustratively, the target game comprises a partition 1, a partition 2 and a partition 3, and the user has game accounts in the partition 1, the partition 2 and the partition 3, wherein the user logs in the partition 1 through an account A, logs in the partition 2 through an account B and logs in the partition 3 through an account C. Optionally, the account a, the account B and the account C may be three parallel independent accounts, or may be a binding account corresponding to the same main account, or alternatively, the main account may be any one of the account a, the account B and the account C, for example: the account A is a main account, and the account B and the account C are bound with the account A; the main account may also be an independent account, and illustratively, the user corresponds to an account D in the social application program a, the target game is a game bound to the social application program, and the account a, the account B and the account C are bound accounts generated under the main account D when the user uses the target game.
Step 402, obtaining a target account group corresponding to the first account according to the data query request, wherein the target account group comprises at least two associated accounts.
Optionally, the at least two associated accounts have a binding relationship corresponding to each other, or a binding relationship exists between part of the associated accounts in the at least two associated accounts.
Optionally, the at least two associated accounts include a main account and a binding account, and the binding account and the main account have a binding relationship. Optionally, the binding accounts may or may not have a binding relationship.
Alternatively, the first account may correspond to one target account group or may correspond to multiple target account groups, which is not limited in the embodiment of the present application. Optionally, in the embodiment of the present application, an example is described in which the first account corresponds to a target account group.
Optionally, when the target account group is determined, an account having a binding relationship with the first account is obtained according to the data query request, so as to obtain the target account group. Optionally, the first account may be a main account in the target account group, or may be a binding account in the target account group.
Optionally, when the first account is implemented as a main account in the target account group, directly acquiring a binding account having a binding relationship with the first account to obtain the target account group; when the first account is realized as a binding account in the target account group, the main account in the target account group is determined first, so that the binding account in the target account group is determined according to the main account.
Optionally, taking the data query server as an example, the data query server includes a logic server, an account server and a community database server, the logic server receives a data query request sent by a client, and performs an account query to the account server according to the data query request, and after the account server obtains a target account group corresponding to the first account from the community database server, the account server sends an associated account in the target account group to the logic server, so that the logic server obtains the target account group corresponding to the first account.
Step 403, obtaining the result data corresponding to each of the at least two associated accounts, thereby obtaining a result data set.
Optionally, after determining the target account group, obtaining, for each associated account in the target account group, respective result data corresponding to each associated account.
Optionally, each associated account in the target account group corresponds to an account identifier, and the result data corresponding to each associated account is obtained according to the account identifier. Optionally, the result data set is obtained after integrating the result data of each associated account.
Optionally, the result data is game data of at least two associated accounts in the target game, optionally, the target game comprises at least two game partitions, and each associated account in the at least two associated accounts uniquely corresponds to one game partition. Optionally, each associated account corresponds to a game partition, and each game partition corresponds to an associated account, then the at least two associated accounts are parallel and independent accounts, the at least two associated accounts are associated through a main account, the main account can be any one account of the at least two associated accounts, that is, the main account and the binding account are also in parallel relationship, and a binding relationship exists between the main account and the binding account; the main account may also be a parent account of the at least two associated accounts, i.e. the parent account is a public account binding the at least two associated accounts.
Step 404, feeding back the result data set to the client.
Optionally, the client is configured to display result data corresponding to at least two associated accounts.
In summary, in the data query method provided in this embodiment, when a data query request sent by a first account is received, a target account group corresponding to the first account is first determined, so that result data is obtained for all associated accounts in the target account group, a result data set is obtained, and the client displays the result data of the associated accounts, so that the result data of a plurality of associated accounts can be queried through a single query, the data query efficiency is improved, and the data interaction process of the data query is simplified.
In an alternative embodiment, the first account may be a main account in the target account group, or may be a bound account in the target account group. Fig. 5 is a flowchart of a data query method according to an exemplary embodiment of the present application, and the method is applied to the data query server shown in fig. 3, and as shown in fig. 5, the method includes:
step 501, a data query request of a first account sent by a client is received.
Optionally, the first account is logged on the client, and a data query function is provided in the client. Optionally, the data query request includes an account identifier of the first account.
Step 502, when the first account is the main account in the target account group, obtaining at least one binding account having a binding relationship with the first account according to the data query request, and obtaining the target account group.
Optionally, when the first account is the main account in the target account group, the binding accounts with binding relation with the first account are obtained, that is, all the binding accounts in the target account group are obtained, so as to obtain the target account group.
Optionally, the first account is implemented as a main account in the target account group, and is also implemented as a bound account in the target account group, that is, the first account has two identities of the main account and the bound account, that is, the main account in the target account group defaults to be one of the bound accounts.
Referring to fig. 6, a schematic structure diagram of an account group according to an exemplary embodiment of the present application is shown, as shown in fig. 6, the account group 600 includes a main account 610 and a binding account 620, where the main account 610 (main account a) is also one of the binding accounts 620, and the binding account 620 includes an account a, an account B, an account C, a …, and an account N.
Optionally, the determining that the first account is the main account includes at least one of the following ways:
Firstly, acquiring at least one account with a binding relation with a first account according to a data query data request, when the at least one account comprises the first account, determining the first account as a main account in a target account group, and obtaining the target account group according to the at least one account, namely determining at least one binding account according to the first account;
and secondly, each main account corresponds to a main account identifier, when the first account corresponds to the main account identifier, determining that the first account is the main account in the target account group, and acquiring a binding account (comprising the first account) with a binding relation with the first account to obtain the target account group.
In step 503, when the first account is a binding account in the target account group, a second account having a binding relationship with the first account is determined according to the data query request, where the second account is a main account in the target account group.
Optionally, the determining that the first account is a bound account includes at least one of the following ways:
firstly, when a second account with a binding relation with the first account is obtained according to a data query request, only a single account with the second account with the binding relation with the first account is included, and when the second account and the first account are two different accounts, the second account is determined to be a main account in a target account group, and the first account is a binding account in the target account group;
And secondly, each main account is corresponding to a main account identifier, when the first account is not corresponding to the main account identifier, the first account is determined to be a binding account in the target account group, and a second account with a binding relation with the first account is determined to be the main account in the target account group.
Step 504, at least one binding account having a binding relationship with the second account is obtained, and a target account group is obtained.
Optionally, if the second account is the main account in the target account group, all the bound accounts in the target account group can be obtained by acquiring the bound account having a binding relationship with the second account according to the second account, wherein the bound account in the target account group also includes the second account, that is, the second account is implemented as both the main account and the bound account in the target account group.
Step 505, obtaining the result data corresponding to at least two associated accounts in the target account group, and obtaining a result data set.
Optionally, after the logic server obtains at least two associated accounts in the target account group, determining account identifiers of the at least two associated accounts, and obtaining result data of the at least two associated accounts from the database server through the account identifiers of the at least two associated accounts to obtain a result data set.
Illustratively, taking the database server as a game database server for example, the logic server obtains game data of at least two associated accounts from the game database server through account identifiers of the at least two associated accounts, and obtains a game data set.
Step 506, feeding back the result data set to the client, where the client is configured to display the result data of at least two associated accounts.
Optionally, the client may display the result data of the at least two associated accounts in the same data display interface, or may display the result data of the associated accounts separately through each sub-interface in multiple sub-interfaces of the data display interface.
In summary, in the data query method provided in this embodiment, when a data query request sent by a first account is received, a target account group corresponding to the first account is first determined, so that result data is obtained for all associated accounts in the target account group, a result data set is obtained, and the client displays the result data of the associated accounts, so that the result data of a plurality of associated accounts can be queried through a single query, the data query efficiency is improved, and the data interaction process of the data query is simplified.
According to the method provided by the embodiment, when the first account is the main account in the target account group, the binding accounts with binding relation with the first account are directly obtained, and all the binding accounts (namely the associated accounts) in the target account group can be obtained, so that the result data of the associated accounts are obtained, the data query efficiency is improved, and the data interaction process of the data query is simplified.
When the first account is the binding account in the target account group, the method provided by the embodiment first determines the second account having a binding relationship with the first account, determines the second account as the main account in the target account group, and obtains all the binding accounts in the target account group through the second account, thereby obtaining the result data of the associated account, improving the efficiency of data query, and simplifying the data interaction process of data query.
In an alternative embodiment, the client needs to log in the first account first, so that the client can send a data query request for querying data of the first account, and fig. 7 is a flowchart of a data query method according to another exemplary embodiment of the present application, where the method is applied to the data query system shown in fig. 3, and as shown in fig. 7, the method includes:
In step 701, a client sends a login request to a server.
Optionally, the client is a data query client, and the data query client is used for querying game data, for example, the data query client can be used for querying game data of a single game, and can also be used for querying game data of a plurality of games.
Optionally, the client is configured to query game data of the target game.
Optionally, after the user inputs the first account and the password of the first account in the client, clicking the confirmation control to log in the first account in the client. Optionally, the first account is an account used by the user when logging in the target game, and the target game and the data query client are two associated and bound application programs.
In step 702, the server receives a login request sent by the client, where the login request is used to request to login a first account in the client.
Optionally, the client sends the login request to the login server, the login server obtains login information of the first account from the community database server according to the login request, compares the login information with request information in the login request, feeds back a login success message to the client when the request information is consistent with the login information, and feeds back a login failure message to the client when the request information is inconsistent with the login information.
And step 703, feeding back a login result to the client according to the login request.
Optionally, the login result includes any one of a login success message and a login failure message.
In step 704, the client receives the login result.
Step 705, the client sends a data query request of the first account to the server.
Optionally, the first account is logged in the client, and when the client sends a data query request to the server, the data query request of the first account is sent, that is, the data query request is used for requesting to query data corresponding to the first account.
In step 706, the server receives a data query request of the first account sent by the client.
Step 707, the server obtains a target account group corresponding to the first account according to the data query request, where the target account group includes at least two associated accounts.
Optionally, the logic server receives a data query request of the first account sent by the client, and sends an account query request to the account server according to the data query request, wherein the account query request comprises an account identifier of the first account. The account server obtains a target account group corresponding to the first account from a community database according to the account identifier, namely, obtains an associated account in the target account group where the first account is located, and optionally obtains a binding account with a binding relation with the first account to obtain the target account group when the first account is a main account in the target account group; when the first account is a binding account in the target account group, a second account corresponding to the first account (namely, a main account in the target account group) is firstly determined, and the binding account with a binding relation with the second account is obtained, so that the target account group is obtained.
Step 708, the server obtains the result data corresponding to each of the at least two associated accounts, and obtains a result data set.
Optionally, after obtaining at least two associated accounts in the target account group through the logic server, determining account identifiers of the at least two associated accounts, and obtaining result data of the at least two associated accounts from the database server through the account identifiers of the at least two associated accounts to obtain a result data set.
Illustratively, taking the database server as a game database server for example, the logic server obtains game data of at least two associated accounts from the game database server through account identifiers of the at least two associated accounts, and obtains a game data set.
In step 709, the server feeds back the result data set to the client.
Optionally, the client is configured to display result data corresponding to the at least two associated accounts.
In step 710, the client receives the result set data sent by the server.
And 711, the client displays the result data corresponding to the at least two associated accounts.
Optionally, the client may display the result data of the at least two associated accounts in the same data display interface, or may display the result data of the associated accounts separately through each sub-interface in multiple sub-interfaces of the data display interface.
Optionally, for the associated account in the target account group corresponding to the first account, the client further includes a data display option, where the data display option is used to provide the associated account where the client selects to display data and the associated account where the client does not display data, optionally, when the user closes the data display of the target associated account in the data display option, the client cancels displaying the data of the target associated account when displaying the result data corresponding to at least two associated accounts; or when the client sends a data query request to the server, adding a target account identifier of a target associated account to the data query request, wherein the target account identifier is used for indicating that the result data of the target associated account does not need to be acquired, so that the server does not contain the result data of the target associated account when feeding back the result data corresponding to at least two associated accounts to the client.
Referring to fig. 8, a data display option is included in the data setting interface 800, where the data display option includes an account a data display option, an account B data display option, and an account C data display option, where the account a data is turned on, the account B data is turned off, the account C data is turned on, and the currently logged-in account in the client is the account a, and game data of the account a, the account B, and the account C are obtained by querying the account a, so that the result data of the account a and the result data of the account C are displayed in the data display interface 810.
In summary, in the data query method provided in this embodiment, when a data query request sent by a first account is received, a target account group corresponding to the first account is first determined, so that result data is obtained for all associated accounts in the target account group, a result data set is obtained, and the client displays the result data of the associated accounts, so that the result data of a plurality of associated accounts can be queried through a single query, the data query efficiency is improved, and the data interaction process of the data query is simplified.
Illustratively, the above data query server includes a login server, a community database server, a logic server, a game database server, and an account server, and fig. 9 is an overall flowchart of a data query method according to an exemplary embodiment of the present application, and as shown in fig. 9, the method includes:
step 901, the client determines whether an account is logged in.
Optionally, when an account is logged in the client, the client is directly started to apply through the logged account.
In step 902, the client sends a login request of the account a to the login server.
Optionally, when the client side is not logged in with the account, the user performs login verification on the account a, where the verification mode includes password verification and biometric verification, for example: face recognition, fingerprint recognition, and the like.
And the client sends the verification information of the account A to a login server as a login request of the account A.
In step 903, the login server sends an account information acquisition request of the account a to the community database server.
Optionally, after receiving the login request of the account a, the login server sends an acquisition request for acquiring account information of the account a to the community database server, where the account information is used to verify the login request of the account a.
In step 904, the community database server feeds back account information of the account A to the login server.
In step 905, the login server feeds back the login result to the client according to the account information.
Optionally, when the account information of the account A is consistent with the verification information, a login success message is fed back to the client; and when the account information of the account A is inconsistent with the verification information, feeding back a login failure message to the client.
In step 906, the client sends a game data query request for account a to the logical server.
Optionally, after the account a is logged in the client, a game data query request may be automatically generated and sent to the logic server; the game data query request may also be sent to the logical server when the user triggers the data query function.
In step 907, the logical server sends an account group query request to the account server based on the game data query request.
Optionally, when the logic server receives the game data query request of the account a, it needs to determine the account group corresponding to the account a, that is, obtain the associated account in the account group corresponding to the account a.
In step 908, the account server obtains the associated account in the target account group corresponding to the account a from the community database server according to the account group query request.
Optionally, when the account a is the main account in the target account group, acquiring a binding account having a binding relationship with the account a from the community database server; when the account A is a binding account in the target account group, an account B (main account in the target account group) with a binding relation with the account A is obtained from the community database server, and the binding account with the binding relation with the account B is obtained.
In step 909, the account server performs account group processing on the associated account to obtain a target account group.
Optionally, after the binding account is obtained, the combination obtained by the binding account is determined as the target account group.
In step 910, the account server feeds back the associated account in the target account group to the logical server.
In step 911, the logic server sends a game data acquisition request to the game database server based on the associated account number.
Optionally, when the logic server sends a game data acquisition request to the game database server, the game data acquisition request includes an account identifier of the associated account, so as to acquire game data of the associated account.
In step 912, the game database server sends the game data corresponding to each of the associated accounts to the logic server.
In step 913, the logic server feeds back game data corresponding to each associated account to the client.
Optionally, the client is configured to display game data of at least one associated account.
In summary, in the data query method provided in this embodiment, when a data query request sent by a first account is received, a target account group corresponding to the first account is first determined, so that result data is obtained for all associated accounts in the target account group, a result data set is obtained, and the client displays the result data of the associated accounts, so that the result data of a plurality of associated accounts can be queried through a single query, the data query efficiency is improved, and the data interaction process of the data query is simplified.
Fig. 10 is a block diagram of a data query device according to an exemplary embodiment of the present application, and as shown in fig. 10, the device is applied to a server, for example, and includes: a receiving module 1010, an acquiring module 1020, and a transmitting module 1030;
a receiving module 1010, configured to receive a data query request of a first account sent by a client;
an obtaining module 1020, configured to obtain, according to the data query request, a target account group corresponding to the first account, where the target account group includes at least two associated accounts, the at least two associated accounts include the first account, and a binding relationship exists between the at least two associated accounts;
the obtaining module 1020 is further configured to obtain result data corresponding to each of the at least two associated accounts, to obtain a result data set;
and the sending module 1030 is configured to feed back the result data set to the client, where the client is configured to display the result data corresponding to the at least two associated accounts.
In an optional embodiment, the obtaining module 1020 is further configured to obtain the target account group by obtaining an account having the binding relationship with the first account according to the data query request.
In an optional embodiment, the at least two associated accounts include a main account and a binding account, the binding account and the main account have the binding relationship, and the first account is the main account in the target account group;
the obtaining module 1020 is further configured to obtain, according to the data query request, at least one binding account having the binding relationship with the first account, to obtain the target account group.
In an alternative embodiment, the main account is implemented as the main account and the bound account in the target account group at the same time;
the obtaining module 1020 is further configured to obtain at least one account having the binding relationship with the first account according to the data query request;
as shown in fig. 11, the apparatus further includes:
a determining module 1040, configured to determine, when the at least one account includes the first account, that the first account is the main account of the target account group; and obtaining the target account group according to the at least one account.
In an optional embodiment, the at least two associated accounts include a main account and a bound account, the bound account and the main account have the binding relationship, and the first account is the bound account in the target account group;
The apparatus further comprises:
a determining module 1040, configured to determine, according to the data query request, a second account having the binding relationship with the first account, where the second account is the main account in the target account group;
the obtaining module 1020 is further configured to obtain the target account group by obtaining at least one of the bound accounts having the binding relationship with the second account.
In an alternative embodiment, the main account is implemented as the main account and the bound account in the target account group at the same time;
the determining module 1040 is further configured to determine that the second account is the main account in the target account group when the second account and the first account are implemented as two different accounts.
In an optional embodiment, the receiving module 1010 is further configured to receive a login request sent by the client, where the login request is used to request to login the first account in the client;
the sending module 1030 is further configured to feed back a login result to the client according to the login request.
In an alternative embodiment, the result data is game data of the at least two associated accounts in a target game;
The target game comprises at least two game partitions, and each associated account in the at least two associated accounts uniquely corresponds to one game partition.
Fig. 12 is a block diagram of a data query device according to an exemplary embodiment of the present application, as shown in fig. 10, and the device is applied to a server, for example, and includes: a transmitting module 1210, a receiving module 1220 and a display module 1230;
a sending module 1210, configured to send a data query request of the first account to a server;
a receiving module 1220, configured to receive a result data set fed back by the server, where the result data set includes result data corresponding to at least two associated accounts, where the at least two associated accounts are accounts in a target account group corresponding to the first account and have a binding relationship between the at least two associated accounts;
and the display module 1230 is used for displaying the result data corresponding to the at least two associated accounts.
It should be noted that: the data query device provided in the above embodiment is only exemplified by the division of the above functional modules, and in practical application, the above functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the data query device and the data query method provided in the foregoing embodiments belong to the same concept, and specific implementation processes of the data query device and the data query method are detailed in the method embodiments and are not repeated herein.
Fig. 13 is a schematic diagram showing a structure of a server according to an exemplary embodiment of the present application. The server may be the data query server shown in fig. 3. Specifically, the present application relates to a method for manufacturing a semiconductor device.
The server 1300 includes a central processing unit (CPU, central Processing Unit) 1301, a system Memory 1304 including a random access Memory (RAM, random Access Memory) 1302 and a Read Only Memory (ROM) 1303, and a system bus 1305 connecting the system Memory 1304 and the central processing unit 1301. The server 1300 also includes a basic input/output system (I/O system, input Output System) 1306 to facilitate the transfer of information between the various devices within the computer, and a mass storage device 1307 for storing an operating system 1313, application programs 1314, and other program modules 1315.
The basic input/output system 1306 includes a display 1308 for displaying information, and an input device 1309, such as a mouse, keyboard, etc., for a user to input information. Wherein both the display 1308 and the input device 1309 are connected to the central processing unit 1301 through an input output controller 1310 connected to the system bus 1305. The basic input/output system 1306 may also include an input/output controller 1310 for receiving and processing input from a keyboard, mouse, or electronic stylus, among a plurality of other devices. Similarly, the input output controller 1310 also provides output to a display screen, a printer, or other type of output device.
The mass storage device 1307 is connected to the central processing unit 1301 through a mass storage controller (not shown) connected to the system bus 1305. The mass storage device 1307 and its associated computer-readable media provide non-volatile storage for the server 1300. That is, the mass storage device 1307 may include a computer-readable medium (not shown) such as a hard disk or compact disc read only memory (CD-ROM, compact Disc Read Only Memory) drive.
Computer readable media may include computer storage media and communication media without loss of generality. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, erasable programmable read-only memory (EPROM, erasable Programmable Read Only Memory), electrically erasable programmable read-only memory (EEPROM, electrically Erasable Programmable Read Only Memory), flash memory or other solid state memory technology, CD-ROM, digital versatile disks (DVD, digital Versatile Disc) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will recognize that computer storage media are not limited to the ones described above. The system memory 1304 and mass storage device 1307 described above may be referred to collectively as memory.
According to various embodiments of the application, the server 1300 may also operate by a remote computer connected to the network through a network, such as the Internet. I.e., the server 1300 may be connected to the network 1312 via a network interface unit 1311 coupled to the system bus 1305, or the network interface unit 1311 may be used to connect to other types of networks or remote computer systems (not shown).
The memory also includes one or more programs, one or more programs stored in the memory and configured to be executed by the CPU.
The embodiment of the application also provides a computer device, which comprises a processor and a memory, wherein at least one instruction, at least one section of program, code set or instruction set is stored in the memory, and the at least one instruction, the at least one section of program, the code set or the instruction set is loaded and executed by the processor to realize the data query method provided by each method embodiment.
Embodiments of the present application also provide a computer readable storage medium having stored thereon at least one instruction, at least one program, a code set, or an instruction set, where the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the data query method provided by the above method embodiments.
Alternatively, the computer-readable storage medium may include: read Only Memory (ROM), random access Memory (RAM, random Access Memory), solid state disk (SSD, solid State Drives), or optical disk, etc. The random access memory may include resistive random access memory (ReRAM, resistance Random Access Memory) and dynamic random access memory (DRAM, dynamic Random Access Memory), among others. The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The foregoing description of the preferred embodiments of the present application is not intended to limit the application, but rather, the application is to be construed as limited to the appended claims.
Claims (9)
1. A method of querying data, the method comprising:
Receiving a data query request of a first account sent by a client, wherein the first account is an account applied when a user logs in a target partition in a target game, the data query request comprises a target account identifier of a target associated account, the target associated account is an account in a target account group corresponding to the first account, the target account identifier is used for indicating that result data of the target associated account is not acquired, the target account identifier is obtained by selecting a data display option corresponding to a plurality of associated accounts in the target account group by the client, the target account group corresponds to the first account, and the data display option is used for providing an associated account of which the client selects display result data and an associated account of which the result data is not displayed;
determining a second account with a binding relation with the first account according to the data query request, wherein the second account is a main account in a target account group, the target account group comprises at least two associated accounts with the binding relation, the at least two associated accounts are parallel and independent accounts, the at least two associated accounts comprise the main account and the binding account, and the first account is the binding account in the target account group;
Obtaining at least one binding account with the binding relation with the second account from a community database server to obtain the target account group, wherein account data of at least one account group is stored in the community database server;
obtaining result data corresponding to at least two associated accounts except the target associated account in the target account group, and obtaining a result data set;
and feeding back the result data set to the client, wherein the client is used for displaying the result data corresponding to the at least two associated accounts except the target associated account.
2. The method according to claim 1, wherein the at least two associated accounts include a main account and a bound account, the bound account and the main account have the binding relationship, and the first account is the main account in the target account group;
the method further comprises the steps of:
and acquiring at least one binding account with the binding relation with the first account according to the data query request to obtain the target account group.
3. The method of claim 2, wherein the main account is implemented as both the main account and the bound account in the target account group;
The step of obtaining the target account group by obtaining at least one binding account having the binding relation with the first account according to the data query request, including:
acquiring at least one account having the binding relation with the first account according to the data query request;
when the at least one account includes the first account, determining that the first account is the main account of the target account group;
and obtaining the target account group according to the at least one account.
4. The method of claim 1, wherein the main account is implemented as both the main account and the bound account in the target account group;
before the obtaining at least one binding account having the binding relationship with the second account, the method further includes:
and when the second account and the first account are realized as two different accounts, determining that the second account is the main account in the target account group.
5. The method according to any one of claims 1 to 4, wherein before receiving the data query request of the first account sent by the client, the method further comprises:
Receiving a login request sent by the client, wherein the login request is used for requesting to login the first account in the client;
and feeding back a login result to the client according to the login request.
6. The method according to any one of claims 1 to 4, wherein the result data is game data of the at least two associated accounts in a target game;
the target game comprises at least two game partitions, and each associated account in the at least two associated accounts uniquely corresponds to one game partition.
7. A data querying device, the device comprising:
the receiving module is used for receiving a data query request of a first account sent by a client, wherein the first account is an account applied when a user logs in a target partition in a target game, the data query request comprises a target account identifier of a target associated account, the target associated account is an account in a target account group corresponding to the first account, the target account identifier is used for indicating that the result data of the target associated account is not acquired, the target account identifier is obtained by selecting data display options corresponding to a plurality of associated accounts in the target account group by the client, the target account group corresponds to the first account, and the data display options are used for providing the associated account of which the client selects and displays the result data and the associated account which does not display the result data;
The acquisition module is used for determining a second account with a binding relation with the first account according to the data query request, wherein the second account is a main account in a target account group, the target account group comprises at least two associated accounts with the binding relation, the at least two associated accounts are parallel and independent accounts, the at least two associated accounts comprise the main account and the binding account, and the first account is the binding account in the target account group;
the acquisition module is further configured to acquire at least one binding account having the binding relationship with the second account from a community database server, so as to obtain the target account group, where account data of at least one account group is stored in the community database server; obtaining result data corresponding to at least two associated accounts except the target associated account in the target account group, and obtaining a result data set;
and the sending module is used for feeding back the result data set to the client, and the client is used for displaying the result data corresponding to the at least two associated accounts except the target associated account.
8. A computer device comprising a processor and a memory, wherein the memory has stored therein at least one program that is loaded and executed by the processor to implement the data query method of any of claims 1 to 6.
9. A computer readable storage medium, wherein at least one program is stored in the storage medium, and the at least one program is loaded and executed by a processor to implement the data query method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911272784.2A CN112989138B (en) | 2019-12-12 | 2019-12-12 | Data query method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911272784.2A CN112989138B (en) | 2019-12-12 | 2019-12-12 | Data query method, device, equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112989138A CN112989138A (en) | 2021-06-18 |
| CN112989138B true CN112989138B (en) | 2023-10-17 |
Family
ID=76331688
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911272784.2A Active CN112989138B (en) | 2019-12-12 | 2019-12-12 | Data query method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112989138B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105553984A (en) * | 2015-12-18 | 2016-05-04 | 北京金山安全软件有限公司 | User account login management method and device and electronic equipment |
| CN108096838A (en) * | 2017-12-18 | 2018-06-01 | 广东欧珀移动通信有限公司 | Gift bag gets method, apparatus, server, mobile terminal and storage medium |
| US10055421B1 (en) * | 2017-04-14 | 2018-08-21 | Xactly Corporation | Pre-execution query optimization |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8812532B2 (en) * | 2007-01-08 | 2014-08-19 | Mazen A. Skaf | System and method for tracking and rewarding users |
| US9633120B2 (en) * | 2014-01-29 | 2017-04-25 | International Business Machines Corporation | Continuously blocking query result data for a remote query |
-
2019
- 2019-12-12 CN CN201911272784.2A patent/CN112989138B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105553984A (en) * | 2015-12-18 | 2016-05-04 | 北京金山安全软件有限公司 | User account login management method and device and electronic equipment |
| US10055421B1 (en) * | 2017-04-14 | 2018-08-21 | Xactly Corporation | Pre-execution query optimization |
| CN108096838A (en) * | 2017-12-18 | 2018-06-01 | 广东欧珀移动通信有限公司 | Gift bag gets method, apparatus, server, mobile terminal and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112989138A (en) | 2021-06-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108833521B (en) | Message pushing method, device, system, computer equipment and storage medium | |
| JP6985576B2 (en) | Business process systems, business data processing methods and equipment | |
| CN111478967B (en) | Request processing method and device | |
| US20150154293A1 (en) | Cloud system and cloud resource allocation method | |
| US8239535B2 (en) | Network architecture with load balancing, fault tolerance and distributed querying | |
| CN109672714A (en) | A kind of data processing method and distributed memory system of distributed memory system | |
| US9613100B2 (en) | System and method for cloud-storage support | |
| CN112860778B (en) | Database management method, device, equipment and medium for desktop application program | |
| CN112910880B (en) | Virtual room creating method, system, device, equipment and medium | |
| EP3306904A1 (en) | Automatic recharging system, method and server | |
| CN112101942A (en) | Transaction request processing method, system, device and equipment based on block chain | |
| CN111200649B (en) | Scheduling method and device and scheduling model generation method and device | |
| EP3901766A1 (en) | Offline configuration method and apparatus for smart device | |
| CN112989138B (en) | Data query method, device, equipment and readable storage medium | |
| CN111400266B (en) | Data processing method and system, and diagnosis processing method and device for operation event | |
| CN115004666A (en) | Registration method, device, equipment and storage medium of Internet of things equipment | |
| CN111343240A (en) | Service request processing method and device, electronic equipment and storage medium | |
| US10951600B2 (en) | Domain authentication | |
| CN112583890A (en) | Message pushing method and device based on enterprise office system and computer equipment | |
| CN112308660A (en) | Data processing method, device and system | |
| CN111694598A (en) | Software version package management method, device, equipment and medium | |
| CN112000945B (en) | Authorization method, device, equipment and medium based on artificial intelligence | |
| CN111191251A (en) | Data authority control method, device and storage medium | |
| CN111026565B (en) | Cluster management method and management system | |
| CN111144860B (en) | Order processing method, device, server and storage 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 | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40046389 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |