Database-based business data storage method and device, terminal equipment and medium

Abstract

The application relates to a database-based business data storage method and device, a terminal equipment and a medium. The method generates an index classification ID by taking a business ID in business data as a prefix, generates an index ID by taking an index attribute ID under the index classification as a prefix, stores the index classification ID, the index attribute ID, the index ID and index content into a data table to form a corresponding storage table, stores the index ID and the index classification ID to which the index ID belongs into a data table to form a corresponding mapping table, connects the index classification ID and the index ID at the head and tail to generate an index tree node ID, stores the index tree node ID into a data table to form a corresponding relationship table, determines the primary key of the table according to the ID stored in each table, thereby realizing the storage of business data, and when the primary key is used for querying, the mapping table can be directly determined according to the relationship table, and the corresponding storage table is determined according to the mapping table, the time for querying is short, and the query efficiency is effectively improved.

Description

Technical Field

[0001] This application relates to the field of data storage technology, and in particular to a database-based business data storage method, apparatus, terminal equipment, and medium. Background Technology

[0002] Currently, the storage of business data with hierarchical relationships typically employs structured databases, such as SQL and MySQL. The storage process involves defining the relationships between tables in the database according to specific needs, and storing the primary keys of all parent tables in their respective table fields, arranged hierarchically to establish data association. However, each level of table field needs to be separated by commas. Querying a parent table requires sequentially matching the fields, which can drastically slow down query speeds when dealing with large datasets, resulting in low efficiency and hindering its application in big data environments. Therefore, improving the storage structure of business data to enhance query efficiency when dealing with large datasets is a pressing issue. Summary of the Invention

[0003] In view of this, embodiments of this application provide a database-based business data storage method, apparatus, terminal device, and medium to solve the problem of low query efficiency in current data storage methods under big data scenarios.

[0004] In a first aspect, embodiments of this application provide a database-based business data storage method, the business data storage method comprising:

[0005] Using the business ID in the business data to be stored as a prefix, generate the indicator category ID for each indicator category under the business data, store each indicator category ID in the corresponding indicator category node information table, and determine the primary key of the stored indicator category node information table as the corresponding indicator category ID.

[0006] Store each indicator category ID into the corresponding indicator category node information table, and determine that the primary key of the stored indicator category node information table is the corresponding indicator category ID;

[0007] Store the indicator attribute ID under each indicator category into the indicator generation rule table, determine the primary key of the stored indicator generation rule table as the corresponding indicator attribute ID, and generate the indicator ID of each indicator under the corresponding indicator attribute using the indicator attribute ID as a prefix.

[0008] Obtain the indicator content for each indicator, and store the indicator ID and indicator content for each indicator into the corresponding indicator node information table. Determine that the primary key of the stored indicator node information table is the corresponding indicator ID.

[0009] Store the indicator ID of each indicator and the indicator category ID of its respective indicator category into the corresponding indicator node mapping table. The primary key of the stored indicator node mapping table is determined to be the corresponding indicator ID and the indicator category ID.

[0010] Connect the tail of the indicator ID of each indicator to the head of the indicator category ID to generate the corresponding indicator tree node ID. Store each indicator tree node ID in the corresponding indicator tree information table and determine that the primary key of the stored indicator tree information table is the corresponding indicator tree node ID.

[0011] Secondly, embodiments of this application provide a database-based business data storage device, the business data storage device comprising:

[0012] The category node storage module is used to generate an indicator category ID for each indicator category under the business data, using the business ID in the business data to be stored as a prefix, and to store each indicator category ID in the corresponding indicator category node information table, and to determine that the primary key of the stored indicator category node information table is the corresponding indicator category ID.

[0013] The indicator ID generation module is used to store the indicator attribute ID under each indicator category into the indicator generation rule table, determine the primary key of the stored indicator generation rule table as the corresponding indicator attribute ID, and generate the indicator ID of each indicator under the corresponding indicator attribute using the indicator attribute ID as a prefix.

[0014] The indicator content storage module is used to obtain the indicator content of each indicator, and store the indicator ID and indicator content of each indicator into the corresponding indicator node information table. The primary key of the stored indicator node information table is determined to be the corresponding indicator ID.

[0015] The indicator node mapping module is used to store the indicator ID of each indicator and the indicator category ID of the indicator category to the corresponding indicator node mapping table, and to determine the primary key of the stored indicator node mapping table as the corresponding indicator ID and the indicator category ID.

[0016] The tree node storage module is used to connect the tail of the indicator ID of each indicator to the head of the indicator category ID to generate the corresponding indicator tree node ID, and store each indicator tree node ID to the corresponding indicator tree information table. The primary key of the stored indicator tree information table is the corresponding indicator tree node ID.

[0017] Thirdly, embodiments of this application provide a terminal device, the terminal device including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the business data storage method as described in the first aspect.

[0018] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the business data storage method as described in the first aspect.

[0019] The beneficial effects of this application's embodiments compared to the prior art are as follows: This application uses the business ID in the business data to be stored as a prefix to generate an indicator category ID for each indicator category. Then, using the indicator attribute ID under each indicator category as a prefix, it generates an indicator ID for each indicator under the indicator attribute. The indicator category ID, indicator attribute ID, indicator ID, and indicator content are stored in data tables to form corresponding stored tables. Then, the indicator ID of each indicator and its corresponding indicator category ID are stored in the data tables to form a corresponding mapping table. This mapping table is used to represent the hierarchical relationship between the storage table corresponding to the indicator ID and other storage tables. By concatenating the tail of the indicator ID of each indicator with the head of the corresponding indicator category ID, a corresponding indicator tree node ID is generated. Each indicator tree node ID is stored in a data table to form a corresponding relation table. This relation table is used to represent the relationships between the indicator ID and all its associated storage tables at all levels. Based on the IDs stored in each storage table, mapping table, and relation table, the primary key of the corresponding table is determined, thereby enabling the storage of business data in different tables. When querying by the primary key of a table, the mapping table can be directly determined based on the relation table, and the corresponding storage table can be determined based on the mapping table, resulting in shorter query time and effectively improving query efficiency. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a schematic diagram of an application environment for a database-based business data storage method provided in Embodiment 1 of this application;

