Transaction record query method and device, equipment and medium

Abstract

The invention relates to the technical field of data processing, in particular to a transaction record query method and device, equipment and a medium, and is used for solving the problems of a query consumption event process and query timeout in the prior art. The method comprises the following steps: acquiring a query request of a transaction record, wherein the query request carries a customer channel number, a target jump page number and a display quantity of each page; determining a target business behavior table fragment where a first transaction record displayed in a target jump page is located and a target position in the target business behavior table fragment according to a first number of transaction records stored in the business behavior table fragment of each account corresponding to the customer channel number, the target jump page number and a display number of each page; and determining each target transaction record displayed on the target jump page according to the target position and the display number of each page. According to the method, the business behavior table is fragmented by the account, and only data in the business behavior table fragments of the account needs to be queried, so that the query range is narrowed, the database query efficiency is improved, and the query time consumption is shortened.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a transaction record query method, device, equipment and medium. Background Art

[0002] When customers of the new generation of electronic invoice system query transaction records through customer channels, since one customer channel number can be bound to multiple accounts one-to-many, it is equivalent to querying the transaction records of multiple accounts at the same time. When the front end displays the transaction records of all accounts bound to the customer's customer channel number to the customer, considering the page uniformity and loading time limit, it is required to implement customer transaction record query in the form of page turning. If a customer channel is bound to multiple accounts, and the number of transaction records for each account is large, the result return of the customer transaction record query not only needs to be paginated according to the jump page number and the number of displays per page, but also the impact of multiple different accounts bound to the channel on the query result pagination must be considered.

[0003] Therefore, according to the database design specifications and electronic invoice business processing logic, querying the transaction records of multiple accounts bound to the same channel involves two database tables: the business behavior table and the account and channel relationship table. Among them, the business behavior table records the transaction status of various businesses with the account as the dimension, and the account and channel relationship table records the binding relationship between the customer channel number and multiple accounts.

[0004] Among them, when using conventional paging query, the user enters the front-end page display requirements on the front-end page, and the front-end page display requirements include the customer channel number, the jump page number of the query results, and the number of displays per page; after the user enters the front-end page display requirements, the query request for the transaction record is determined, and the query request carries the customer channel number, the jump page number of the query results, and the number of displays per page. According to the customer channel number carried in the query request for the transaction record, the saved account and channel relationship table, and the business behavior table, the first transaction record related to all accounts bound to the customer channel number is determined; according to the position of the first transaction record in the business behavior table, the jump page number carried in the query request, and the number of displays per page, the position of the first transaction record displayed on the jump page in the business behavior table is determined, and according to the position and the number of displays per page, each transaction record displayed on the jump page in the business behavior table is searched to obtain the query result that meets the customer's paging requirements.

[0005] However, when querying using the conventional paging method, since the query is an online query and the business behavior table records the transaction status of all accounts, that is, the total amount of accumulated business transaction records is huge, it is easy to cause the database joint table query to take too long, resulting in query timeout, which has a negative impact on customer experience. Summary of the invention

[0006] The embodiments of the present application provide a transaction record query method, apparatus, device and medium to solve the problems of query consumption event process and query timeout in the prior art.

[0007] In a first aspect, the present application provides a transaction record query method, which is applied to an electronic device, and the method includes:

[0008] A query request for obtaining transaction records, wherein the query request carries a customer channel number, a target jump page number, and a display quantity per page;

[0009] Determine the target business behavior table shard where the first transaction record displayed on the target jump page is located and the target position in the target business behavior table shard according to the first number of transaction records stored in the business behavior table shard of each account corresponding to the customer channel number, the target jump page number, and the number of displays per page;

[0010] Each target transaction record to be displayed on the target jump page is determined according to the target position and the display quantity per page.

[0011] Through the above method, since the business behavior table is sharded by the account field, when the business behavior table is queried using the account corresponding to the customer channel number as the query condition, only the data in the business behavior table shard corresponding to the account needs to be queried, thereby narrowing the query scope, improving database query efficiency, and shortening query time.

[0012] In a possible implementation, determining each target transaction record displayed on the target jump page according to the target location and the display quantity per page includes:

[0013] Taking the target position of the target business behavior table shard as a starting point, query the transaction records of the number displayed per page, and determine the queried transaction records as each target transaction record displayed on the target jump page.

[0014] In a possible implementation, determining the target business behavior table shard where the first transaction record displayed on the target jump page is located and the target position in the target business behavior table shard according to the first number of transaction records stored in the business behavior table shard of each account corresponding to the customer channel number, the target jump page number, and the number of displays per page, includes:

[0015] Determine the query start row according to the target jump page number and the display quantity per page;

[0016] The target business behavior table shard and the target position are determined according to the first number of transaction records stored in each business behavior table shard and the query start row.

[0017] In a possible implementation, determining the target business behavior table shard according to the first number of transaction records stored in each business behavior table shard and the query start row includes:

[0018] According to the arrangement order of each business behavior table slice, the following steps are performed in sequence for each business behavior table slice until the target business behavior table slice is determined:

[0019] Determine whether the sum of the first number of transaction records stored in the business behavior table shard and the first number of transaction records stored in each business behavior table shard before the business behavior table shard is not less than the query start row;

[0020] If yes, then determining the business behavior table slice as the target business behavior table slice;

[0021] If not, continue to determine whether the sum of the first number of transaction records stored in the next business behavior table slice and the first number of transaction records stored in each business behavior table slice before the next business behavior table slice is not less than the step of querying the start row.

[0022] In a possible implementation, determining the target location according to the first number of transaction records stored in each business behavior table shard and the query start row includes:

[0023] Determine a first difference between the query start row and a first number of business behavior table shards before the target business behavior table shard;

[0024] According to the first difference, a target position of the first transaction record in the target business behavior table shard is determined.

[0025] In a possible implementation, determining the query start row according to the target jump page number and the display quantity per page includes:

[0026] Determine the number of transaction records displayed before the target jump page number according to the target jump page number and the number of displays per page;

[0027] The query start row is determined according to the number of transaction records displayed before the target jump page number.

