CN117251468A - Query processing method, device, computer equipment and storage medium - Google Patents

Query processing method, device, computer equipment and storage medium Download PDF

Info

Publication number
CN117251468A
CN117251468A CN202311214142.3A CN202311214142A CN117251468A CN 117251468 A CN117251468 A CN 117251468A CN 202311214142 A CN202311214142 A CN 202311214142A CN 117251468 A CN117251468 A CN 117251468A
Authority
CN
China
Prior art keywords
user
target
information
application
preset
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202311214142.3A
Other languages
Chinese (zh)
Inventor
李勇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Property and Casualty Insurance Company of China Ltd
Original Assignee
Ping An Property and Casualty Insurance Company of China Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Property and Casualty Insurance Company of China Ltd filed Critical Ping An Property and Casualty Insurance Company of China Ltd
Priority to CN202311214142.3A priority Critical patent/CN117251468A/en
Publication of CN117251468A publication Critical patent/CN117251468A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/242Query formulation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22Indexing; Data structures therefor; Storage structures
    • G06F16/2282Tablespace storage structures; Management thereof
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2455Query execution
    • G06F16/24552Database cache management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44521Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08Insurance

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Data Mining & Analysis (AREA)
  • Computational Linguistics (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Mathematical Physics (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • General Business, Economics & Management (AREA)
  • Storage Device Security (AREA)

Abstract

The application belongs to the field of big data and the field of financial science and technology, and relates to a query processing method, which comprises the following steps: receiving a query request of an application center for target product application, which is triggered by a user; determining a target user type of the user based on the user information in the query request; acquiring target application permission information corresponding to user information; judging whether the target application authority accords with a preset appointed loading scene or not; if yes, calling a target interface corresponding to the target application permission based on an asynchronous loading mechanism; response processing corresponding to the query request is performed based on the target interface. The application also provides a query processing device, a computer device and a storage medium. In addition, the present application relates to blockchain technology in which user information may be stored. The method and the device can be applied to application query scenes in the financial field, the response processing corresponding to the query request is rapidly executed, the response efficiency of the query request is effectively improved, and the server pressure of target product application is reduced.

Description

Query processing method, device, computer equipment and storage medium
Technical Field
The present disclosure relates to the field of big data technologies and financial technologies, and in particular, to a query processing method, a device, a computer device, and a storage medium.
Background
For financial and technological enterprises, such as insurance enterprises, financial insurance products for business promotion are generally developed. At present, in the application scene of the financial insurance product, the application center of the home page is the most commonly used function entry of the user, bears larger concurrency pressure, and plays an extremely key role in user experience. When the application center of the home page of the financial insurance product has more functional modules and more complicated authorities, the authority query processing for querying each application entry is often realized by adopting a pre-constructed data table with application authority information of all users. The permission query processing mode easily causes that the query return of the application center is slower, the query processing efficiency of the financial insurance product is low, the server of the financial insurance product is high in pressure, and even the server may crash.
Disclosure of Invention
An object of the embodiments of the present application is to provide a query processing method, a device, a computer device, and a storage medium, so as to solve the technical problems that an application center query returns slowly, query processing efficiency of a financial insurance product is low, and pressure of a financial insurance product server is huge due to an existing permission query processing mode of a pre-constructed data table with application permission information of all users.
In order to solve the above technical problems, the embodiments of the present application provide a query processing method, which adopts the following technical schemes:
receiving a query request of an application center for target product application, which is triggered by a user; wherein, the query request carries user information of the user;
acquiring the user information from the query request, and determining a target user type of the user based on the user information;
acquiring target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type;
judging whether the target application authority accords with a preset appointed loading scene or not;
if yes, calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism;
and executing response processing corresponding to the query request based on the target interface.
Further, the step of acquiring the target application permission information corresponding to the user information based on the target processing rule corresponding to the target user type specifically includes:
judging whether the user belongs to an active user or not based on the target user type;
if the user does not belong to the active user, acquiring classification information corresponding to the user information;
Acquiring application permission information corresponding to the classification information from a preset cache;
and taking the application authority information as the target application authority information.
Further, the step of acquiring the application permission information corresponding to the classification information from a preset cache specifically includes:
judging whether first classification information matched with the classification information is stored in a preset local memory cache or not;
if the local memory cache stores first classification information matched with the classification information, acquiring application permission information corresponding to the first classification information from the local memory cache;
if the local memory cache does not store the first classification information matched with the classification information, judging whether a preset redis cache stores the second classification information matched with the classification information or not;
and if the redis cache stores the second classification information matched with the classification information, acquiring application permission information corresponding to the second classification information from the redis cache.
Further, before the step of obtaining the application permission information corresponding to the classification information from the preset cache, the method further includes:
Calling a preset data acquisition interface;
acquiring appointed application permission information of an inactive user through the data acquisition interface;
storing the appointed application authority information into the local memory cache; and
and storing the appointed application authority information into the redis cache.
Further, the step of acquiring the target application permission information corresponding to the user information based on the target processing rule corresponding to the target user type specifically includes:
judging whether the user belongs to an active user or not based on the target user type;
if the user belongs to an active user, calling preset active user data;
and acquiring target application permission information corresponding to the user information from the active user data.
Further, the step of determining the target user type of the user based on the user information specifically includes:
calling a preset active user pool;
judging whether target user information matched with the user information is stored in the active user pool;
if the active user pool stores target user information matched with the user information, judging that the user belongs to the active user, and generating a target user type with the content being the active user;
And if the active user pool does not store the target user information matched with the user information, judging that the user belongs to the inactive user, and generating a target user type with the content of the inactive user.
Further, before the step of calling the preset active user pool, the method further comprises:
acquiring user access data and log records in a preset time period;
analyzing and processing the user access data and the log records, and determining appointed users belonging to active users from all the initial users;
acquiring appointed user information of the appointed user;
and storing the specified user information into the active user pool.
In order to solve the above technical problems, the embodiments of the present application further provide a query processing apparatus, which adopts the following technical schemes:
the receiving module is used for receiving a query request of an application center for target product application, which is triggered by a user; wherein, the query request carries user information of the user;
the determining module is used for acquiring the user information from the query request and determining the target user type of the user based on the user information;
The acquisition module is used for acquiring target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type;
the judging module is used for judging whether the target application permission accords with a preset appointed loading scene or not;
the calling module is used for calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism if the target application permission is met;
and the processing module is used for executing response processing corresponding to the query request based on the target interface.
In order to solve the above technical problems, the embodiments of the present application further provide a computer device, which adopts the following technical schemes:
receiving a query request of an application center for target product application, which is triggered by a user; wherein, the query request carries user information of the user;
acquiring the user information from the query request, and determining a target user type of the user based on the user information;
acquiring target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type;
judging whether the target application authority accords with a preset appointed loading scene or not;
If yes, calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism;
and executing response processing corresponding to the query request based on the target interface.
In order to solve the above technical problems, embodiments of the present application further provide a computer readable storage medium, which adopts the following technical solutions:
receiving a query request of an application center for target product application, which is triggered by a user; wherein, the query request carries user information of the user;
acquiring the user information from the query request, and determining a target user type of the user based on the user information;
acquiring target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type;
judging whether the target application authority accords with a preset appointed loading scene or not;
if yes, calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism;
and executing response processing corresponding to the query request based on the target interface.
Compared with the prior art, the embodiment of the application has the following main beneficial effects:
In the embodiment of the application, when a query request of an application center for target product application triggered by a user is received, firstly, the user information is obtained from the query request, and the target user type of the user is determined based on the user information; then, based on a target processing rule corresponding to the target user type, acquiring target application permission information corresponding to the user information; subsequently judging whether the target application authority accords with a preset appointed loading scene or not; if yes, calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism; and finally, executing response processing corresponding to the query request based on the target interface. After receiving a query request of an application center for target product application triggered by a user, the embodiment of the invention determines the target user type of the user based on the user information carried in the query request, and judges the target user type of the user by using the target user type, and further, the embodiment of the invention can intelligently realize rapid acquisition of target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type, thereby being beneficial to calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism according to the acquired target application permission information, realizing rapid execution of response processing corresponding to the query request, effectively improving the response efficiency of the interface, improving the response efficiency of the query request, reducing the server pressure of the target product application, and being beneficial to improving the use experience of the user.
Drawings
For a clearer description of the solution in the present application, a brief description will be given below of the drawings that are needed in the description of the embodiments of the present application, it being obvious that the drawings in the following description are some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art.
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow chart of one embodiment of a query processing method according to the present application;
FIG. 3 is a schematic diagram of one embodiment of a query processing device according to the present application;
FIG. 4 is a schematic structural diagram of one embodiment of a computer device according to the present application.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the applications herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having" and any variations thereof in the description and claims of the present application and in the description of the figures above are intended to cover non-exclusive inclusions. The terms first, second and the like in the description and in the claims or in the above-described figures, are used for distinguishing between different objects and not necessarily for describing a sequential or chronological order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
In order to better understand the technical solutions of the present application, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings.
As shown in fig. 1, a system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications, such as a web browser application, a shopping class application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc., may be installed on the terminal devices 101, 102, 103.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablet computers, electronic book readers, MP3 players (Moving Picture Experts Group Audio Layer III, dynamic video expert compression standard audio plane 3), MP4 (Moving Picture Experts Group Audio Layer IV, dynamic video expert compression standard audio plane 4) players, laptop and desktop computers, and the like.
The server 105 may be a server providing various services, such as a background server providing support for pages displayed on the terminal devices 101, 102, 103.
It should be noted that, the query processing method provided in the embodiments of the present application is generally executed by a server/terminal device, and accordingly, the query processing apparatus is generally disposed in the server/terminal device.
The embodiment of the application can acquire and process the related data based on the artificial intelligence technology. Among these, artificial intelligence (Artificial Intelligence, AI) is the theory, method, technique and application system that uses a digital computer or a digital computer-controlled machine to simulate, extend and extend human intelligence, sense the environment, acquire knowledge and use knowledge to obtain optimal results.
Artificial intelligence infrastructure technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a robot technology, a biological recognition technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and other directions.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
With continued reference to FIG. 2, a flow chart of one embodiment of a query processing method according to the present application is shown. The order of the steps in the flowchart may be changed and some steps may be omitted according to various needs. The query processing method provided by the embodiment of the application can be applied to any scene requiring permission information query for product application, and can be applied to products in the scenes, for example, permission information query for insurance product application in the field of financial insurance. The query processing method comprises the following steps:
Step S201, receiving a query request of an application center for target product application, which is triggered by a user; wherein the query request carries user information of the user.
In this embodiment, the electronic device (for example, the server/terminal device shown in fig. 1) on which the query processing method operates may acquire the query request carrying the user information through a wired connection manner or a wireless connection manner. It should be noted that the wireless connection may include, but is not limited to, 3G/4G/5G connection, wiFi connection, bluetooth connection, wiMAX connection, zigbee connection, UWB (ultra wideband) connection, and other now known or later developed wireless connection. In the business scenario of financial insurance, the target product application may specifically be a financial insurance application product, for example, may include any one of a car insurance application product, a life insurance application product, a medical insurance application product, and the like. The application center is the application center in the home page of the target product application, is the most commonly used function entry of the user, bears larger concurrency pressure, and plays an extremely key role in user experience. The query request is triggered when the user accesses an application center of the home page of the target product application. In addition, the user information may include identity information of the user, such as name information.
Step S202, obtaining the user information from the query request, and determining the target user type of the user based on the user information.
In this embodiment, the user information may be extracted from the query request by performing parsing processing on the query request. The above implementation process of determining the target user type of the user based on the user information will be described in further detail in the following embodiments, which will not be described herein.
Step S203, obtaining target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type.
In this embodiment, the target user types include active users or inactive users, and processing rules for acquiring application permission information of the user, which correspond to different user types, are preset for different user types. The specific implementation process of obtaining the target application permission information corresponding to the user information based on the target processing rule corresponding to the target user type is described in further detail in the following specific embodiments, which are not described herein.
Step S204, judging whether the target application authority accords with a preset appointed loading scene.
In this embodiment, the specific loading scenario is a scenario in which the third party interface needs to be called to determine the application display permission and jump-to-parameter.
Step S205, if yes, calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism.
In this embodiment, the asynchronous loading mechanism refers to a mechanism for integrating Future asynchronous call, and specifically, the thread pool may be introduced to implement simultaneous call of each third party interface, that is, the target interface, in a manner of using a concurrent call interface, so that the interface query efficiency may be greatly improved. Future asynchronization is one of the commonly used asynchronous programming methods in Java that is capable of returning a Future object representing Future results during code execution, so that the program can continue to perform other operations while waiting for the results. The Future object represents a result of an asynchronous operation, and when an asynchronous task is executed, the execution state and result of the task can be obtained through the Future object. In Java, the Future object is usually returned by an asynchronous task submitted by the Executor framework, and a Future () method may be used to obtain the execution result of the asynchronous task. If the asynchronous task is not yet completed, then invoking the future. Get () method will block the thread until the asynchronous task is completed and the result is returned.
Step S206, executing a response process corresponding to the query request based on the target interface.
In this embodiment, after the target interface corresponding to the target application authority is invoked based on the asynchronous loading mechanism, the response processing of the query request of the application center of the target product application triggered by the user can be executed by using the target interface, so that the response return of the query request can be quickly and accurately completed.
When a query request of an application center for target product application triggered by a user is received, firstly, acquiring the user information from the query request, and determining the target user type of the user based on the user information; then, based on a target processing rule corresponding to the target user type, acquiring target application permission information corresponding to the user information; subsequently judging whether the target application authority accords with a preset appointed loading scene or not; if yes, calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism; and finally, executing response processing corresponding to the query request based on the target interface. After receiving a query request of an application center for target product application, which is triggered by a user, the method determines the target user type of the user based on user information carried in the query request, and judges the target user type of the user by using the target user type, and further, the method intelligently and rapidly obtains target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type, thereby being beneficial to calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism according to the obtained target application permission information, realizing rapid execution of response processing corresponding to the query request, effectively improving the response efficiency of the interface, improving the response efficiency of the query request, reducing the server pressure of the target product application, and being beneficial to improving the use experience of the user.
In some alternative implementations, step S203 includes the steps of:
and judging whether the user belongs to an active user or not based on the target user type.
In this embodiment, the content of the target user type includes active users or inactive users. If the content of the target user type is an active user, the user is determined to belong to the active user, and if the content of the target user type is an inactive user, the user is determined to belong to the inactive user.
And if the user does not belong to the active user, acquiring classification information corresponding to the user information.
In this embodiment, the above classification information may refer to information for classifying tags, institutions, people, and the like.
And acquiring application permission information corresponding to the classification information from a preset cache.
In this embodiment, the above specific implementation process of obtaining the application permission information corresponding to the classification information from the preset cache is described in further detail in the following specific embodiments, which are not described herein.
And taking the application authority information as the target application authority information.
Judging whether the user belongs to an active user or not based on the target user type; if the user does not belong to the active user, acquiring classification information corresponding to the user information; then acquiring application permission information corresponding to the classification information from a preset cache; and taking the application authority information as the target application authority information. According to the method and the device, when the user belongs to the inactive user through the use of the target user type, the classification information corresponding to the user information is intelligently acquired, and then the application permission information corresponding to the classification information is rapidly acquired based on the use of the cache and used as the target application permission information, so that a target interface corresponding to the target application permission is conveniently and rapidly invoked according to the target application permission information of the user rapidly acquired from the cache, response processing corresponding to the query request is rapidly executed, the response efficiency of the interface response is effectively improved, the response efficiency of the query request is improved, and the use experience of the user is facilitated.
In some optional implementations of this embodiment, the obtaining, from a preset cache, application permission information corresponding to the classification information includes the following steps:
judging whether first classification information matched with the classification information is stored in a preset local memory cache or not.
In this embodiment, the local memory cache may also be referred to as a ThreadLocal memory. The local memory cache may be queried by using the classification information to detect whether the local memory cache stores first classification information matching the classification information. Wherein, the local memory cache is pre-cached with the classification information of the inactive user and the application permission information corresponding to the classification information of the inactive user. The application permission information may refer to the visible permission of the user for each application of the application center, and the visible application permissions corresponding to different users may be different. In addition, the cache data in the local memory cache is subjected to regular cleaning.
And if the local memory cache stores the first classification information matched with the classification information, acquiring application permission information corresponding to the first classification information from the local memory cache.
In this embodiment, the application permission information is application permission information stored in a local memory cache and having a data correspondence with the first classification information. For example, the classification information, such as a tag, a mechanism or a crowd code, may be found according to the identity information of the user, and then the corresponding application permission information is obtained from the local memory cache according to the classification information.
If the first classification information matched with the classification information is not stored in the local memory cache, judging whether the second classification information matched with the classification information is stored in a preset redis cache or not.
In this embodiment, the redis cache is a cache database built in advance in the electronic device. The redis cache may be queried for data by using the classification information to detect whether second classification information matching the classification information is stored in the redis cache. Wherein, the redis cache is pre-cached with the classification information of the inactive user and the application permission information corresponding to the classification information of the inactive user. The application rights information may refer to the user's visible rights to the respective application of the application center. In addition, the cache data in the redis cache is subjected to regular cleaning.
And if the redis cache stores the second classification information matched with the classification information, acquiring application permission information corresponding to the second classification information from the redis cache.
In this embodiment, the application permission information is application permission information stored in the redis cache and having a data correspondence relationship with the second classification information. In addition, if the second classification information matched with the classification information is not stored in the redis cache, a preset user application authority initialization interface is called to trigger a personal authority initialization process to acquire the application authority information of the user, and the acquired application authority information of the user is maintained in the local memory cache and the redis cache after the completion.
Judging whether first classification information matched with the classification information is stored in a preset local memory cache or not; if the local memory cache stores first classification information matched with the classification information, acquiring application permission information corresponding to the first classification information from the local memory cache; if the local memory cache does not store the first classification information matched with the classification information, judging whether a preset redis cache stores the second classification information matched with the classification information or not; and if the redis cache stores the second classification information matched with the classification information, acquiring application permission information corresponding to the second classification information from the redis cache. According to the method and the device, when the user belongs to the inactive user through the use of the target user type, the classification information corresponding to the user information is intelligently acquired, the application permission information corresponding to the classification information is rapidly acquired based on the use of the local memory cache and the redis cache and is used as the target application permission information, the target interface corresponding to the target application permission is conveniently and rapidly invoked according to the target application permission information of the user rapidly acquired from the cache, so that response processing corresponding to the query request is rapidly executed, the efficiency of interface response is effectively improved, the response efficiency of the query request is improved, and the use experience of the user is facilitated to be improved.
In some optional implementations, before the step of acquiring the application permission information corresponding to the classification information from the preset cache, the electronic device may further execute the following steps:
and calling a preset data acquisition interface.
In this embodiment, the data acquisition interface is a pre-built user application authority initialization interface, and the data acquisition interface is used for starting a task of generating interface data in batches, where the task is a task of querying all application authority information visible in an application center of a target product application by a user from preset user authority data. The application permission information is acquired in advance and comprises application permission of an active user and application permission of a non-active user. In addition, the users are classified into active users and inactive users in advance according to user access data and log records of the users.
And acquiring the appointed application permission information of the inactive user through the data acquisition interface.
In this embodiment, after the application permission information that is all visible in the application center of the target product application by the user is obtained through the data obtaining interface, the application permission information of the inactive user may be further screened out from the application permission information.
And storing the appointed application authority information into the local memory cache.
In this embodiment, a first storage area for storing application permission information may be constructed in a local memory cache, and the specified application permission information may be stored in the first storage area in the local memory cache.
And storing the appointed application authority information into the redis cache.
In this embodiment, a second storage area for storing application rights information may be constructed in the redis cache, and the specified application rights information may be stored in the second storage area in the redis cache. In addition, when the user is detected to have the update of the application permission information, the application permission information stored in the local memory cache and the redis cache is synchronously updated, so that the accuracy of the application permission information stored in the local memory cache and the redis cache is ensured.
The method comprises the steps of calling a preset data acquisition interface; then acquiring appointed application authority information of the inactive user through the data acquisition interface; subsequently, the appointed application authority information is stored in the local memory cache; and storing the appointed application authority information into the redis cache. According to the method and the device, the appointed application permission information of the inactive user is acquired by intelligently calling the preset data acquisition interface in advance, and then the appointed application permission information is stored in the local memory cache and the redis cache, so that the target application permission information of the user which is rapidly acquired from the local memory cache or the redis cache can be achieved later, the subsequent response processing corresponding to the query request can be rapidly executed by calling the target interface corresponding to the target application permission, the response efficiency of the interface response is effectively improved, the response efficiency of the query request is improved, and the use experience of the user is improved.
In some alternative implementations, step S203 includes the steps of:
and judging whether the user belongs to an active user or not based on the target user type.
In this embodiment, the content of the target user type includes active users or inactive users. If the content of the target user type is an active user, the user is determined to belong to the active user, and if the content of the target user type is an inactive user, the user is determined to belong to the inactive user.
And if the user belongs to the active user, calling preset active user data.
In this embodiment, the active user data is active user data generated in advance according to a warm-up scheme set for a warm-up mechanism of an active user. Specifically, at a preset time point of each day, a task schedule is started, and the active user group is analyzed through user access data and log records and recorded into an active user pool. The value of the preset time period is not particularly limited, and may be set according to actual use requirements, for example, may be set to 1 am. Further, for the batch of active users, a task of generating interface data in batches is restarted, visible application rights, three-party dependencies and the like of each active user are sequentially traversed through running batches, all visible application rights (namely application rights information) are queried in advance for each active user, and data are stored, so that corresponding active user data are generated. The user information of the active user may be used as an identifier of the corresponding application authority information in the active user data for storage.
And acquiring target application permission information corresponding to the user information from the active user data.
In this embodiment, the user information may be used to query active user data, so as to query specific user information matching with the user information from the active user data, and further obtain application permission information corresponding to the specific user information from the active user data, so as to obtain the target application permission information.
Judging whether the user belongs to an active user or not based on the target user type; if the user belongs to an active user, calling preset active user data; and subsequently, acquiring target application permission information corresponding to the user information from the active user data. According to the method and the device, when the user belongs to the active user through the use of the target user type, the active user data can be intelligently called, and then the target application permission information corresponding to the user information is rapidly acquired based on the use of the active user data, so that the subsequent rapid execution of response processing corresponding to the query request is realized through calling the target interface corresponding to the target application permission, the efficiency of interface response is effectively improved, the response efficiency of the query request is improved, and the use experience of the user is improved.
In some alternative implementations of the present embodiment, step S202 includes the steps of:
and calling a preset active user pool.
In this embodiment, a task schedule is started in a preset time period of each day, so as to obtain an active user group by analyzing user access data and log records, and user information corresponding to the active user group is recorded in a preset data pool, so that the active user pool is obtained.
And judging whether target user information matched with the user information is stored in the active user pool.
In this embodiment, the user information and the information stored in the active user pool may be matched to determine whether the target user information matched with the user information is stored in the active user pool.
And if the active user pool stores target user information matched with the user information, judging that the user belongs to the active user, and generating a target user type with the content being the active user.
And if the active user pool does not store the target user information matched with the user information, judging that the user belongs to the inactive user, and generating a target user type with the content of the inactive user.
The method comprises the steps of calling a preset active user pool; then judging whether target user information matched with the user information is stored in the active user pool; if the active user pool stores target user information matched with the user information, judging that the user belongs to the active user, and generating a target user type with the content being the active user; and if the active user pool does not store the target user information matched with the user information, judging that the user belongs to the inactive user, and generating a target user type with the content of the inactive user. According to the method and the device, the information is matched with the user information by using the active user pool, so that the target user type of the target user can be rapidly and accurately identified according to the generated matching result, the generation efficiency of the target user type is improved, and the accuracy of the generated target user type is ensured.
In some optional implementations of this embodiment, before the step of calling the preset active user pool, the electronic device may further perform the following steps:
and acquiring user access data and log records within a preset time period.
In this embodiment, the value of the preset time period is not specifically limited, and may be set according to actual use requirements, for example, may be set to 1 am.
And analyzing and processing the user access data and the log records, and determining the appointed user belonging to the active user from all the initial users.
In this embodiment, the user accessing data and the log record may be analyzed to screen out a user whose access frequency to the target product application is greater than a preset frequency threshold and whose total access time to the target product application is greater than a preset duration threshold, where the user is a designated user belonging to an active user. The values of the frequency threshold and the duration threshold are not particularly limited, and can be set according to actual use requirements.
And acquiring the appointed user information of the appointed user.
In this embodiment, the specified user information may refer to identity information of the specified user, and may include name information, for example.
And storing the specified user information into the active user pool.
In this embodiment, when some historical active users in the active user pool are counted to become inactive users, the user information of the historical active users is removed from the active user pool, so as to ensure the accuracy of the stored data in the active user pool.
The method comprises the steps of obtaining user access data and log records in a preset time period; then analyzing and processing the user access data and the log records, and determining appointed users belonging to active users from all the initial users; then acquiring the appointed user information of the appointed user; and storing the appointed user information into the active user pool. According to the method and the device, the user access data and the log records are analyzed, the appointed users belonging to the active users are determined from all the initial users, and then the obtained appointed user information of the appointed users is stored into the active user pool, so that the construction of the active user pool is completed quickly, the purpose of quickly and accurately distinguishing the target user types of the users by using the active user pool is facilitated, and the generation accuracy of the target user types of the users is ensured.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present invention.
It should be emphasized that, to further ensure the privacy and security of the user information, the user information may also be stored in a node of a blockchain.
The blockchain referred to in the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm and the like. The Blockchain (Blockchain), which is essentially a decentralised database, is a string of data blocks that are generated by cryptographic means in association, each data block containing a batch of information of network transactions for verifying the validity of the information (anti-counterfeiting) and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, an application services layer, and the like.
The embodiment of the application can acquire and process the related data based on the artificial intelligence technology. Among these, artificial intelligence (Artificial Intelligence, AI) is the theory, method, technique and application system that uses a digital computer or a digital computer-controlled machine to simulate, extend and extend human intelligence, sense the environment, acquire knowledge and use knowledge to obtain optimal results.
Artificial intelligence infrastructure technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a robot technology, a biological recognition technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and other directions.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by computer readable instructions stored in a computer readable storage medium that, when executed, may comprise the steps of the embodiments of the methods described above. The storage medium may be a nonvolatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a random access Memory (Random Access Memory, RAM).
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited in order and may be performed in other orders, unless explicitly stated herein. Moreover, at least some of the steps in the flowcharts of the figures may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order of their execution not necessarily being sequential, but may be performed in turn or alternately with other steps or at least a portion of the other steps or stages.
With further reference to fig. 3, as an implementation of the method shown in fig. 2, the present application provides an embodiment of a query processing apparatus, where an embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 3, the query processing apparatus 300 according to the present embodiment includes: a receiving module 301, a determining module 302, an obtaining module 303, a judging module 304, a calling module 305 and a processing module 306. Wherein:
a receiving module 301, configured to receive a query request, triggered by a user, for an application center of a target product application; wherein, the query request carries user information of the user;
a determining module 302, configured to obtain the user information from the query request, and determine a target user type of the user based on the user information;
an obtaining module 303, configured to obtain target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type;
the judging module 304 is configured to judge whether the target application permission accords with a preset designated loading scenario;
a calling module 305, configured to, if yes, call a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism;
And a processing module 306, configured to execute response processing corresponding to the query request based on the target interface.
In this embodiment, the operations performed by the modules or units respectively correspond to the steps of the query processing method in the foregoing embodiment one by one, which is not described herein again.
In some alternative implementations of the present embodiment, the obtaining module 303 includes:
the first judging submodule is used for judging whether the user belongs to an active user or not based on the target user type;
the first acquisition sub-module is used for acquiring classification information corresponding to the user information if the user does not belong to the active user;
the second acquisition sub-module is used for acquiring application permission information corresponding to the classification information from a preset cache;
and determining a submodule, wherein the application authority information is used as the target application authority information.
In this embodiment, the operations performed by the modules or units respectively correspond to the steps of the query processing method in the foregoing embodiment one by one, which is not described herein again.
In some optional implementations of this embodiment, the second acquisition submodule includes:
the first judging unit is used for judging whether first classification information matched with the classification information is stored in a preset local memory cache or not;
The first acquisition unit is used for acquiring application permission information corresponding to the first classification information from the local memory cache if the first classification information matched with the classification information is stored in the local memory cache;
the second judging unit is used for judging whether second classification information matched with the classification information is stored in a preset redis cache or not if the first classification information matched with the classification information is not stored in the local memory cache;
and the second acquisition unit is used for acquiring the application permission information corresponding to the second classification information from the redis cache if the redis cache stores the second classification information matched with the classification information.
In this embodiment, the operations performed by the modules or units respectively correspond to the steps of the query processing method in the foregoing embodiment one by one, which is not described herein again.
In some optional implementations of this embodiment, the obtaining module 303 further includes:
the first calling sub-module is used for calling a preset data acquisition interface;
the third acquisition sub-module is used for acquiring the appointed application permission information of the inactive user through the data acquisition interface;
The first storage submodule is used for storing the appointed application authority information into the local memory cache; and
and the second storage sub-module is used for storing the appointed application permission information into the redis cache.
In this embodiment, the operations performed by the modules or units respectively correspond to the steps of the query processing method in the foregoing embodiment one by one, which is not described herein again.
In some alternative implementations of the present embodiment, the obtaining module 303 includes:
the second judging sub-module is used for judging whether the user belongs to an active user or not based on the target user type;
the second calling sub-module is used for calling preset active user data if the user belongs to an active user;
and the fourth acquisition sub-module is used for acquiring target application permission information corresponding to the user information from the active user data.
In this embodiment, the operations performed by the modules or units respectively correspond to the steps of the query processing method in the foregoing embodiment one by one, which is not described herein again.
In some alternative implementations of the present embodiment, the determining module 302 includes:
the third calling sub-module is used for calling a preset active user pool;
A third judging sub-module, configured to judge whether target user information matched with the user information is stored in the active user pool;
the first generation sub-module is used for judging that the user belongs to the active user if the target user information matched with the user information is stored in the active user pool, and generating a target user type with the content being the active user;
and the second generation sub-module is used for judging that the user belongs to the non-active user if the target user information matched with the user information is not stored in the active user pool, and generating a target user type with the content of the non-active user.
In this embodiment, the operations performed by the modules or units respectively correspond to the steps of the query processing method in the foregoing embodiment one by one, which is not described herein again.
In some optional implementations of this embodiment, the determining module 302 further includes:
a fifth obtaining sub-module, configured to obtain user access data and log records in a preset time period;
the analysis sub-module is used for analyzing and processing the user access data and the log records, and determining appointed users belonging to active users from all the initial users;
A sixth obtaining sub-module, configured to obtain specified user information of the specified user;
and the third storage sub-module is used for storing the appointed user information into the active user pool.
In this embodiment, the operations performed by the modules or units respectively correspond to the steps of the query processing method in the foregoing embodiment one by one, which is not described herein again.
In order to solve the technical problems, the embodiment of the application also provides computer equipment. Referring specifically to fig. 4, fig. 4 is a basic structural block diagram of a computer device according to the present embodiment.
The computer device 4 comprises a memory 41, a processor 42, a network interface 43 communicatively connected to each other via a system bus. It should be noted that only computer device 4 having components 41-43 is shown in the figures, but it should be understood that not all of the illustrated components are required to be implemented and that more or fewer components may be implemented instead. It will be appreciated by those skilled in the art that the computer device herein is a device capable of automatically performing numerical calculations and/or information processing in accordance with predetermined or stored instructions, the hardware of which includes, but is not limited to, microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASICs), programmable gate arrays (fields-Programmable Gate Array, FPGAs), digital processors (Digital Signal Processor, DSPs), embedded devices, etc.
The computer equipment can be a desktop computer, a notebook computer, a palm computer, a cloud server and other computing equipment. The computer equipment can perform man-machine interaction with a user through a keyboard, a mouse, a remote controller, a touch pad or voice control equipment and the like.
The memory 41 includes at least one type of readable storage medium including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), random Access Memory (RAM), static Random Access Memory (SRAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), programmable Read Only Memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the storage 41 may be an internal storage unit of the computer device 4, such as a hard disk or a memory of the computer device 4. In other embodiments, the memory 41 may also be an external storage device of the computer device 4, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card) or the like, which are provided on the computer device 4. Of course, the memory 41 may also comprise both an internal memory unit of the computer device 4 and an external memory device. In this embodiment, the memory 41 is typically used to store an operating system and various application software installed on the computer device 4, such as computer readable instructions of a query processing method. Further, the memory 41 may be used to temporarily store various types of data that have been output or are to be output.
The processor 42 may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 42 is typically used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is configured to execute computer readable instructions stored in the memory 41 or process data, such as computer readable instructions for executing the query processing method.
The network interface 43 may comprise a wireless network interface or a wired network interface, which network interface 43 is typically used for establishing a communication connection between the computer device 4 and other electronic devices.
Compared with the prior art, the embodiment of the application has the following main beneficial effects:
in the embodiment of the application, when a query request of an application center for target product application triggered by a user is received, firstly, acquiring the user information from the query request, and determining a target user type of the user based on the user information; then, based on a target processing rule corresponding to the target user type, acquiring target application permission information corresponding to the user information; subsequently judging whether the target application authority accords with a preset appointed loading scene or not; if yes, calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism; and finally, executing response processing corresponding to the query request based on the target interface. After receiving a query request of an application center for target product application triggered by a user, the embodiment of the invention determines the target user type of the user based on the user information carried in the query request, and judges the target user type of the user by using the target user type, and further, the embodiment of the invention can intelligently realize rapid acquisition of target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type, thereby being beneficial to calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism according to the acquired target application permission information, realizing rapid execution of response processing corresponding to the query request, effectively improving the response efficiency of the interface, improving the response efficiency of the query request, reducing the server pressure of the target product application, and being beneficial to improving the use experience of the user.
The present application also provides another embodiment, namely, a computer-readable storage medium storing computer-readable instructions executable by at least one processor to cause the at least one processor to perform the steps of a query processing method as described above.
Compared with the prior art, the embodiment of the application has the following main beneficial effects:
in the embodiment of the application, when a query request of an application center for target product application triggered by a user is received, firstly, acquiring the user information from the query request, and determining a target user type of the user based on the user information; then, based on a target processing rule corresponding to the target user type, acquiring target application permission information corresponding to the user information; subsequently judging whether the target application authority accords with a preset appointed loading scene or not; if yes, calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism; and finally, executing response processing corresponding to the query request based on the target interface. After receiving a query request of an application center for target product application triggered by a user, the embodiment of the invention determines the target user type of the user based on the user information carried in the query request, and judges the target user type of the user by using the target user type, and further, the embodiment of the invention can intelligently realize rapid acquisition of target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type, thereby being beneficial to calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism according to the acquired target application permission information, realizing rapid execution of response processing corresponding to the query request, effectively improving the response efficiency of the interface, improving the response efficiency of the query request, reducing the server pressure of the target product application, and being beneficial to improving the use experience of the user.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.
It is apparent that the embodiments described above are only some embodiments of the present application, but not all embodiments, the preferred embodiments of the present application are given in the drawings, but not limiting the patent scope of the present application. This application may be embodied in many different forms, but rather, embodiments are provided in order to provide a more thorough understanding of the present disclosure. Although the present application has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that modifications may be made to the embodiments described in the foregoing, or equivalents may be substituted for elements thereof. All equivalent structures made by the specification and the drawings of the application are directly or indirectly applied to other related technical fields, and are also within the protection scope of the application.