[0022] Figure 2 This is a schematic flowchart of a database-based business data storage method provided in Embodiment 2 of this application;

[0023] Figure 3This is a schematic flowchart of a database-based business data storage method provided in Embodiment 3 of this application;

[0024] Figure 4 This is a schematic diagram of the structure of a database-based business data storage device provided in Embodiment 4 of this application;

[0025] Figure 5 This is a schematic diagram of the structure of a terminal device provided in Embodiment 5 of this application. Detailed Implementation

[0026] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0027] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0028] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0029] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0030] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0031] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0032] It should be understood that the sequence number of each step in the following embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0033] To illustrate the technical solution of this application, specific embodiments are described below.

[0034] The first embodiment of this application provides a database-based business data storage method, which can be applied to applications such as... Figure 1 In this application environment, the client and server communicate with each other. Clients include, but are not limited to, handheld computers, desktop computers, laptops, ultra-mobile personal computers (UMPCs), netbooks, cloud terminal devices, and personal digital assistants (PDAs). The server can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0035] See Figure 2 This is a flowchart illustrating a database-based business data storage method provided in Embodiment 2 of this application. The aforementioned business data storage method can be applied to... Figure 1 The server-side component connects to the database, and the corresponding terminal devices use appropriate database software to store business data in the database. These terminal devices can also connect to clients to collect business data sent by client users.

[0036] like Figure 2 As shown, this business data storage method may include the following steps:

[0037] Step S201: Using the business ID in the business data to be stored as a prefix, generate the indicator category ID for each indicator category under the business data, store each indicator category ID in the corresponding indicator category node information table, and determine that the primary key of the stored indicator category node information table is the corresponding indicator category ID.

[0038] In this process, the terminal device of the aforementioned server provides storage services to the client through a preset access address. The user sends the business data to be stored to the terminal device of the server, and after receiving the business data to be stored, the terminal device stores the data into the corresponding database through database software.

[0039] Business data refers to the data generated when a user performs a specific business task. The content of this business data varies across different application scenarios. For example, in a network platform with multiple business scenarios, such as a user management scenario, the managed objects are multiple users, and the data corresponding to those users constitutes the business data for the user management task. Metrics are specific objects within the business data. For instance, the data of a single user mentioned above is a metric. The metric type refers to the category to which the metric belongs. This type can be defined based on the actual business scenario. Within a specific business scenario, metrics of the same type are grouped together, such as numerical metrics and textual metrics.

[0040] The Business Identity Document (ID) is a unique identifier defined for each business. Each ID corresponds one-to-one with the business name, uniquely identifying the corresponding business. In the example above, "User Management" can be used as the business name for the "User Management" business, and its corresponding ID could be "U". The Indicator Category ID is a unique identifier defined for each indicator category, corresponding one-to-one with the indicator category name. Each ID uniquely identifies the type of indicator. In the example above, "Numerical" can be used as the indicator category name for the "Numerical Indicator" category, with an ID of U001. Similarly, "Textual" can be used as the indicator category name for the "Textual Indicator" category, with an ID of U002.

[0041] Extract all indicator type names from the business data, prefix them with the business ID, and then encode each indicator type name with an ID to generate different indicator type IDs. Therefore, the business ID to which an indicator type belongs can be determined from its indicator type ID. For example, if the business ID is U and the indicator category ID is U001, the first character of the indicator category ID indicates that the business ID to which it belongs is U.

[0042] After generating the indicator category ID, the indicator category ID is stored in a data table in the database. The stored data table is the indicator category node information table. The primary key of the stored data table is the indicator category ID. One indicator category ID is stored in one data table. Therefore, one indicator category ID corresponds to one indicator category node information table.

[0043] This indicator category node information table is used to maintain the mapping relationship between indicator categories and business operations. That is, through this indicator category node information table, the business ID, business name, etc., to which the indicator category ID belongs can be determined.

[0044] When storing the indicator category ID in the data table, you can also store the indicator category name corresponding to the indicator category ID in the data table.

[0045] Optionally, before generating the indicator category ID for each indicator category under the business data, using the business ID as a prefix in the business data to be stored, the following is also included:

[0046] Retrieve the business ID of the business data to be stored;

[0047] Check if there is an existing metric classification rule table with the same primary key as the business ID;

[0048] If no existing indicator classification generation table with the same primary key and business ID is detected, the business ID in the business data to be stored is stored in the data table to form an indicator classification generation rule table.

[0049] Before generating the indicator category ID for each indicator category under the business data, using the business ID in the business data to be stored as a prefix, it is also necessary to check whether a data table with the business ID as the primary key exists in the database. If it does not exist, the business ID needs to be stored in a data table in the database to form an indicator category generation rule table. If it exists, it is not necessary to store the business ID in a data table in the database.

[0050] Specifically, after acquiring the business data, it is parsed to obtain the business name. Based on the known correspondence between the business name and the business ID, the business ID is determined. The data table serves as the unit for forming the database. The business ID is stored in a data table within the database, and the primary key of the stored data table is determined to be the aforementioned business ID. Simultaneously, when storing the business ID in the data table, the corresponding business name can also be stored in the same data table.

[0051] Optionally, after checking if an existing metric classification rule table exists with the same primary key as the business ID, the following steps are also included:

[0052] If an existing indicator category generation table with the same primary key as the business ID is detected, then based on the existing indicator category generation table, the step of generating the indicator category ID for each indicator category under the business data with the business ID in the business data to be stored as a prefix is ​​executed.

[0053] If an existing indicator category generation table exists, the indicator category ID can be generated directly using the business ID as a prefix. At the same time, it needs to be distinguished from the indicator category IDs already generated in the existing indicator category generation table to avoid duplicate indicator category IDs.

[0054] Step S202: Store the indicator attribute ID under each indicator category into the indicator generation rule table, determine the primary key of the stored indicator generation rule table as the corresponding indicator attribute ID, and generate the indicator ID of each indicator under the corresponding indicator attribute using the indicator attribute ID as a prefix.

[0055] In this context, indicator attributes refer to the attribute information of the corresponding indicator. This attribute information is used to distinguish the attribute differences between each indicator. This indicator attribute is different from the indicator classification mentioned above; it is the actual attribute of the indicator under an indicator classification. For example, for user management business, the indicator classification is numerical indicators, and the indicator is the user's asset value. If the user is a member, then the corresponding indicator attribute is "member user".

[0056] The indicator attribute ID is a code defined for different indicator attributes. The indicator attribute ID corresponds one-to-one with the indicator attribute name. The corresponding indicator attribute name can be uniquely identified through the indicator attribute ID. In the example above, the business ID corresponding to user management is defined as U. If the user is a member, the corresponding indicator attribute ID can be UVIP.

[0057] After acquiring the business data, it is parsed to obtain the attribute information of the metrics. Based on the correspondence between the known attribute information and the metric attribute IDs, all metric attribute IDs under the metric category are determined and stored in a database table. This table becomes the metric generation rule table, and its primary key is the aforementioned metric attribute ID. Simultaneously, the names of all metrics corresponding to the metric attribute IDs under each metric type are extracted. Using the metric attribute ID as a prefix, all metric names are ID-encoded to generate different metric IDs corresponding to different metric names. Therefore, the metric attribute ID to which a metric belongs can be determined from its metric ID. For example, if the metric attribute ID is UVIP and the metric ID is UVIP0000, the first four characters of the metric ID indicate that it belongs to the UVIP metric attribute ID.

[0058] Step S203: Obtain the indicator content of each indicator, and store the indicator ID and indicator content of each indicator into the corresponding indicator node information table, and determine that the primary key of the stored indicator node information table is the corresponding indicator ID.

[0059] The indicator content refers to the data information corresponding to the indicator. This data information can be any information that can be stored. The indicator content is the main body of the business data, which is the part of the business data that needs to be stored.

[0060] The indicator ID and indicator content are stored in a database table. This table is the indicator node information table, and the primary key of the indicator node information table is the indicator ID. Using the primary key query function, the corresponding indicator node information table can be retrieved based on the indicator ID, and then the corresponding indicator content can be found.

[0061] When storing an indicator ID in a data table, you can also store the indicator name corresponding to that indicator ID in the data table.

[0062] Optionally, the business data storage method may also include:

[0063] Get the online / offline status of each indicator category and the online / offline status of each indicator in the business data to be stored;

[0064] Store the online / offline status of each indicator category in the corresponding indicator category node information table, and store the online / offline status of each indicator in the corresponding indicator node information table.

[0065] After storing the indicator category ID in the data table to obtain the indicator category node information table, the first node status information is also maintained in the indicator category node information table. The first node status information can refer to the online or offline status of the indicator category, which is used to indicate the online or offline status of the corresponding indicator category ID. The online status indicates that the information in the indicator category node information table can be queried, and the offline status indicates that the information in the indicator category node information table cannot be queried.

[0066] After storing the indicator ID in the data table to obtain the indicator node information table, the indicator node information table also maintains the second node status information. The second node status information can refer to the online or offline status of the indicator, which is used to indicate the online or offline status of the corresponding indicator ID. The online status means that the information in the indicator node information table can be queried, and the offline status means that the information in the indicator node information table cannot be queried.

[0067] In addition, the indicator category node information table also maintains first deletion status information. This first deletion status information can indicate whether the indicator category has been deleted, that is, whether the indicator category node information table has been deleted. If the indicator category node information table is deleted, the corresponding first deletion status information is marked as deleted, meaning that the indicator category node information table can no longer be edited or used. However, the indicator category node information table still exists in the database. If the indicator category node information table is restored, the corresponding first deletion status information is marked as not deleted, and the indicator category node information table can be directly restored, which can prevent data loss caused by accidental deletion operations. The indicator node information table also maintains a second deletion status information, which indicates whether the indicator has been deleted, or whether the indicator node information table has been deleted. If the indicator node information table is deleted, the corresponding second deletion status information is marked as deleted, meaning that the indicator node information table can no longer be edited or used. However, the indicator node information table still exists in the database. If the indicator node information table is restored, the corresponding second deletion status information is marked as not deleted, and the indicator node information table can be directly restored, which can prevent data loss caused by accidental deletion.

[0068] Step S204: Store the indicator ID of each indicator and the indicator category ID of the corresponding indicator category into the corresponding indicator node mapping table, and determine that the primary key of the stored indicator node mapping table is the corresponding indicator ID and the indicator category ID.

[0069] The mapping between the indicator ID and the indicator category ID of the corresponding indicator category can be achieved by storing both in a data table in a database. The stored data table is the indicator node mapping table, thus creating a mapping between the indicator category node information table and the indicator node information table.

[0070] To facilitate querying, the indicator ID and indicator category ID are used as the primary key of the indicator node mapping table. Specifically, the indicator ID and indicator category ID are merged to form the primary key of the indicator node mapping table. The merging method can be to concatenate the beginning and end of the indicator ID and indicator category ID. Alternatively, the end of the indicator ID can be concatenated with the beginning of the indicator category ID.

[0071] This indicator node mapping table can be attached as a node to the corresponding node of the aforementioned indicator category node information table. Multiple indicator node mapping tables can be attached to a node corresponding to an indicator category node information table, forming a node tree.

[0072] When storing the indicator ID and the indicator category ID of the corresponding indicator category in the data table, you can also store the indicator name corresponding to the indicator ID in the data table.

[0073] Additionally, when storing the indicator ID and its corresponding indicator category ID in a data table, the indicator level and the ID of the parent node of the indicator ID can also be stored in the data table. If the indicator level of the indicator ID is level one and it does not have a parent indicator, the indicator category ID is the ID of the parent node. If the indicator level of the indicator ID is level two, the indicator ID of its parent indicator (i.e., the indicator at level one) is used as the ID of the parent node.

[0074] In addition, after storing the indicator ID and its corresponding indicator category ID in the data table to obtain the indicator node mapping table, the indicator node mapping table also maintains third node status information and third deletion status information. The third node status information refers to the online or offline status of the corresponding node in the indicator node mapping table, indicating whether the corresponding node is online or offline. An online status means that the information in the indicator node mapping table can be queried, and an offline status means that the information in the indicator node mapping table cannot be queried. The third deletion status information refers to whether the corresponding node in the indicator node mapping table has been deleted, that is, whether the indicator node mapping table has been deleted. If the indicator node mapping table is deleted, the corresponding third deletion status information is marked as deleted, meaning that the indicator node mapping table can no longer be edited or used, but the indicator node mapping table still exists in the database. If the indicator node mapping table is restored, the corresponding third deletion status information is marked as not deleted, and the indicator node mapping table can be directly restored, which can prevent data loss caused by accidental deletion operations.

[0075] Optionally, after storing the indicator ID of each indicator and the indicator category ID of its respective indicator category in the corresponding indicator node mapping table, the following steps are also included:

[0076] Get the current auto-incrementing ID. After the current auto-incrementing ID is used, the ID count is incremented by one. Get the updated auto-incrementing ID and use the updated auto-incrementing ID as the current auto-incrementing ID.

[0077] Accordingly, the primary key of the stored indicator node mapping table is determined to be the corresponding indicator ID and the indicator category ID, including:

[0078] The primary key of the stored indicator node mapping table is determined to be the corresponding indicator ID, the indicator category ID to which it belongs, and the current auto-incrementing ID.

[0079] The auto-incrementing ID is set to prevent primary key conflicts. After the current auto-incrementing ID is used, its ID count is automatically incremented by one to form a new current auto-incrementing ID. When storing the indicator ID and its corresponding indicator category ID in the indicator node mapping table, the current auto-incrementing ID is also stored in the indicator node mapping table. The primary key of the indicator node mapping table is determined to be the indicator ID, indicator category ID, and current auto-incrementing ID, specifically by concatenating the indicator tree ID, indicator category ID, and current auto-incrementing ID end to end.

[0080] Step S205: Connect the tail of the indicator ID of each indicator to the head of the indicator category ID to generate the corresponding indicator tree node ID, and store each indicator tree node ID in the corresponding indicator tree information table, and determine that the primary key of the stored indicator tree information table is the corresponding indicator tree node ID.

[0081] The indicator node mapping table is attached as a node to the corresponding node of the indicator classification node information table, forming a node tree. In order to collect information on each branch of the node tree, it is necessary to integrate the information of the nodes on any branch and store the integration result in a data table in the database. The stored data table is the indicator tree information table. The indicator tree information table can be attached as a node to the corresponding node of the indicator node mapping table. The indicator tree information table records the information of the indicator tree branch where the indicator node mapping table is located.

[0082] The above integration involves connecting the tail of each indicator's indicator ID to the head of its corresponding indicator category ID to generate a corresponding indicator tree node ID. This indicator tree node ID is then stored in a data table in the database, thus obtaining the indicator tree information table. The nodes in this indicator tree information table are the indicator tree node IDs.

[0083] When storing the indicator tree node ID to the data table, you can also generate the indicator tree node name and store the indicator tree node name in the data table.

[0084] The above storage method is applied to relational databases. By recursively traversing the ID field in the indicator tree information table, various tree-like or list-like data structures required for page display can be generated. When querying a node, the result can be retrieved by the length of the leftmost prefix character (i.e., the length of the indicator ID), achieving millisecond-level search even in scenarios with large amounts of data.

[0085] Optionally, after storing each indicator tree node ID in the corresponding indicator tree information table, the following steps are also included:

[0086] Get the current auto-incrementing ID. After the current auto-incrementing ID is used, the ID count is incremented by one. Get the updated auto-incrementing ID and use the updated auto-incrementing ID as the current auto-incrementing ID.

[0087] Accordingly, the primary key of the stored indicator tree information table is determined to be the corresponding indicator tree node ID, including:

[0088] The primary key of the stored indicator tree information table is determined to be the corresponding indicator tree node ID and the current auto-incrementing ID.

[0089] The auto-incrementing ID is set to prevent primary key conflicts. After the current auto-incrementing ID is used, its ID count will be automatically incremented by one to form a new current auto-incrementing ID. When storing the indicator tree node ID to the indicator tree information table, the current auto-incrementing ID is also stored in the indicator tree information table, and the primary key of the indicator tree information table is determined to be the indicator tree node ID and the current auto-incrementing ID, specifically by concatenating the indicator tree node ID and the current auto-incrementing ID end to end.

[0090] In this embodiment, the business ID in the business data to be stored is used as a prefix to generate an indicator category ID for each indicator category. Then, the indicator attribute ID under each indicator category is used as a prefix to generate an indicator ID for each indicator under the indicator attribute. The indicator category ID, indicator attribute ID, indicator ID, and indicator content are stored in data tables to form corresponding stored tables. Then, the indicator ID of each indicator and its corresponding indicator category ID are stored in the data tables to form a corresponding mapping table. This mapping table is used to represent the hierarchical relationship between the storage table corresponding to the indicator ID and other storage tables. The tail of the indicator ID of each indicator is connected to the head of its corresponding indicator category ID to generate a corresponding indicator tree node ID. Each indicator tree node ID is stored in the data tables to form a corresponding relationship table. This relationship table is used to represent the hierarchical relationship between the indicator ID and all its corresponding storage tables. Based on the IDs stored in each storage table, mapping table, and relationship table, the primary key of the corresponding table is determined. This allows business data to be stored in different tables. When querying by the primary key of a table, the mapping table can be directly determined based on the relationship table, and the corresponding storage table can be determined based on the mapping table. The query time is short, thus effectively improving query efficiency.

[0091] See Figure 3 This is a flowchart illustrating a database-based business data storage method provided in Embodiment 3 of this application. Figure 3 As shown, this business data storage method may include the following steps:

[0092] Step S301: Using the business ID in the business data to be stored as a prefix, generate the indicator category ID for each indicator category under the business data, store each indicator category ID in the corresponding indicator category node information table, and determine that the primary key of the stored indicator category node information table is the corresponding indicator category ID.

[0093] Step S302: Store the indicator attribute ID under each indicator category into the indicator generation rule table, determine that the primary key of the stored indicator generation rule table is the corresponding indicator attribute ID, and generate the indicator ID of each indicator under the corresponding indicator attribute by using the indicator attribute ID as a prefix.

[0094] Steps S301 to S302 are the same as those steps S201 to S202 above, and can be referred to the description of steps S201 to S202, which will not be repeated here.

[0095] Step S303: Obtain the indicator level of each indicator, determine the root indicator and sub-indicators, and determine the indicator ID of the N-1 level indicator above the sub-indicator.

[0096] In this example, the root indicator has a level of one, and the sub-indicators have N levels, where N is an integer greater than 1. The second embodiment above only illustrates a scenario where there is only one level one indicator, i.e., the root indicator. Generally, a root indicator may have multiple sub-indicators at different levels. For example, the root indicator might be "Member User 1," under which there might be a level two "Member Account" indicator, and under that, a level three "Account Balance" indicator, and so on.

[0097] The root indicator is above the indicator category, and the indicator category ID can be used as the ID of the node above the root indicator. The sub-indicator is above the root indicator or the sub-indicator. If the sub-indicator is a second-level indicator, then its upper level is the root indicator, and the indicator ID of the root indicator can be used as the ID of the node above the sub-indicator. If the sub-indicator is a third-level indicator, then its upper level is the second-level indicator, and the second-level indicator is the root indicator, and the indicator ID of the second-level indicator can be used as the ID of the node above the sub-indicator.

[0098] Step S304: Obtain the indicator content of each indicator, and store the indicator ID and indicator content of each indicator into the corresponding indicator node information table, and determine that the primary key of the stored indicator node information table is the corresponding indicator ID.

[0099] Step S304 is the same as step S203 above, and can be referred to the description of step S203, so it will not be repeated here.

[0100] Step S305: For each root indicator, store the indicator ID, indicator level, and indicator category ID of the root indicator to the corresponding indicator node mapping table, and determine that the primary key of the stored indicator node mapping table is the indicator ID of the corresponding root indicator and the indicator category ID of the root indicator.

[0101] Specifically, for the processing of root indicators, the indicator category ID is stored together with the indicator ID and indicator level of the root indicator as the parent node ID of the root indicator in the indicator node mapping table, and the two are merged to form the primary key of the indicator node mapping table.

[0102] Step S306: For each sub-indicator, store the sub-indicator's indicator ID, indicator level, and the indicator ID of the parent indicator to the corresponding indicator node mapping table, and determine that the primary key of the stored indicator node mapping table is the indicator ID of the corresponding sub-indicator and the indicator ID of the parent indicator.

[0103] Specifically, for sub-indicators, the indicator ID of the sub-indicator's parent indicator is used as the parent node ID. This parent node ID, along with the sub-indicator's indicator ID and indicator level, are stored in an indicator node mapping table. The primary key of this mapping table is formed based on the sub-indicator's indicator ID and the parent node ID. Additionally, the indicator category ID to which the sub-indicator belongs is also stored in this mapping table, for later use in forming indicator tree node IDs based on the IDs in the mapping table.

[0104] Step S307: For each sub-indicator, concatenate the sub-indicator's indicator ID, the indicator ID of the N-1 level above indicator, and the indicator category ID to generate the corresponding indicator tree node ID. For each root indicator, concatenate the tail of the root indicator's indicator ID with the head of the indicator category ID to generate the corresponding indicator tree node ID.

[0105] The specific rules for generating the indicator tree node ID are as follows:

[0106] TID = IID + PN-1ID + ... + P1ID + CID

[0107] Where TID is the indicator tree node ID, IID is the indicator ID of the N-level indicator to be mounted, CID is the indicator category ID, P1ID is the indicator ID of the root indicator, PN-1ID is the indicator ID of the parent indicator of the N-level indicator, and + indicates that the first and last indicators are connected.

[0108] Step S308: Store each indicator tree node ID into the corresponding indicator tree information table, and determine that the primary key of the stored indicator tree information table is the corresponding indicator tree node ID.

[0109] Step S308 is the same as step S205 above, and can be referred to the description of step S205, so it will not be repeated here.

[0110] The resulting tables after the above storage are as follows: The indicator category generation rule table maintains two fields: `class_prefix_id` (business ID) and `class_prefix_name` (business name). When generating indicator category IDs, the business ID serves as the prefix. The indicator category node information table maintains the indicator category mapping relationship, indicator category online / offline status, and deletion status. This table contains four fields: `class_id` (indicator category ID), `class_name` (category name), `class_status` (indicator category node status), and `del_status` (deletion status). The indicator generation rule table must maintain two fields: `index_prefix_id` (indicator attribute ID) and `index_prefix_name` (indicator attribute name). When generating indicator IDs, the indicator attribute ID serves as the prefix. The indicator information table stores indicator-related indicator content and status information. This table contains four fields: `index_id` (indicator ID), `index_name` (indicator name), `index_status` (indicator status), and `del_status` (deletion status). The node mapping table maintains the node information of each indicator attached to the indicator category information table. The table contains eight fields: index_id (indicator ID), index_name (indicator name), class_id (indicator category ID), parent_id (parent node ID), index_level (indicator level), node_status (mapping table status), del_status (deletion status), and auto_id (auto-incrementing ID). The indicator tree node information table records all online indicator category nodes and indicator node information, including a unique ID field, parent and child node information fields, and deletion status. Specifically, the table contains tree_id (indicator tree node ID), tree_name (indicator tree node name), parent_id (parent node ID), auto_id (auto-incrementing ID), and del_status (deletion status). When the indicator node mapping table goes online, it is finally attached to the indicator category node information table, forming the indicator tree node information table. This means that the data in the indicator node information table corresponding to the indicator node mapping table is stored in the indicator tree node information table, allowing for queries and other operations through the fields in the indicator tree node information table.

[0111] This application embodiment achieves the establishment of a multi-level relational tree through the above-described storage process for multiple levels of indicators. Since each table has a primary key index and the primary key is constructed by setting the indicator ID at the beginning, when querying an indicator, the result can be retrieved by the number of characters in the leftmost prefix (i.e., the length of the indicator ID). Even in scenarios with large amounts of data, millisecond-level search can be achieved.

[0112] Corresponding to the business data storage method in the above embodiments, Figure 4 This paper shows a structural block diagram of a database-based business data storage device provided in Embodiment 4 of this application. The above-described business data storage method can be applied to... Figure 1 The server-side component connects to the database, and the corresponding terminal device stores the business data in the database using appropriate database software. The terminal device can also connect to the client to collect business data sent by the client user. For ease of explanation, only the parts relevant to the embodiments of this application are shown.

[0113] See Figure 4 The business data storage device includes:

[0114] The classification node storage module 41 is used to generate the indicator classification ID for each indicator category under the business data, using the business ID in the business data to be stored as a prefix, and store each indicator classification ID to the corresponding indicator classification node information table, and determine that the primary key of the stored indicator classification node information table is the corresponding indicator classification ID.

[0115] The indicator ID generation module 42 is used to store the indicator attribute ID under each indicator category into the indicator generation rule table, determine the primary key of the stored indicator generation rule table as the corresponding indicator attribute ID, and generate the indicator ID of each indicator under the corresponding indicator attribute by using the indicator attribute ID as a prefix.

[0116] The indicator content storage module 43 is used to obtain the indicator content of each indicator, store the indicator ID and indicator content of each indicator into the corresponding indicator node information table, and determine that the primary key of the stored indicator node information table is the corresponding indicator ID.

[0117] The indicator node mapping module 44 is used to store the indicator ID of each indicator and the indicator category ID of the indicator category to the corresponding indicator node mapping table, and to determine that the primary key of the stored indicator node mapping table is the corresponding indicator ID and the indicator category ID.

[0118] The tree node storage module 45 is used to connect the tail of the indicator ID of each indicator to the head of the indicator category ID to generate the corresponding indicator tree node ID, and store each indicator tree node ID to the corresponding indicator tree information table, and determine that the primary key of the stored indicator tree information table is the corresponding indicator tree node ID.

[0119] Optionally, the business data storage device also includes:

[0120] The business ID acquisition module is used to acquire the business ID of the business data to be stored before generating the indicator category ID for each indicator category under the business data, using the business ID in the business data to be stored as a prefix.

[0121] The rule table detection module is used to detect whether there is an existing rule table for generating indicator categories with the same primary key and business ID.

[0122] The rule table generation module is used to store the business ID from the business data to be stored into the data table if it is detected that there is no existing indicator classification generation table with the same primary key and business ID. This forms the indicator classification generation rule table.

[0123] Optionally, the business data storage device also includes:

[0124] The category ID generation module is used to, after checking whether there is an existing indicator category generation rule table with the same primary key as the business ID, if an existing indicator category generation table with the same primary key as the business ID is detected, execute the step of generating the indicator category ID for each indicator category under the business data with the business ID in the business data to be stored as a prefix.

[0125] Optionally, the business data storage device also includes:

[0126] The indicator level acquisition module is used to obtain the indicator level of each indicator after generating the indicator ID of each indicator under the corresponding indicator attribute with the indicator attribute ID as a prefix, and to determine the root indicator and sub-indicators. The indicator level of the root indicator is level 1, and the indicator level of the sub-indicators is level N, where N is an integer greater than 1.

[0127] The indicator ID determination module is used to determine the indicator ID of the N-1 level above the sub-indicator;

[0128] Accordingly, the aforementioned indicator node mapping module 44 includes:

[0129] The first mapping unit is used to store the indicator ID, indicator level, and indicator category ID of the indicator category to which the root indicator belongs to each root indicator into the corresponding indicator node mapping table, and to determine that the primary key of the stored indicator node mapping table is the indicator ID of the corresponding root indicator and the indicator category ID to which it belongs.

[0130] The second mapping unit is used to store the indicator ID, indicator level, and indicator ID of the parent indicator of each sub-indicator into the corresponding indicator node mapping table, and to determine that the primary key of the stored indicator node mapping table is the indicator ID of the corresponding sub-indicator and the indicator ID of the parent indicator.

[0131] Optionally, the business data storage device also includes:

[0132] The first auto-incrementing ID acquisition module is used to obtain the current auto-incrementing ID after storing the indicator ID of each indicator and the indicator category ID of the corresponding indicator category into the corresponding indicator node mapping table. After the current auto-incrementing ID is used, the ID count is incremented by one to obtain the updated auto-incrementing ID, and the updated auto-incrementing ID is used as the current auto-incrementing ID.

[0133] Accordingly, the aforementioned indicator node mapping module 44 includes:

[0134] The first primary key determination unit is used to determine that the primary key of the stored indicator node mapping table is the corresponding indicator ID, the indicator category ID to which it belongs, and the current auto-incrementing ID.

[0135] Optionally, the business data storage device also includes:

[0136] The second auto-incrementing ID acquisition module is used to obtain the current auto-incrementing ID after storing each indicator tree node ID into the corresponding indicator tree information table. After the current auto-incrementing ID is used, the ID count is incremented by one to obtain the updated auto-incrementing ID, and the updated auto-incrementing ID is used as the current auto-incrementing ID.

[0137] Accordingly, the tree node storage module 45 includes:

[0138] The second primary key determination unit is used to determine that the primary key of the stored indicator tree information table is the corresponding indicator tree node ID and the current auto-incrementing ID.

[0139] Optionally, the business data storage device also includes:

[0140] The online / offline status acquisition module is used to acquire the online / offline status of each indicator category and each indicator in the business data to be stored.

[0141] The online / offline status storage module is used to store the online / offline status of each indicator category into the corresponding indicator category node information table, and to store the online / offline status of each indicator into the corresponding indicator node information table.

[0142] It should be noted that the information interaction and execution process between the above modules are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, which will not be repeated here.

[0143] Figure 5 This is a schematic diagram of the structure of a terminal device provided in Embodiment 5 of this application. Figure 5 As shown, the terminal device of this embodiment includes: at least one processor ( Figure 5 Only one is shown in the diagram), a memory, and a computer program stored in the memory and executable on at least one processor, wherein the processor executes the computer program to implement the steps in any of the above-described business data storage method embodiments.

[0144] The terminal device may include, but is not limited to, a processor and memory. Those skilled in the art will understand that... Figure 5 This is merely an example of a terminal device and does not constitute a limitation on the terminal device. A terminal device may include more or fewer components than shown in the figure, or a combination of certain components, or different components, such as a network interface, a display screen, and an input device.

[0145] The processor referred to can be a CPU, but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0146] The memory includes readable storage media, internal memory, etc., wherein the internal memory can be the main memory of the terminal device, and the internal memory provides an environment for the operation of the operating system and computer-readable instructions stored in the readable storage media. The readable storage media can be the hard drive of the terminal device, or in some embodiments, it can be an external storage device of the terminal device, such as a plug-in hard drive, a Smart Media Card (SMC), a Secure Digital Card (SD), or a Flash Card. Furthermore, the memory can include both internal storage units and external storage devices of the terminal device. The memory is used to store the operating system, applications, bootloader, data, and other programs, such as program code for computer programs. The memory can also be used to temporarily store data that has been output or will be output.

[0147] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above device can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the above method embodiments. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. A computer-readable medium can include at least: any entity or device capable of carrying computer program code, a recording medium, a computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0148] The implementation of all or part of the processes in the methods of the above embodiments can also be accomplished by a computer program product. When the computer program product is run on a terminal device, the terminal device executes the steps in the above method embodiments.

[0149] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0150] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0151] In the embodiments provided in this application, it should be understood that the disclosed apparatus / terminal devices and methods can be implemented in other ways. For example, the apparatus / terminal device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0152] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0153] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A database-based business data storage method, characterized in that, The business data storage method includes: Using the business ID in the business data to be stored as a prefix, generate the indicator category ID for each indicator category under the business data, store each indicator category ID in the corresponding indicator category node information table, and determine the primary key of the stored indicator category node information table as the corresponding indicator category ID; Store the indicator attribute ID under each indicator category into the indicator generation rule table, determine the primary key of the stored indicator generation rule table as the corresponding indicator attribute ID, and generate the indicator ID of each indicator under the corresponding indicator attribute using the indicator attribute ID as a prefix. Obtain the indicator content for each indicator, and store the indicator ID and indicator content for each indicator into the corresponding indicator node information table. Determine that the primary key of the stored indicator node information table is the corresponding indicator ID. Store the indicator ID of each indicator and the indicator category ID of its respective indicator category into the corresponding indicator node mapping table. The primary key of the stored indicator node mapping table is determined to be the corresponding indicator ID and the indicator category ID. Connect the tail of the indicator ID of each indicator to the head of the indicator category ID to generate the corresponding indicator tree node ID. Store each indicator tree node ID in the corresponding indicator tree information table and determine the primary key of the stored indicator tree information table as the corresponding indicator tree node ID.

2. The business data storage method according to claim 1, characterized in that, Before generating the indicator category ID for each indicator category under the business data by prefixing it with the business ID in the business data to be stored, the method further includes: Retrieve the business ID of the business data to be stored; Check if there exists an existing indicator classification generation rule table in the database with the business ID as the primary key; If it is detected that there is no existing indicator classification generation table with the business ID as the primary key, then the business ID in the business data to be stored is stored in the data table to form an indicator classification generation rule table, and the business ID is determined to be the primary key of the indicator classification generation rule table.

3. The business data storage method according to claim 2, characterized in that, After detecting whether an existing indicator classification rule table with the business ID as the primary key exists in the database, the method further includes: If an existing indicator classification generation table with the business ID as the primary key is detected, then according to the existing indicator classification generation table, the step of generating an indicator classification ID for each indicator category under the business data with the business ID in the business data to be stored as a prefix is ​​executed.

4. The business data storage method according to claim 1, characterized in that, After generating the indicator ID for each indicator under the corresponding indicator attribute, using the indicator attribute ID as a prefix, the method further includes: Obtain the indicator level of each indicator, determine the root indicator and sub-indicators, wherein the indicator level of the root indicator is level one, and the indicator level of the sub-indicators is level N, where N is an integer greater than 1. Determine the index ID of the N-1 level above the sub-index; Accordingly, storing the indicator ID of each indicator and the indicator category ID of its respective indicator category in the corresponding indicator node mapping table, and determining that the primary key of the stored indicator node mapping table is the corresponding indicator ID and the indicator category ID, includes: For each root indicator, the indicator ID, indicator level, and indicator category ID of the indicator category to which the root indicator belongs are stored in the corresponding indicator node mapping table. The primary key of the stored indicator node mapping table is determined to be the indicator ID of the corresponding root indicator and the indicator category ID to which it belongs. For each sub-indicator, the sub-indicator's indicator ID, indicator level, and the indicator ID of the parent indicator are stored in the corresponding indicator node mapping table. The primary key of the stored indicator node mapping table is determined to be the indicator ID of the corresponding sub-indicator and the indicator ID of the parent indicator.

5. The business data storage method according to claim 1, characterized in that, After storing the indicator ID of each indicator and the indicator category ID of its respective indicator category in the corresponding indicator node mapping table, the method further includes: Get the current auto-incrementing ID. After the current auto-incrementing ID is used, the ID count is incremented by one to obtain the updated auto-incrementing ID, and use the updated auto-incrementing ID as the current auto-incrementing ID. Accordingly, the primary key of the stored indicator node mapping table, which consists of the corresponding indicator ID and the corresponding indicator category ID, includes: The primary key of the stored indicator node mapping table is determined to be the corresponding indicator ID, the indicator category ID to which it belongs, and the current auto-incrementing ID.

6. The business data storage method according to claim 1, characterized in that, After storing each indicator tree node ID into the corresponding indicator tree information table, the process also includes: Get the current auto-incrementing ID. After the current auto-incrementing ID is used, the ID count is incremented by one to obtain the updated auto-incrementing ID, and use the updated auto-incrementing ID as the current auto-incrementing ID. Accordingly, the primary key of the stored indicator tree information table, which is the corresponding indicator tree node ID, includes: The primary key of the stored indicator tree information table is determined to be the corresponding indicator tree node ID and the current auto-incrementing ID.

7. The business data storage method according to any one of claims 1 to 6, characterized in that, The business data storage method further includes: Obtain the online / offline status of each indicator category and the online / offline status of each indicator in the business data to be stored; Store the online / offline status of each indicator category in the corresponding indicator category node information table, and store the online / offline status of each indicator in the corresponding indicator node information table.

8. A database-based business data storage device, characterized in that, The business data storage device includes: The category node storage module is used to generate an indicator category ID for each indicator category under the business data, using the business ID in the business data to be stored as a prefix, and to store each indicator category ID to the corresponding indicator category node information table, and to determine that the primary key of the stored indicator category node information table is the corresponding indicator category ID. The indicator ID generation module is used to store the indicator attribute ID under each indicator category into the indicator generation rule table, determine the primary key of the stored indicator generation rule table as the corresponding indicator attribute ID, and generate the indicator ID of each indicator under the corresponding indicator attribute using the indicator attribute ID as a prefix. The indicator content storage module is used to obtain the indicator content of each indicator, and store the indicator ID and indicator content of each indicator into the corresponding indicator node information table. The primary key of the stored indicator node information table is the corresponding indicator ID. The indicator node mapping module is used to store the indicator ID of each indicator and the indicator category ID of the indicator category to the corresponding indicator node mapping table, and to determine the primary key of the stored indicator node mapping table as the corresponding indicator ID and the indicator category ID. The tree node storage module is used to connect the tail of the indicator ID of each indicator to the head of the indicator category ID to generate the corresponding indicator tree node ID, and store each indicator tree node ID to the corresponding indicator tree information table. The primary key of the stored indicator tree information table is the corresponding indicator tree node ID.

9. A computer device, characterized in that, The computer device includes a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the business data storage method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the business data storage method as described in any one of claims 1 to 7.

Images