[0028] In a second aspect, the present application provides a transaction record query device, the device comprising:

[0029] An acquisition module, used to acquire a query request for transaction records, wherein the query request carries a customer channel number, a target jump page number, and a display quantity per page;

[0030] a determination module, configured to determine a target business behavior table slice where a first transaction record displayed on a target jump page is located and a target position in the target business behavior table slice according to a first number of transaction records stored in the business behavior table slice of each account corresponding to the customer channel number, the target jump page number, and the number of displays per page;

[0031] A query module is used to determine each target transaction record displayed on the target jump page according to the target location and the display quantity per page.

[0032] In a possible implementation, the query module is specifically used to query the transaction records displayed per page with the target position of the target business behavior table shard as the starting point, and determine the queried transaction records as each target transaction record displayed on the target jump page.

[0033] In a possible implementation, the determination module is specifically used to determine the query starting row based on the target jump page number and the display quantity per page; determine the target business behavior table shard and the target position based on the first number of transaction records stored in each business behavior table shard and the query starting row.

[0034] In a possible implementation, the determination module is specifically used to execute the following steps in sequence for each business behavior table slice according to the arrangement order of each business behavior table slice until the target business behavior table slice is determined: determine whether the sum of the first number of transaction records stored in the business behavior table slice and the first number of transaction records stored in each business behavior table slice before the business behavior table slice is not less than the query starting row; if so, determine the business behavior table slice as the target business behavior table slice; if not, continue to determine whether the first number of transaction records stored in the next business behavior table slice and the sum of the first number of transaction records stored in each business behavior table slice before the next business behavior table slice is not less than the query starting row.

[0035] In a possible implementation, the determination module is specifically used to determine a first difference between the query start row and a first number of business behavior table shards before the target business behavior table shard; and based on the first difference, determine the target position of the first transaction record in the target business behavior table shard.

[0036] In a possible implementation, the determination module is specifically used to determine the number of transaction records displayed before the target jump page number based on the target jump page number and the number of displays per page; and determine the query starting row based on the number of transaction records displayed before the target jump page number.

[0037] In a third aspect, the present application provides an electronic device, which includes at least a processor and a memory, and the processor is used to implement the steps of any method described in the first aspect when executing a computer program stored in the memory.

[0038] In a fourth aspect, the present application provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of any method described in the first aspect.

[0039] In a fifth aspect, the present application provides a computer program product, comprising: a computer program code, when the computer program code is run on a computer, the computer executes the steps of any method described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0041] Figure 1 A schematic diagram of a transaction record query process provided in an embodiment of the present application;

[0042] Figure 2 A schematic diagram of a transaction record query process provided in an embodiment of the present application;

[0043] Figure 3 A schematic diagram of a process for determining a target query range in each target business behavior table slice provided in an embodiment of the present application;

[0044] Figure 4 A schematic diagram of a transaction record query device provided in an embodiment of the present application;

[0045] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solutions and advantages of this application clearer, this application will be further described in detail below in conjunction with the accompanying drawings. Obviously, the embodiments described in this application are only part of the embodiments of this application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0047] It should be noted that the brief description of terms in this application is only for the convenience of understanding the embodiments described below, and is not intended to limit the embodiments of this application. Unless otherwise specified, these terms should be understood according to their common and usual meanings.

[0048] The terms "first", "second", "third", etc. in the specification and claims of this application and the above drawings are used to distinguish similar or similar objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances.

[0049] The terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device comprising a list of components is not necessarily limited to all the components expressly listed but may include other components not expressly listed or inherent to such product or device.

[0050] The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functions associated with that element.

[0051] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

[0052] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description. It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0053] In the technical solution of this application, the acquisition, transmission, storage, and use of data are in compliance with the requirements of relevant national laws and regulations.

[0054] Before introducing the transaction record query method provided in the embodiment of the present application, in order to facilitate understanding, the technical background of the embodiment of the present application is first introduced.

[0055] In the related technology, according to the database design specifications and the electronic invoice business processing logic, querying the transaction records of multiple accounts bound to the same channel involves two database tables: the business behavior table and the account and channel relationship table. Among them, the business behavior table records the transaction status of various businesses with the account as the dimension, and the account and channel relationship table records the binding relationship between the customer channel number and multiple accounts.

[0056] Among them, when using conventional paging query, the user enters the front-end page display requirements on the front-end page, and the front-end page display requirements include the customer channel number, the jump page number of the query results, and the number of displays per page; after the user enters the front-end page display requirements, the query request for the transaction record is determined, and the query request carries the customer channel number, the jump page number of the query results, and the number of displays per page. According to the customer channel number carried in the query request for the transaction record, the saved account and channel relationship table, and the business behavior table, the first transaction record related to all accounts bound to the customer channel number is determined; according to the position of the first transaction record in the business behavior table, the jump page number carried in the query request, and the number of displays per page, the position of the first transaction record displayed on the jump page in the business behavior table is determined, and according to the position and the number of displays per page, each transaction record displayed on the jump page in the business behavior table is searched to obtain the query result that meets the customer's paging requirements.

[0057] However, when querying using the conventional paging method, since the query is an online query and the business behavior table records the transaction status of all accounts, that is, the total amount of accumulated business transaction records is huge, it is easy to cause the database joint table query to take too long, resulting in query timeout, which has a negative impact on customer experience.

[0058] In view of this, in order to improve the efficiency of database query and shorten the query time, the embodiments of the present application propose a transaction record query method, device, system, equipment and medium. The following describes some preferred embodiments of the present application in conjunction with the drawings of the specification.

[0059] Embodiment 1:

[0060] Figure 1 A schematic diagram of a transaction record query process provided in an embodiment of the present application, the process includes:

[0061] S101: Obtain a query request for transaction records, wherein the query request carries a customer channel number, a target jump page number, and a display quantity per page.

[0062] The transaction record query method provided in the embodiment of the present application is applied to an electronic device, which may be a computer (Personal Computer, PC), a server, etc.

[0063] Since a whole page of content is usually displayed each time a transaction record is displayed on the front-end page, the user usually enters the front-end page display requirements on the front-end page, which include the user's customer channel number, the target jump page number of the query result, and the number of displays per page. Among them, the target jump page number and the number of displays per page are positive integers that can be selected by the user.

[0064] After receiving the front-end page display requirement input by the user, the electronic device determines the query request for transaction records according to the information carried in the front-end page display requirement. The query request for transaction records carries the user's customer channel number, the target jump page number, and the number of displays per page. The target jump page number is the page number selected by the user that he or she wishes to locate on the front-end page, and the target jump page number is usually a natural number.

[0065] S102: Determine the target business behavior table shard where the first transaction record displayed on the target jump page is located and the target position in the target business behavior table shard based on the first number of transaction records stored in the business behavior table shard of each account corresponding to the customer channel number, the target jump page number, and the number of displays per page.

[0066] Since an account and channel relationship table is stored in the electronic device, and the account and channel relationship table records the binding relationship between the customer channel number and multiple accounts, after the electronic device obtains the query request, it determines the multiple accounts corresponding to the user's customer channel number based on the customer channel number carried in the query request and the account and channel relationship table stored in itself.

[0067] In an embodiment of the present application, the business behavior table is sharded based on the account number as a field to obtain a business behavior table shard corresponding to each account number. This makes it easier to match the business behavior table based on the account number without having to match all transaction records in the business behavior table. Instead, it is only necessary to match the account number corresponding to each business behavior table shard, thereby shortening the matching time.

[0068] After obtaining multiple accounts corresponding to the customer channel number, the multiple accounts corresponding to the customer channel number are matched with the accounts corresponding to each shard in the business behavior table, the business behavior table shard of each account corresponding to the customer channel number is determined, and the first number of transaction records stored in the business behavior table shard of each account is obtained. It can be understood that the transaction record stored in the business behavior table shard of each account is the transaction record of the account, and the first numbers of transaction records of different accounts can be the same or different, and are generally different.

[0069] According to the target jump page number and the number of displays per page, the number of transaction records displayed before the target jump page number is determined; according to the first number of transaction records stored in the business behavior table shard of each account and the number of transaction records displayed before the target jump page number, the target business behavior table shard where the first transaction record displayed in the target jump page corresponding to the target jump page number is located and the target position in the target business behavior table shard are determined.

[0070] The target business behavior table shard is the first business behavior table shard in the database where the target transaction record to be displayed in the target jump page of the front-end page is located. Since a database usually stores one transaction record per row, the target location is the row where the first transaction record is located in the target business behavior table shard.

[0071] S103: Determine each target transaction record to be displayed on the target jump page according to the target position and the display quantity per page.

[0072] Since the target position is the starting position of the first transaction record that the user expects to be displayed in the business behavior table, and the number of displays per page is the number of all transaction records that the user expects to be displayed on the front end, after determining the target position of the first transaction record displayed in the target jump page in the target business behavior table, the area of ​​the transaction records to be displayed in the business behavior table can be determined according to the starting position of all transaction records in the business behavior table (i.e., the target position) and the number of all transaction records displayed (i.e., the number of displays per page), and the transaction records within the area are determined as each target transaction record displayed on the target jump page. Among them, because the arrangement order of the transaction records stored in each business behavior table shard is determined, and the front-to-back order between each business behavior table shard is determined, it is possible to find each target transaction record to be displayed on the target jump page by starting from the target position in the target business behavior table shard and searching for the transaction records of the number of displays per page in the business behavior table shards in sequence.

[0073] In an embodiment of the present application, the business behavior table is sharded by the account field. When the business behavior table is queried using the account corresponding to the customer channel number as a query condition, only the data in the business behavior table shard corresponding to the account needs to be queried, thereby narrowing the query scope, improving database query efficiency, and shortening query time.

[0074] Embodiment 2:

[0075] In order to further improve the efficiency of database query, based on the above embodiment, in the embodiment of the present application, each target transaction record displayed on the target jump page is determined according to the target position and the number of displays per page, including:

[0076] Starting from the target position of the target business behavior table shard, query the transaction records displayed on each page, and determine the queried transaction records as each target transaction record displayed on the target jump page.

[0077] In an embodiment of the present application, after determining the target business behavior table slice where the first transaction record displayed in the target jump page is located and the target position in the target business behavior table slice, since the target position is the starting position of all transaction records that the user expects to be displayed in the business behavior table, and the number of displays per page is the number of all transaction records that the user expects to be displayed on the front end, in an embodiment of the present application, the target position of the target business behavior table slice is used as the starting point, and the number of displays per page is used as the query number, and the transaction records of the number of displays per page are queried, and the queried transaction records are determined as each target transaction record displayed on the target jump page.

[0078] In one possible implementation, based on the first number of transaction records stored in the target business behavior table shard and the target position of the first transaction record displayed in the target jump page in the target business behavior table shard, the difference between the first number and the number of rows at the target position is determined, and the (difference + 1) is determined as the first remaining number of transaction records in the target business behavior table shard; and a determination is made as to whether the first remaining number of transaction records is not less than the number displayed per page.

[0079] If it is determined that the first remaining transaction record quantity in the target business behavior table shard is not less than the display quantity per page, then it is determined that all transaction records corresponding to the display quantity per page can be queried in the target business behavior table shard with the target position as the starting point, and the target query number of rows in the target business behavior table shard is determined to be the display quantity per page. Therefore, in the target business behavior table shard, with the target position of the target business behavior table shard as the starting point, the transaction records of the target query number of rows are queried, and the transaction records queried in the target business behavior table shard are determined as each target transaction record displayed on the target jump page.

[0080] If it is determined that the first remaining transaction record number in the target business behavior table shard is less than the display number per page, then it is determined that the remaining transaction records in the target business behavior table shard does not meet the display number per page to be displayed on the target jump page. Therefore, it is necessary to continue to query the transaction records to be displayed on the target jump page in other target business behavior table shards arranged after the target business behavior table shard.

[0081] Therefore, in the embodiment of the present application, the target query row number in the target business behavior table shard is determined to be the first remaining transaction record number. According to the arrangement order of each first business behavior table shard, the next business behavior table shard of the target business behavior table shard is determined to be the second target business behavior table shard, and the number of transaction records stored in the second business behavior table shard is determined to be the second remaining transaction record number. And it is judged whether the second remaining transaction record number is not less than the second difference between the number of displayed per page and the first remaining transaction record number. If so, it is determined that the number of remaining transaction records in the target business behavior table shard and the number of transaction records stored in the second target business behavior table shard can meet the number of displayed per page on the target jump page, and the target query row number in the second target business behavior table shard is determined to be the first difference. In the second target business behavior table shard, the target query row number (i.e., the first difference) of the second target business behavior table shard is queried starting from the target query starting row (i.e., the first row), and the transaction records queried in the second target business behavior table shard are determined to be the number of displayed per page on the target jump page. target transaction records; if not, then determine the target query row number in the second target business behavior table shard as the second remaining transaction record number, and repeat the above steps of determining the next target business behavior table shard and the target query row number in the next target business behavior table shard, until it is determined that the sum of the target query row numbers in all target business behavior table shards is equal to the display quantity per page, and for each target business behavior table shard, in the target business behavior table shard, take the target query starting behavior of the target business behavior table shard as the starting point, query the target query row number of the target business behavior table shard, and determine the transaction records queried in the target business behavior table shard as each target transaction record displayed in the target jump.

[0082] In the embodiment of the present application, it is only necessary to query the data in the target business behavior table shard according to the target location and the number of displays per page, thereby narrowing the query scope, further improving the database query efficiency, and shortening the query time.

[0083] Embodiment 3:

[0084] In order to further improve the efficiency of database query, based on the above embodiments, in the embodiment of the present application, according to the first number of transaction records stored in the business behavior table shard of each account corresponding to the customer channel number, the target jump page number and the number of displays per page, the target business behavior table shard where the first transaction record displayed in the target jump page is located and the target position in the target business behavior table shard are determined, including:

[0085] Determine the query start row based on the target jump page number and the number of displays per page;

[0086] A target business behavior table shard and a target location are determined according to a first number of transaction records stored in each business behavior table shard and a query start row.

[0087] After determining the business behavior table shard for each account corresponding to the customer channel number, determine the query start row corresponding to the first transaction record displayed in the target jump page in the database (i.e., in the business behavior table corresponding to the customer channel number composed of the business behavior table shards of all accounts corresponding to the customer channel number in arrangement order) based on the target jump page number and the number of displays per page.

[0088] After determining the query start row corresponding to the first transaction record, for each business behavior table shard, determine that the first row of the business behavior table shard is in the first position in the business behavior table corresponding to the customer channel number, and the last row of the business behavior table shard is in the second position in the business behavior table corresponding to the customer channel number according to the arrangement order of the business behavior table shards and the first number of transaction records stored in each business behavior table shard; since each row in the business behavior table shard records a transaction record, determine whether the query start row is located in the interval corresponding to the first position to the second position, and if so, determine that the business behavior table shard is the target business behavior table shard.

[0089] After determining the target business behavior table shard, determine the target position of the first transaction record in the target business behavior table shard based on the query start row and the first position of the first row of the target business behavior table shard in the business behavior table corresponding to the customer channel.

[0090] In an embodiment of the present application, the query starting row of the first transaction record in the business behavior table corresponding to the customer channel number is determined, and the target business behavior table shard where the first transaction record is located and the target position in the target business behavior table shard are determined based on the query starting row, so as to facilitate querying the target transaction record based on the target position to narrow the query scope, further improve the database query efficiency, and shorten the query time.

[0091] Embodiment 4:

[0092] On the basis of the above embodiments, in an embodiment of the present application, according to the first number of transaction records stored in each business behavior table shard and the query start row, determining the target business behavior table shard includes:

[0093] According to the arrangement order of each business behavior table shard, the following steps are performed in sequence for each business behavior table shard until the target business behavior table shard is determined:

[0094] Determine whether the sum of the first number of transaction records stored in the business behavior table shard and the first number of transaction records stored in each business behavior table shard before the business behavior table shard is not less than the query start row;

[0095] If yes, then determine the business behavior table shard as the target business behavior table shard;

[0096] If not, continue to determine whether the sum of the first number of transaction records stored in the next business behavior table shard and the first number of transaction records stored in each business behavior table shard before the next business behavior table shard is not less than the step of querying the start row.

[0097] In order to determine the target business behavior table shard where the first transaction record displayed on the target jump page is located (i.e., the first target business behavior table shard where the target transaction record is located), in an embodiment of the present application, according to the arrangement order of each business behavior table shard, for each business behavior table shard, the sum of the first number of transaction records stored in the business behavior table shard and the first number of transaction records stored in each business behavior table shard before the business behavior table shard is determined, and it is determined whether the sum is not less than the number of rows where the query start row is located. If so, the target business behavior table shard is determined to be the target business behavior table shard, and there is no need to continue to judge the business behavior table shards after the target business behavior table shard; if not, continue to judge whether the first number of transaction records stored in the next business behavior table shard and the sum of the first number of transaction records stored in each business behavior table shard before the next business behavior table shard is not less than the number of rows where the query start row is located, until the target business behavior table shard is determined.

[0098] After the first target business behavior table shard is determined, in order to determine all target business behavior table shards, in a possible implementation, according to the arrangement order of each business behavior table shard, starting from the first target business behavior table shard, the following steps are performed in sequence for each business behavior table shard until all target business behavior table shards are determined: determine whether the sum of the first number of transaction records stored in the business behavior table shard and the first number of transaction records stored in each business behavior table shard before the business behavior table shard is less than the sum of the number of rows where the query start row is located and the number displayed per page; if so, determine that the business behavior table shard is the target business behavior table shard, and continue to determine whether the first number of transaction records stored in the next business behavior table shard and the sum of the first number of transaction records stored in each business behavior table shard before the business behavior table shard is less than the sum of the number of rows where the query start row is located and the number displayed per page; if not, determine that the business behavior table shard is not the target business behavior table shard, and there is no need to continue to judge for each business behavior table shard after the business behavior table shard.

[0099] Embodiment 5:

[0100] On the basis of the above embodiments, in an embodiment of the present application, according to the first number of transaction records stored in each business behavior table shard and the query start row, determining the target location includes:

[0101] Determine a first difference between the query start row and a first number of each business behavior table shard before the target business behavior table shard;

[0102] According to the first difference, a target position of the first transaction record in the target business behavior table shard is determined.

[0103] In an embodiment of the present application, after determining the target business behavior table shard where the first transaction record is located, the first sum of the first quantities of transaction records stored in each business behavior table shard before the target business behavior table shard is determined based on the arrangement order of each business behavior table shard and the first quantity of transaction records stored in each business behavior table shard, and based on the first sum and the query starting row, the difference between the number of rows where the query starting row is located and the first sum is determined, and the difference is determined as the first difference between the query starting row and the first quantity of each business behavior table shard before the target business behavior table shard.

[0104] According to the first difference, the (first difference+1) is determined as the row number of the target position of the first transaction record in the target business behavior table shard.

[0105] Embodiment 6:

[0106] On the basis of the above embodiments, in the embodiment of the present application, the query start row is determined according to the target jump page number and the number of displays per page, including:

[0107] According to the target jump page number and the display quantity per page, determine the number of transaction records to be displayed before the target jump page number;

[0108] Determine the query start row based on the number of transaction records displayed before the target jump page number.

[0109] In a possible implementation, based on the target jump page number and the number of displays per page, the product of (target jump page number-1) and the number of displays per page is determined, and the product value is determined as the number of transaction records displayed before the target jump page number.

[0110] According to the target transaction quantity displayed before the target jump page number, (the number of transaction records displayed before the target jump page number + 1) is determined as the row number where the query start row is located, and the query start row is determined.

[0111] In another possible implementation, according to the target jump page number and the number of displays per page, the query starting row = the number of displays per page * (target page number - 1) + 1 is used to determine the row number where the query starting row is located, and determine the query starting row.

[0112] The above embodiments are described below with a specific embodiment. Figure 2 The transaction record query process diagram includes the following steps:

[0113] Step 1: Obtain a query request for transaction records, and determine multiple accounts corresponding to the customer channel number based on the stored account and channel relationship table and the customer channel number carried in the query request.

[0114] Step 2: Determine the query starting row based on the target jump page number and the number of displays per page carried in the query request; determine all target business behavior table shards, the target position of the first transaction record displayed in the target jump page in the target business behavior table shard, and the target query row number of transaction records queried in each target business behavior table shard based on the first number of transaction records stored in the business behavior table shard of each account corresponding to the customer channel number and the query starting row.

[0115] After all target business behavior table shards are determined, the following steps are performed for each target business behavior table shard in turn according to the arrangement order of each business behavior table shard to determine the target query row number corresponding to the target business behavior table shard:

[0116] If the target business behavior table shard is the first target business behavior table shard, determine the first remaining transaction record number in the first target business behavior table shard based on the target position and the first number of transaction records saved in the first target business behavior table shard; determine whether the first remaining transaction record number is not less than the display number per page; if so, determine the target query row number of the first target business behavior table shard to be the display number per page; if not, determine the target query row number of the first target business behavior table shard to be the first remaining transaction record number.

[0117] If the target business behavior table shard is not the first target business behavior table shard, determine whether the sum of the first number of transaction records saved in the target business behavior table shard and the first number of transaction records saved in other target business behavior table shards before the target business behavior table shard is not less than the number displayed per page; if so, determine the difference between the number displayed per page and the first number of transaction records saved in other target business behavior table shards before the target business behavior table shard as the target query row number of the target business behavior table shard; if not, determine the target query row number of the target business behavior table shard to be the first number of transaction records saved in the target business behavior table shard.

[0118] Step three: determine the target query start row and target query end row of each target business behavior table shard according to the target query row number of each target business behavior table shard.

[0119] Among them, if the target business behavior table shard is the first target business behavior table shard, then determine the target query starting behavior target position corresponding to the first target business behavior table shard, and determine (the number of rows where the target position is located + the number of target query rows - 1) as the number of rows where the target query end row of the first target business behavior table shard is located.

[0120] If the target business behavior table shard is not the first target business behavior table shard, determine the first row of the target query start behavior corresponding to the first target business behavior table shard; and determine the value corresponding to the target query row number as the row number of the target query end row of the target business behavior table shard.

[0121] Step 4: Determine the target query range in the target business behavior table shard based on the target query start row and target query end row of each target business behavior table shard, and determine the target transaction records contained in the target business behavior table shard based on the target query range in the target business behavior table shard.

[0122] The target query range starts from the target query start row and ends at the target query end row.

[0123] Step 5: Summarize the target transaction records contained in each target business behavior table shard, and determine each target transaction record to be displayed on the target jump page.

[0124] The following is a specific example to illustrate the above determination of the target query range in each target business behavior table segment. Figure 3 A flow chart of determining a target query range in each target business behavior table shard includes the following steps:

[0125] Step 1: According to the target jump page number and the number of displays per page, the query start row is determined by using the query start row = the number of displays per page * (target page number - 1) + 1, and the query end row is determined by using the query end row = the query start row + the number of displays per page - 1. At the same time, the cursor row is initialized to determine that the cursor row = 0.

[0126] The business behavior table corresponding to the customer channel number is composed of business behavior table fragments of all accounts corresponding to the customer channel number in an arranged order.

[0127] Step 2: Obtain the first number of transaction records stored in the business behavior table shards of multiple accounts corresponding to the customer channel number (i.e. Figure 3 <Account number, first number of transaction records>) shown in, and subsequent steps are performed in sequence for each business behavior table shard according to the arrangement order of each business behavior table shard.

[0128] Step 3: Determine the updated cursor row according to the current cursor row and the first number of transaction records stored in the business behavior table shard. The current cursor row is the cursor row mentioned above.