Claims (10)

1. A method of query processing comprising the steps of:
receiving a query request of an application center for target product application, which is triggered by a user; wherein, the query request carries user information of the user;
acquiring the user information from the query request, and determining a target user type of the user based on the user information;
acquiring target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type;
judging whether the target application authority accords with a preset appointed loading scene or not;
if yes, calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism;
and executing response processing corresponding to the query request based on the target interface.
2. The query processing method according to claim 1, wherein the step of acquiring the target application right information corresponding to the user information based on the target processing rule corresponding to the target user type specifically includes:
judging whether the user belongs to an active user or not based on the target user type;
if the user does not belong to the active user, acquiring classification information corresponding to the user information;
Acquiring application permission information corresponding to the classification information from a preset cache;
and taking the application authority information as the target application authority information.
3. The query processing method according to claim 2, wherein the step of obtaining application permission information corresponding to the classification information from a preset cache specifically includes:
judging whether first classification information matched with the classification information is stored in a preset local memory cache or not;
if the local memory cache stores first classification information matched with the classification information, acquiring application permission information corresponding to the first classification information from the local memory cache;
if the local memory cache does not store the first classification information matched with the classification information, judging whether a preset redis cache stores the second classification information matched with the classification information or not;
and if the redis cache stores the second classification information matched with the classification information, acquiring application permission information corresponding to the second classification information from the redis cache.
4. The query processing method according to claim 3, further comprising, before the step of acquiring application permission information corresponding to the classification information from a preset cache:
Calling a preset data acquisition interface;
acquiring appointed application permission information of an inactive user through the data acquisition interface;
storing the appointed application authority information into the local memory cache; and
and storing the appointed application authority information into the redis cache.
5. The query processing method according to claim 1, wherein the step of acquiring the target application right information corresponding to the user information based on the target processing rule corresponding to the target user type specifically includes:
judging whether the user belongs to an active user or not based on the target user type;
if the user belongs to an active user, calling preset active user data;
and acquiring target application permission information corresponding to the user information from the active user data.
6. The query processing method according to claim 1, wherein the step of determining the target user type of the user based on the user information specifically comprises:
calling a preset active user pool;
judging whether target user information matched with the user information is stored in the active user pool;
If the active user pool stores target user information matched with the user information, judging that the user belongs to the active user, and generating a target user type with the content being the active user;
and if the active user pool does not store the target user information matched with the user information, judging that the user belongs to the inactive user, and generating a target user type with the content of the inactive user.
7. The query processing method of claim 6, further comprising, prior to said step of invoking the preset pool of active users:
acquiring user access data and log records in a preset time period;
analyzing and processing the user access data and the log records, and determining appointed users belonging to active users from all the initial users;
acquiring appointed user information of the appointed user;
and storing the specified user information into the active user pool.
8. A query processing apparatus, comprising:
the receiving module is used for receiving a query request of an application center for target product application, which is triggered by a user; wherein, the query request carries user information of the user;
The determining module is used for acquiring the user information from the query request and determining the target user type of the user based on the user information;
the acquisition module is used for acquiring target application permission information corresponding to the user information based on a target processing rule corresponding to the target user type;
the judging module is used for judging whether the target application permission accords with a preset appointed loading scene or not;
the calling module is used for calling a target interface corresponding to the target application permission based on a preset asynchronous loading mechanism if the target application permission is met;
and the processing module is used for executing response processing corresponding to the query request based on the target interface.
9. A computer device comprising a memory having stored therein computer readable instructions which when executed by a processor implement the steps of the query processing method of any of claims 1 to 7.
10. A computer readable storage medium having stored thereon computer readable instructions which when executed by a processor implement the steps of the query processing method of any of claims 1 to 7.
CN202311214142.3A 2023-09-19 2023-09-19 Query processing method, device, computer equipment and storage medium Pending CN117251468A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311214142.3A CN117251468A (en) 2023-09-19 2023-09-19 Query processing method, device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311214142.3A CN117251468A (en) 2023-09-19 2023-09-19 Query processing method, device, computer equipment and storage medium