[0129] Among them, CURSOR (the row where the cursor is located after the update) = CURSOR (the row where the current cursor is located) + RSLT_NUM (the first number of transaction records stored in the business behavior table shard) is used to determine the row where the cursor is located after the update.

[0130] Step 4: Determine whether the updated cursor row is less than or equal to the query start row. Figure 3 CURSOR (the row where the cursor is located after the update) ≤ START_ROW (the query start row) shown in , if so, continue to execute step 2 for the next business behavior table fragment of the business behavior table fragment; if not, execute step 5.

[0131] Furthermore, it can be understood that when it is determined that the row where the updated cursor is located is less than or equal to the query starting row, when step two is continued to be executed for the next business behavior table shard of the business behavior table shard, the row where the updated cursor is located corresponding to the business behavior table shard is determined as the row where the current cursor is located corresponding to the next business behavior table shard.

[0132] Step five, determine that the business behavior table shard is the target business behavior table shard, and determine the target query starting row in the target business behavior table shard based on the first number of transaction records saved in the target business behavior table shard, the row where the updated cursor is located, and the query starting row; determine the remaining number of transaction records in the target business behavior table shard based on the target query starting row in the target business behavior table shard and the first number of saved transaction records.

[0133] Among them, START_INDEX (target query starting row in the target business behavior table shard) = RSLT_NUM (the first number of transaction records stored in the target business behavior table shard) - [CURSOR (the row where the updated cursor is located) - START_ROW (query starting row)] is used to determine the target query starting row in the target business behavior table shard.

[0134] Use LEFT_ROWS (the remaining number of transaction records in the target business behavior table shard) = RSLT_NUM (the first number of transaction records stored in the target business behavior table shard) - START_INDEX (the target query starting row in the target business behavior table shard) + 1 to determine the remaining number of transaction records in the target business behavior table shard.

[0135] Step 6: According to the query start row and the number of remaining transaction records in the target business behavior table shard, determine the first position of the last row in the target business behavior table shard in the business behavior table corresponding to the customer channel number, and determine whether the first position is greater than the query end row, that is, Figure 3 START_ROW (query start row) + LEFT_ROWS (the number of remaining transaction records in the target business behavior table shard) - 1 ≥ END_ROW (query end row) shown in, if yes, execute step seven, if not, execute step eight.

[0136] Among them, the first position = START_ROW (query start row) + LEFT_ROWS (the number of remaining transaction records in the target business behavior table shard) - 1 is used to determine the first position of the last row in the target business behavior table shard in the business behavior table corresponding to the customer channel number.

[0137] Step 7: Determine the target query row number in the target business behavior table shard according to the query start row and the query end row, and execute step 9.

[0138] Among them, the target query row number in the target business behavior table shard is determined by using REC_NUM (the target query row number in the target business behavior table shard) = END_ROW (query end row) - START_ROW (query start row) + 1.

[0139] Step eight, determine the target query row number in the target business behavior table shard according to the number of remaining transaction records in the target business behavior table shard, and execute step nine.

[0140] Among them, the target query row number in the target business behavior table shard is determined by using REC_NUM (the target query row number in the target business behavior table shard) = LEFT_ROWS (the remaining transaction record number in the target business behavior table shard). In other words, the remaining transaction record number in the target business behavior table shard is determined as the target query row number in the target business behavior table shard.

[0141] Step 9: Determine the updated query start row based on the current query start row and the target query row number of the target business behavior table shard. And determine the account number, target query start row, and target query row number corresponding to the target business behavior table shard. The current query start row is the query start row mentioned above.

[0142] Among them, START_ROW (updated query start row) = START_ROW (current query start row) + REC_NUM (the number of target query rows in the target business behavior table shard) - 1 is used to determine the updated query start row.

[0143] Step 10: Determine whether the updated query start row is greater than or equal to the query end row. Figure 3 START_ROW (updated query start row) ≥ END_ROW (query end row) shown in, if yes, execute step eleven, if not, continue to execute step two for the next business behavior table fragment of the target business behavior table fragment.

[0144] Furthermore, it can be understood that when it is determined that the updated query start row is less than the query end row, when step two is continued to be executed for the next business behavior table shard of the target business behavior table shard, the updated query start row corresponding to the target business behavior table shard is determined as the current query start row corresponding to the next business behavior table shard.

[0145] Step 11: Summarize the account number, target query start row, and target query row number corresponding to each target business behavior table shard. Figure 3 Shown<ACCTNO,START_INDEX,REC_NUM> , where ACCTNO is the account number corresponding to the target business behavior table shard, START_INDEX is the target query start row corresponding to the target business behavior table shard, and REC_NUM is the target query row number corresponding to the target business behavior table shard.

[0146] Step 12, based on the target query starting row and the target query row number of each target business behavior table shard, determine the target query ending row in the target business behavior table shard; based on the target query starting row and the target query ending row in the target business behavior table shard, determine the target query range in the target business behavior table shard.

[0147] Embodiment 7:

[0148] Based on the same inventive concept, on the basis of the above embodiments, the present application provides a transaction record query device, see Figure 4 , Figure 4 A schematic diagram of a transaction record query device provided by some embodiments is shown, the device comprising:

[0149] The acquisition module 401 is used to acquire a query request for transaction records, wherein the query request carries a customer channel number, a target jump page number, and a display quantity per page;

[0150] A determination module 402 is used to determine a target business behavior table shard where the first transaction record displayed on the target jump page is located and a target position in the target business behavior table shard according to the first number of transaction records stored in the business behavior table shard of each account corresponding to the customer channel number, the target jump page number, and the number of displays per page;

[0151] The query module 403 is used to determine each target transaction record displayed on the target jump page according to the target location and the display quantity per page.

[0152] In a possible implementation, the query module 403 is specifically used to query the transaction records displayed per page with the target position of the target business behavior table shard as the starting point, and determine the queried transaction records as each target transaction record displayed on the target jump page.

[0153] In a possible implementation, the determination module 402 is specifically used to determine the query starting row based on the target jump page number and the display quantity per page; determine the target business behavior table shard and the target position based on the first number of transaction records stored in each business behavior table shard and the query starting row.

[0154] In one possible implementation, the determination module 402 is specifically used to execute the following steps in sequence for each business behavior table slice according to the arrangement order of each business behavior table slice until the target business behavior table slice is determined: determine whether the sum of the first number of transaction records stored in the business behavior table slice and the first number of transaction records stored in each business behavior table slice before the business behavior table slice is not less than the query starting row; if so, determine the business behavior table slice as the target business behavior table slice; if not, continue to determine whether the first number of transaction records stored in the next business behavior table slice and the sum of the first number of transaction records stored in each business behavior table slice before the next business behavior table slice is not less than the query starting row.

[0155] In a possible implementation, the determination module 402 is specifically used to determine a first difference between the query start row and a first number of business behavior table shards before the target business behavior table shard; and based on the first difference, determine the target position of the first transaction record in the target business behavior table shard.

[0156] In a possible implementation, the determination module 402 is specifically used to determine the number of transaction records displayed before the target jump page number based on the target jump page number and the number of displays per page; and determine the query starting row based on the number of transaction records displayed before the target jump page number.

[0157] Embodiment 8:

[0158] Based on the same inventive concept, on the basis of the above embodiments, the present application embodiment further provides an electronic device, which can realize the functions of the transaction record query device discussed above, please refer to Figure 5 , Figure 5 A schematic diagram of the structure of an electronic device provided in some embodiments is shown, the electronic device comprising: a processor 501, a communication interface 502, a memory 503 and a communication bus 504, wherein the processor 501, the communication interface 502, and the memory 503 communicate with each other through the communication bus 504;

[0159] The memory 503 stores a computer program. When the program is executed by the processor 501, the processor 501 performs the following steps:

[0160] A query request for obtaining transaction records, wherein the query request carries a customer channel number, a target jump page number, and a display quantity per page;

[0161] Determine the target business behavior table shard where the first transaction record displayed on the target jump page is located and the target position in the target business behavior table shard according to the first number of transaction records stored in the business behavior table shard of each account corresponding to the customer channel number, the target jump page number, and the number of displays per page;

[0162] Each target transaction record to be displayed on the target jump page is determined according to the target position and the display quantity per page.

[0163] In a possible implementation, the processor 501 is specifically used to query the transaction records with the number of transactions displayed per page starting from the target position of the target business behavior table shard, and determine the queried transaction records as each target transaction record displayed on the target jump page.

[0164] In a possible implementation, the processor 501 is specifically used to determine the query starting row based on the target jump page number and the number of displays per page; determine the target business behavior table shard and the target position based on the first number of transaction records stored in each business behavior table shard and the query starting row.

[0165] In one possible implementation, the processor 501 is specifically used to execute the following steps in sequence for each business behavior table shard according to the arrangement order of each business behavior table shard until the target business behavior table shard is determined: determine whether the sum of the first number of transaction records stored in the business behavior table shard and the first number of transaction records stored in each business behavior table shard before the business behavior table shard is not less than the query starting row; if so, determine the business behavior table shard as the target business behavior table shard; if not, continue to determine whether the first number of transaction records stored in the next business behavior table shard and the sum of the first number of transaction records stored in each business behavior table shard before the next business behavior table shard is not less than the query starting row.

[0166] In one possible implementation, the processor 501 is specifically used to determine a first difference between the query start row and a first number of business behavior table shards before the target business behavior table shard; and determine a target position of the first transaction record in the target business behavior table shard based on the first difference.

[0167] In a possible implementation, the processor 501 is specifically used to determine the number of transaction records displayed before the target jump page number based on the target jump page number and the number of displays per page; and determine the query starting row based on the number of transaction records displayed before the target jump page number.

[0168] The communication bus mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0169] The communication interface 502 is used for communication between the electronic device and other devices.

[0170] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0171] The above-mentioned processor can be a general-purpose processor, including a central processing unit, a network processor (Network Processor, NP), etc.; it can also be a digital signal processing processor (Digital Signal Processing, DSP), an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc.

[0172] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes the following steps:

[0173] A query request for obtaining transaction records, wherein the query request carries a customer channel number, a target jump page number, and a display quantity per page;

[0174] Determine the target business behavior table shard where the first transaction record displayed on the target jump page is located and the target position in the target business behavior table shard according to the first number of transaction records stored in the business behavior table shard of each account corresponding to the customer channel number, the target jump page number, and the number of displays per page;

[0175] Each target transaction record to be displayed on the target jump page is determined according to the target position and the display quantity per page.

[0176] In a possible implementation, determining each target transaction record displayed on the target jump page according to the target location and the display quantity per page includes:

[0177] Taking the target position of the target business behavior table shard as a starting point, query the transaction records of the number displayed per page, and determine the queried transaction records as each target transaction record displayed on the target jump page.

[0178] In a possible implementation, determining the target business behavior table shard where the first transaction record displayed on the target jump page is located and the target position in the target business behavior table shard according to the first number of transaction records stored in the business behavior table shard of each account corresponding to the customer channel number, the target jump page number, and the number of displays per page, includes:

[0179] Determine the query start row according to the target jump page number and the display quantity per page;

[0180] The target business behavior table shard and the target position are determined according to the first number of transaction records stored in each business behavior table shard and the query start row.

[0181] In a possible implementation, determining the target business behavior table shard according to the first number of transaction records stored in each business behavior table shard and the query start row includes:

[0182] According to the arrangement order of each business behavior table slice, the following steps are performed in sequence for each business behavior table slice until the target business behavior table slice is determined:

[0183] Determine whether the sum of the first number of transaction records stored in the business behavior table shard and the first number of transaction records stored in each business behavior table shard before the business behavior table shard is not less than the query start row;

[0184] If yes, then determining the business behavior table slice as the target business behavior table slice;

[0185] If not, continue to determine whether the sum of the first number of transaction records stored in the next business behavior table slice and the first number of transaction records stored in each business behavior table slice before the next business behavior table slice is not less than the step of querying the start row.

[0186] In a possible implementation, determining the target location according to the first number of transaction records stored in each business behavior table shard and the query start row includes:

[0187] Determine a first difference between the query start row and a first number of business behavior table shards before the target business behavior table shard;

[0188] According to the first difference, a target position of the first transaction record in the target business behavior table shard is determined.

[0189] In a possible implementation, determining the query start row according to the target jump page number and the display quantity per page includes:

[0190] Determine the number of transaction records displayed before the target jump page number according to the target jump page number and the number of displays per page;

[0191] The query start row is determined according to the number of transaction records displayed before the target jump page number.

[0192] The above-mentioned computer-readable storage medium can be any available medium or data storage device that can be accessed by the processor in the electronic device, including but not limited to magnetic storage such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc., optical storage such as CD, DVD, BD, HVD, etc., and semiconductor storage such as ROM, EPROM, EEPROM.

[0193] Based on the same inventive concept, the embodiment of the present application also provides a computer program product, which includes: computer program code, when the computer program code is run on a computer, the computer executes any transaction record query method discussed above. Since the principle of solving the problem by the above computer program product is similar to that of the transaction record query method, the implementation of the above computer program product can refer to the implementation of the method, and the repeated parts will not be repeated.

[0194] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0195] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0196] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0197] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1The steps of the functions specified in one or more boxes. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A transaction record query method, characterized in that: The method comprises: A query request for obtaining transaction records, wherein the query request carries a customer channel number, a target jump page number, and a display quantity per page; Determine the target business behavior table shard where the first transaction record displayed on the target jump page is located and the target position in the target business behavior table shard according to the first number of transaction records stored in the business behavior table shard of each account corresponding to the customer channel number, the target jump page number, and the number of displays per page; Each target transaction record to be displayed on the target jump page is determined according to the target position and the display quantity per page.

2. The method according to claim 1, characterized in that Determining each target transaction record displayed on the target jump page according to the target position and the display quantity per page includes: Taking the target position of the target business behavior table shard as a starting point, query the transaction records of the number displayed per page, and determine the queried transaction records as each target transaction record displayed on the target jump page.

3. The method according to claim 1, characterized in that The determining, according to the first number of transaction records stored in the business behavior table shard of each account corresponding to the customer channel number, the target jump page number, and the number of displays per page, a target business behavior table shard where the first transaction record displayed on the target jump page is located and a target position in the target business behavior table shard, comprises: Determine the query start row according to the target jump page number and the display quantity per page; The target business behavior table shard and the target position are determined according to the first number of transaction records stored in each business behavior table shard and the query start row.

4. The method according to claim 3, characterized in that The determining the target business behavior table shard according to the first number of transaction records stored in each business behavior table shard and the query start row includes: According to the arrangement order of each business behavior table slice, the following steps are performed in sequence for each business behavior table slice until the target business behavior table slice is determined: Determine whether the sum of the first number of transaction records stored in the business behavior table shard and the first number of transaction records stored in each business behavior table shard before the business behavior table shard is not less than the query start row; If yes, then determining the business behavior table slice as the target business behavior table slice; If not, continue to determine whether the sum of the first number of transaction records stored in the next business behavior table slice and the first number of transaction records stored in each business behavior table slice before the next business behavior table slice is not less than the step of querying the start row.

5. The method according to claim 3, characterized in that: The determining the target location according to the first number of transaction records stored in each business behavior table shard and the query start row includes: Determine a first difference between the query start row and a first number of business behavior table shards before the target business behavior table shard; According to the first difference, a target position of the first transaction record in the target business behavior table shard is determined.

6. The method according to claim 3, characterized in that The step of determining the query start row according to the target jump page number and the display quantity per page includes: Determine the number of transaction records displayed before the target jump page number according to the target jump page number and the number of displays per page; The query start row is determined according to the number of transaction records displayed before the target jump page number.

7. A transaction record query device, characterized in that: The device comprises: An acquisition module, used to acquire a query request for transaction records, wherein the query request carries a customer channel number, a target jump page number, and a display quantity per page; a determination module, configured to determine a target business behavior table slice where a first transaction record displayed on a target jump page is located and a target position in the target business behavior table slice according to a first number of transaction records stored in the business behavior table slice of each account corresponding to the customer channel number, the target jump page number, and the number of displays per page; The query module is used to determine each target transaction record displayed on the target jump page according to the target location and the display quantity per page.

8. The device according to claim 7, characterized in that The query module is specifically used to query the transaction records of the number displayed per page with the target position of the target business behavior table shard as the starting point, and determine the queried transaction records as each target transaction record displayed on the target jump page.

9. The device according to claim 7, characterized in that The determination module is specifically used to determine the query starting row according to the target jump page number and the display quantity per page; determine the target business behavior table shard and the target position according to the first number of transaction records stored in each business behavior table shard and the query starting row.

10. The device according to claim 9, characterized in that The determination module is specifically used to execute the following steps in sequence for each business behavior table slice according to the arrangement order of each business behavior table slice until the target business behavior table slice is determined: determine whether the sum of the first number of transaction records stored in the business behavior table slice and the first number of transaction records stored in each business behavior table slice before the business behavior table slice is not less than the query starting row; if so, determine the business behavior table slice as the target business behavior table slice; if not, continue to determine whether the first number of transaction records stored in the next business behavior table slice and the sum of the first number of transaction records stored in each business behavior table slice before the next business behavior table slice is not less than the query starting row.

11. The device according to claim 9, characterized in that The determination module is specifically used to determine a first difference between the query start row and a first number of business behavior table shards before the target business behavior table shard; and determine a target position of the first transaction record in the target business behavior table shard based on the first difference.

12. The device according to claim 9, characterized in that The determination module is specifically used to determine the number of transaction records displayed before the target jump page number according to the target jump page number and the number of displays per page; and determine the query starting row according to the number of transaction records displayed before the target jump page number.

13. An electronic device, characterized in that: include: A memory for storing program instructions; A processor is used to call the program instructions stored in the memory, and execute the steps included in any one of claims 1-6 according to the obtained program instructions.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes the method according to any one of claims 1 to 6.

15. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is run on a computer, the computer is enabled to execute the method according to any one of claims 1 to 6.

Images