Publications (1)

Publication Number Publication Date
CN117251468A true CN117251468A (en) 2023-12-19

Family

ID=89128736

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311214142.3A Pending CN117251468A (en) 2023-09-19 2023-09-19 Query processing method, device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN117251468A (en)

Similar Documents

Publication Publication Date Title
CN117251228A (en) Function management method, device, computer equipment and storage medium
CN117094729A (en) Request processing method, device, computer equipment and storage medium
CN117251490A (en) Data query method, device, computer equipment and storage medium
CN116934283A (en) Employee authority configuration method, device, equipment and storage medium thereof
CN116956326A (en) Authority data processing method and device, computer equipment and storage medium
CN116383787A (en) Page creation method, page creation device, computer equipment and storage medium
CN116661936A (en) Page data processing method and device, computer equipment and storage medium
CN117251468A (en) Query processing method, device, computer equipment and storage medium
CN116842011A (en) Blood relationship analysis method, device, computer equipment and storage medium
CN117407420A (en) Data construction method, device, computer equipment and storage medium
CN117390119A (en) Task processing method, device, computer equipment and storage medium
CN115080045A (en) Link generation method and device, computer equipment and storage medium
CN116910095A (en) Buried point processing method, buried point processing device, computer equipment and storage medium
CN117390241A (en) Data display method, device, computer equipment and storage medium
CN117034173A (en) Data processing method, device, computer equipment and storage medium
CN116932090A (en) Tool pack loading method, device, computer equipment and storage medium
CN115809241A (en) Data storage method and device, computer equipment and storage medium
CN117422523A (en) Product online method and device, computer equipment and storage medium
CN116738948A (en) Data processing method, device, computer equipment and storage medium
CN117278263A (en) Authentication processing method, authentication processing device, computer equipment and storage medium
CN117217684A (en) Index data processing method and device, computer equipment and storage medium
CN117076775A (en) Information data processing method, information data processing device, computer equipment and storage medium
CN116663003A (en) Attack detection method, attack detection device, computer equipment and storage medium
CN116360796A (en) Optimization method and device of sql script, computer equipment and storage medium
CN116627416A (en) Page configuration method, page configuration device, computer equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination