CN115658794A - Data query method and device, computer equipment and storage medium - Google Patents
Data query method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN115658794A CN115658794A CN202211576146.1A CN202211576146A CN115658794A CN 115658794 A CN115658794 A CN 115658794A CN 202211576146 A CN202211576146 A CN 202211576146A CN 115658794 A CN115658794 A CN 115658794A
- Authority
- CN
- China
- Prior art keywords
- target
- interface
- data
- query
- identifier
- 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.)
- Granted
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a data query method, a data query device, computer equipment and a storage medium. The method comprises the following steps: acquiring a data query request, and determining a data identifier corresponding to the data query request; determining a calling record of a target interface corresponding to the target interface identifier, and determining a target data source corresponding to the target interface according to preset configuration information; when the calling record represents that the target interface is called for the first time, determining an interface type corresponding to the target interface, and determining a data query mode according to the interface type; and calling the target interface to query the target data source in a data query mode to obtain a query result corresponding to the target interface. By adopting the method, the diversity of data query can be improved.
Description
Technical Field
The present application relates to the field of big data, and in particular, to a data query method, apparatus, computer device, and storage medium.
Background
With the development of the big data field, on one hand, data integration is provided for the enterprise data mart, and on the other hand, for the data which have fallen into the database, how to query the data through an external system is also a very important research focus. At present, for a data query task, a worker needs to participate deeply in the processes of interface configuration and the like, so that after a query interface is constructed, data query can be performed by adopting a simple query statement.
Therefore, the problem that the configuration threshold of the data query task is high and the query statement form is single is how to improve the diversity of the data query.
Disclosure of Invention
In view of the above, it is necessary to provide a data query method, an apparatus, a computer device and a computer readable storage medium capable of improving the diversity of data query.
In a first aspect, the present application provides a data query method. The method comprises the following steps:
acquiring a data query request, and determining a data identifier corresponding to the data query request; the data identification comprises a target interface identification needing to be called;
determining a calling record of a target interface corresponding to the target interface identifier, and determining a target data source corresponding to the target interface according to preset configuration information;
when the calling record represents that the target interface is called for the first time, determining an interface type corresponding to the target interface, and determining a data query mode according to the interface type;
and calling the target interface to query the target data source in the data query mode to obtain a query result corresponding to the target interface.
In one embodiment, before the obtaining the data query request, the method further includes: acquiring a data configuration request, and determining a current management type in the data configuration request; the current management type at least comprises one of data source management, interface management of a next level of the data source management or application management of a next level of the interface management; determining a data identifier to be configured according to the current management type; responding to the configuration operation aiming at the data identification to be configured, and obtaining a field table of the data identification to be configured corresponding to the current management type; determining the management type of the next level of the current management type, taking the management type of the next level as a new current management type, and returning to the step of determining the data identifier to be configured according to the current management type to continue until a field table of the data identifier to be configured corresponding to the management type of the last level is obtained; and integrating the field tables corresponding to the management types of each hierarchy to obtain configuration information.
In one embodiment, the data identifier to be configured comprises an interface identifier; the obtaining a field table of the to-be-configured data identifier corresponding to the current management type in response to the configuration operation for the to-be-configured data identifier includes: responding to the configuration operation aiming at the interface identifier, and obtaining an initial field table of the interface identifier; performing work order audit on the initial field table to obtain an audit result; and when the verification result represents that the verification is passed, updating the initial field table to obtain a field table of the interface identifier corresponding to the interface management.
In one embodiment, the data identifier to be configured comprises an application identifier; the obtaining a field table of the to-be-configured data identifier corresponding to the current management type in response to the configuration operation for the to-be-configured data identifier includes: displaying a configuration interface comprising an interface identification list; in response to the association operation for the application identifier and the interface identifier list, determining an associated interface identifier associated with the application identifier; responding to attribute configuration operation aiming at the application identifier to obtain attribute information of the application identifier; the attribute information at least comprises a user authority list and charging information; and synthesizing the associated interface identification and the attribute information to obtain a field table of the application identification corresponding to the application management.
In one embodiment, the data identification comprises a target application identification: after the determining the data identifier corresponding to the data query request, the method further includes: determining an application field table corresponding to the target application identifier according to preset configuration information; the application field table comprises an associated interface identifier and a user permission list; determining a query user corresponding to the data query request, and performing authority management on the query user through the user authority list to obtain a management result; and when the management result representation can be queried, taking the associated interface identification as a target interface identification.
In an embodiment, the determining, according to preset configuration information, a target data source corresponding to the target interface includes: determining a target field table corresponding to the target interface identifier according to preset configuration information; the target field table includes an associated data source identification; determining a data source field table corresponding to the associated data source identifier; the data source field table comprises a connection address; the data source field table is obtained by carrying out configuration operation on the associated data source identification; and taking the data source corresponding to the connection address in the data warehouse as a target data source.
In one embodiment, the data query mode comprises a first query mode; the querying the target data source by the data querying method to obtain a querying result corresponding to the target interface includes: when the interface type is a database type, determining an initial query parameter in the data query request, and taking a standard format of the target interface identifier as an auxiliary parameter; determining a database query format corresponding to the database type, and splicing the initial query parameter and the auxiliary parameter according to the database query format to obtain a target query parameter; and querying from the target data source through the target query parameter to obtain a query result corresponding to the target interface.
In one embodiment, the data query mode comprises a second query mode; the target data source is deployed in the target container; the querying the target data source by the data querying method to obtain a querying result corresponding to the target interface includes: when the interface type is a special script type, acquiring a target protocol, and establishing communication with the target container through the target protocol; performing trigger operation on the target container; the triggering operation is used for triggering the target container to query the target data source to obtain a query result corresponding to the target interface; and acquiring the query result fed back by the target container.
In an embodiment, after obtaining the query result corresponding to the target interface, the method further includes: determining a target field table corresponding to the target interface identifier; the target field table includes cache information; recording the process of calling the target interface and the query result to obtain a current recording result, and judging whether the current recording result needs to be cached according to the caching information; if not, updating the call record according to a preset recording period and the current recording result to obtain a new call record.
In a second aspect, the present application further provides a data query apparatus. The device comprises:
the query request acquisition module is used for acquiring a data query request and determining a data identifier corresponding to the data query request; the data identification comprises a target interface identification needing to be called;
the query mode determining module is used for determining a calling record of a target interface corresponding to the target interface identifier and determining a target data source corresponding to the target interface according to preset configuration information; when the calling record represents that the target interface is called for the first time, determining an interface type corresponding to the target interface, and determining a data query mode according to the interface type;
and the query result determining module is used for calling the target interface to query the target data source in the data query mode to obtain a query result corresponding to the target interface.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:
acquiring a data query request, and determining a data identifier corresponding to the data query request; the data identification comprises a target interface identification needing to be called;
determining a calling record of a target interface corresponding to the target interface identifier, and determining a target data source corresponding to the target interface according to preset configuration information;
when the calling record represents that the target interface is called for the first time, determining an interface type corresponding to the target interface, and determining a data query mode according to the interface type;
and calling the target interface to query the target data source in the data query mode to obtain a query result corresponding to the target interface.
In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium has stored thereon a computer program which, when executed by a processor, performs the steps of:
acquiring a data query request, and determining a data identifier corresponding to the data query request; the data identification comprises a target interface identification needing to be called;
determining a calling record of a target interface corresponding to the target interface identifier, and determining a target data source corresponding to the target interface according to preset configuration information;
when the calling record represents that the target interface is called for the first time, determining an interface type corresponding to the target interface, and determining a data query mode according to the interface type;
and calling the target interface to query the target data source in the data query mode to obtain a query result corresponding to the target interface.
According to the data query method, the data query device, the computer equipment and the storage medium, the data query request is obtained, and the data identifier corresponding to the data query request is determined, wherein the data identifier comprises the target interface identifier required to be called. Determining a target data source corresponding to the target interface by determining a calling record of the target interface corresponding to the target interface identifier and according to preset configuration information; when the calling record represents that the target interface is called for the first time, the interface type corresponding to the target interface can be determined, so that the data query mode is determined according to the interface type; therefore, the target interface can be called, so that the target data source is queried in a data query mode, and a query result corresponding to the target interface is obtained. Because different data query modes are obtained after the interface type corresponding to the target interface is determined, compared with the traditional mode of performing data query only by adopting simple query statements, the method and the device can flexibly adopt different data query modes to query the target data source, thereby improving the diversity of data query.
Drawings
FIG. 1 is a diagram of an application environment of a data query method in one embodiment;
FIG. 2 is a flow diagram that illustrates a methodology for querying data in one embodiment;
FIG. 3 is a system architecture diagram of an interface system in one embodiment;
FIG. 4 is a timing diagram of querying data in one embodiment;
FIG. 5 is a flow diagram illustrating the determination of configuration information in one embodiment;
FIG. 6 is a block diagram showing the structure of a data query apparatus according to an embodiment;
FIG. 7 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The data query method provided by the embodiment of the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102 may communicate with the server 104 over a network. The terminal 102 and the server 104 may both independently execute the data query method provided in the embodiment of the present application, or may cooperatively execute the data query method provided in the embodiment of the present application. Taking an example that the terminal 102 and the server 104 cooperate to execute the data query method as an example, the terminal 102 is configured to send the acquired data query request to the server 104. The server 104 is configured to determine a target interface identifier corresponding to the data query request; and determining a calling record of a target interface corresponding to the target interface identifier, and determining a target data source corresponding to the target interface according to preset configuration information. The server 104 is further configured to determine an interface type corresponding to the target interface when the calling record represents that the target interface is primarily called, and determine a data query mode according to the interface type; and calling the target interface to query the target data source in a data query mode to obtain a query result corresponding to the target interface, and sending the query result to the terminal 102. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In one embodiment, as shown in fig. 2, a data query method is provided, which is described by taking the method as an example applied to the server in fig. 1, and includes the following steps:
step 202, a data query request is obtained, and a data identifier corresponding to the data query request is determined.
The data identification comprises a target interface identification needing to be called; the data query request characterizes a request to query for data associated with the target interface identification. The data identification may further include at least one of a target data source identification and a target application identification.
Specifically, the server may be a data mart-based interface system, and fig. 3 is a system architecture diagram of the interface system, wherein the interface system includes middleware and a business layer. The middleware is used for carrying out additional monitoring and operation on the request at the global level, and comprises the steps of carrying out signature verification on interface calling, controlling the request frequency, detecting the interface state and the like. The service layer is the core of the whole interface system and can be used for analyzing the target interface identification needing to be called in the data query request.
In one embodiment, when the data identifier is a target data source identifier, the data query request may characterize a request to query data in the corresponding data source.
In one embodiment, when the data identifier is a target application identifier, the server determines a target application corresponding to the application identifier, and determines a plurality of associated interface identifiers belonging to the target application. And the associated interface identifier at this time is used as a target interface identifier needing to be called. That is, each application includes a plurality of interface identifiers, and when an application is directly triggered to execute a data query request, a plurality of called target interface identifiers are included.
In one embodiment, FIG. 4 is a timing diagram of a query for data. When the user triggers the external system in the terminal to generate the data query request, the external system can trigger the interface system to call the interface based on the target interface identifier, so that the interface system performs signature verification on the user. And when the signature of the user passes the verification, the subsequent processes can be continuously executed.
In one embodiment, after the login verification of the user passes, the server may respond to the configuration operation of the user on the data identifier to be configured to obtain configured configuration information.
And 204, determining a calling record of the target interface corresponding to the target interface identifier, and determining a target data source corresponding to the target interface according to preset configuration information.
The calling record records relevant information associated with each calling of the target interface, such as calling times, calling time, success of calling, data desensitization, and the like.
Specifically, the server may obtain preset configuration information from the database, where the preset configuration information includes a plurality of field tables, and each field table includes a data identifier to be configured. The data identification to be configured at least comprises a data source identification, an interface identification and an application identification; the field table records information such as creation time and number obtained when the data identifier to be configured is configured. The server searches an interface identifier which is the same as the target interface identifier from a plurality of interface identifiers in the data identifier to be configured, and takes a field table where the interface identifier is located as a target field table. The server can determine the target data source corresponding to the target interface according to the information in the target field table.
In one embodiment, when the server obtains the data configuration request, the data identifier to be configured in the data query request may be determined, and a field table corresponding to the data identifier to be configured is obtained in response to a configuration operation of the user for the data identifier to be configured. For example, when the data identifier to be configured is the data source identifier ID1, the field table corresponding to the data source identifier ID1 may be obtained through configuration.
In an embodiment, referring to fig. 3, the interface system further includes a data layer, where the data layer includes various data warehouses related to interface data, also called data sources, and the data warehouses can be called by means of open database connection, where the data sources at least include MySQL, inpala, hadoop, clickhouse, and the like; also included in the data layer is a cache, such as a redis cache.
In one embodiment, determining a target data source corresponding to a target interface according to preset configuration information includes: determining a target field table corresponding to the target interface identifier according to preset configuration information; determining a data source field table corresponding to the associated data source identification; and taking the data source corresponding to the connection address in the data warehouse as a target data source.
Wherein the target field table includes an associated data source identifier; the data source field table is obtained by carrying out configuration operation on the associated data source identification; the data source field table includes a connection address. Wherein, the connection address can be sqlalchemy _ uri field information. That is, the server can accurately obtain the target data source from the data warehouse through the connection address. Therefore, the position of the target data source in the data warehouse can be quickly positioned by associating the data source field table corresponding to the data source identification.
And step 206, when the calling record represents that the target interface is called for the first time, determining the interface type corresponding to the target interface, and determining a data query mode according to the interface type.
The interface type comprises a database type, a special script type and a conventional script type; the special script may be a Python script and the regular script may be a PHP script.
Specifically, when the call record represents that the target interface is called for the first time, that is, the target cache does not store target data associated with the target interface, at this time, the server is required to determine the interface type of the target interface. Because each interface has a number, after the server needle presets the interface type of the interface, the server needle can inquire the configured interface type through the number of the interface. When the interface type is a database type, the server determines that the data query mode is a first query mode, namely a mode of performing data query through an SQL query statement. When the interface type is the special script type, the server determines that the data query mode is the second query mode, namely, the data query is carried out by logging in a remote target container through a target protocol. And when the interface type is the conventional script type, the server determines that the data query mode is the third query mode, namely directly executes the script code corresponding to the target interface, so that the data query is completed through the script code.
In one embodiment, the server may determine a target field table corresponding to the target interface, where the target field table includes a special field, and the special field may be data _ provider, and the server determines the data query mode according to a value of the special field, for example, if the value of the special field is 1, the server corresponds to the first query mode, and so on.
In an embodiment, referring to fig. 4, when the call record indicates that the target interface is not the first call, the server may determine whether the target data corresponding to the target interface identifier is cached according to the cache information in the target field table. If yes, representing the last data query process, finishing the cache of the target data corresponding to the target interface identification, and at the moment, directly reading the data from the target cache. If not, the process of determining the interface type corresponding to the target interface is continuously executed.
And step 208, calling the target interface to query the target data source in a data query mode to obtain a query result corresponding to the target interface.
Specifically, the server executes a call to the target interface to trigger the target interface to query the target data source in different data query modes. And when the script code is executed, the target data source can be queried to obtain a query result corresponding to the target interface.
In one embodiment, when the script code is configured with a data table associated with the target interface, the target data may be read from the data table in the target data source.
In one embodiment, as shown with reference to fig. 3, the interface system may be deployed in a runtime environment such as a cloud host and a second virtual host. And a firewall of a network layer in the interface system is used for taking charge of the overall safety control and wind control interception of the project.
In the data query method, the data query request is obtained, and the data identifier corresponding to the data query request is determined, wherein the data identifier comprises the target interface identifier to be called. Determining a target data source corresponding to the target interface by determining a calling record of the target interface corresponding to the target interface identifier and according to preset configuration information; when the calling record represents that the target interface is called for the first time, the interface type corresponding to the target interface can be determined, so that the data query mode is determined according to the interface type; therefore, the target interface can be called, so that the target data source is queried in a data query mode, and a query result corresponding to the target interface is obtained. Because different data query modes are obtained after the interface type corresponding to the target interface is determined, compared with the traditional mode of performing data query only by adopting simple query statements, the method and the device can flexibly adopt different data query modes to query the target data source, thereby improving the diversity of data query.
In one embodiment, after determining the data identifier corresponding to the data query request, the method further includes: determining an application field table corresponding to the target application identifier according to preset configuration information; determining a query user corresponding to the data query request, and performing authority management on the query user through a user authority list to obtain a management result; and when the management result representation can be inquired, taking the associated interface identification as a target interface identification.
The data identification comprises a target application identification; the target application identification corresponds to a target application; the application field table comprises an associated interface identifier and a user permission list; the application field table is obtained by carrying out configuration operation on the target application identifier; the associated interface mark represents the interface mark belonging to the target application, and the user permission list is the permission limit for calling the interface in the target application.
Specifically, since the user performs account login when triggering the data query request, the server may determine the corresponding querying user. The server manages the authority of the inquiring user through the user authority list, and when the user authority list does not include the inquiring user, the obtained management result is not inquired; when the user authority list comprises the inquiry user, the obtained management result is inquired, namely the management result has the calling authority to the target interface, and the associated interface identifier can be used as the target interface identifier.
In the embodiment, the authority management is performed on the inquiry user in advance, so that an unsafe visitor can be prevented from calling the interface, and the safety of interface calling is ensured; when the target interface is determined to have the calling right, the associated interface identifier can be directly used as the target interface identifier, so that the efficiency of querying the data is improved.
In one embodiment, querying a target data source in a data query manner to obtain a query result corresponding to a target interface includes: when the interface type is a database type, determining initial query parameters in the data query request, and taking the standard format of a target interface as auxiliary parameters; determining a database query format corresponding to the type of the database, and splicing the initial query parameters and the auxiliary parameters according to the database query format to obtain target query parameters; and querying from the target data source through the target query parameters to obtain a query result corresponding to the target interface.
The data query mode comprises a first query mode. The data query request also includes initial query parameters entered by the user. The standard format of the target interface includes, but is not limited to: public interface name {// interface content }, etc.
Specifically, when the interface type is a database type, the server can splice the initial query parameters and the auxiliary parameters to obtain target query parameters conforming to a database query format, wherein the target query parameters can be database query SQL statements. And the server can inquire the target data source through the target inquiry parameters to obtain an inquiry result corresponding to the target interface.
In the embodiment, the database query is performed in the form of the SQL statement, so that the corresponding query mode can be adopted according to different interface types, and the diversity of data query is ensured.
In one embodiment, querying a target data source in a data query manner to obtain a query result corresponding to a target interface includes: when the interface type is a special script type, acquiring a target protocol, and establishing communication with a target container through the target protocol; performing trigger operation on the target container; the triggering operation is used for triggering the target container to query the target data source to obtain a query result corresponding to the target interface; and acquiring a query result fed back by the target container.
The data query mode comprises a second query mode; the target data source is deployed in a target container, the target container corresponds to the platform server, and the target container can be an application container engine, such as a Docker; the target protocol may be a secure shell protocol, such as ssh protocol.
Specifically, the server is remotely connected to the platform server by a protocol method of logging in to the platform server, that is, by configuring target protocol parameters, so that communication between the server and the target container is established. When the server triggers the target container, the target data source can be queried through the remotely connected platform server, and the obtained query result is fed back to the server.
In the embodiment, data query is realized by providing a remote connection mode aiming at the interface with a special script type, application isolation and rapid deployment are realized, the difficulty of interface calling is reduced, the process of querying data is more flexible, and the diversity of data query is ensured.
In one embodiment, the interface system employs laravel as a development framework.
In one embodiment, design patterns in the interface system include an observer pattern and a factory pattern, and the observer pattern is used when there is a one-to-many relationship between objects. For example, when an object is modified, objects that depend on it are automatically notified. The observer pattern belongs to a behavioral pattern. Factory mode provides an optimal way to create objects without exposing the creation logic to the client when creating the objects, and by using a common interface to point to newly created objects
In one embodiment, as shown in fig. 5, before obtaining the data query request, a process of determining configuration information is further included, including the following steps:
step 502, obtain the data configuration request, and determine the current management type in the data configuration request.
The current management type at least comprises one of data source management, interface management of a next level of data source management or application management of a next level of interface management. The data source management comprises the processes of adding, modifying or deleting the data source and the like; the interface management comprises adding interfaces, calling and testing, rolling back the interfaces, copying the interfaces, submitting and reviewing the interfaces, recording interface details and the like; the application management comprises key management, charging management and interface authority management, wherein the application management mainly relates to configuring a plurality of interfaces belonging to each application and limiting the calling authority of a query user.
Specifically, referring to FIG. 3, the business layer in the interface system includes data source management, interface management, and application management. When the service layer in the interface system responds to the data configuration request of the user, the current management type in the data configuration request can be determined.
In one embodiment, as shown with reference to FIG. 3, the business layer in the interface system also includes documentation systems, work order auditing, data export, log management, and call statistics. The document system is used for generating an interface document with a special format according to the configuration information corresponding to the interface, wherein the special format is, for example, a markdown format. And the work order audit is used for auditing the interface newly added or modified by the user each time. Data export may export records, export status, export results, and the like through a user-triggered export job viewing interface. The log management can view SQL execution records and interface call records. The call statistics is used for recording the process of interface call by statistics, wherein the process comprises call times statistics and interface cost statistics.
Step 504, determining the data identifier to be configured according to the current management type.
The data identifier to be configured may be an ID corresponding to a management type, and if the current management type is data source management, the corresponding data identifier to be configured is a data source identifier; if the current management type is interface management, the corresponding data identifier to be configured is an interface identifier; and if the current management type is application management, the corresponding data identifier to be configured is an application identifier.
Step 506, in response to the configuration operation for the data identifier to be configured, a field table of the data identifier to be configured corresponding to the current management type is obtained.
In one embodiment, in response to a configuration operation for a data identifier to be configured, obtaining a field table of the data identifier to be configured corresponding to a current management type includes: responding to the configuration operation aiming at the interface identifier, and obtaining an initial field table of the interface identifier; checking the work order of the initial field table to obtain a checking result; and when the verification result represents that the verification is passed, updating the initial field table to obtain a field table of the interface identifier corresponding to the interface management.
The data identifier to be configured comprises an interface identifier.
Specifically, interface management in the server may complete configuration operations on the interface identifier, and when the server responds to the configuration operations of the user on the interface identifier, for example, configure interface classification, cache information, request interval, and the like, an initial field table corresponding to the interface identifier may be obtained. After the interface preliminary configuration corresponding to the interface identifier is completed, the interface state is in a draft state, and at this time, the user needs to submit and audit the interface identifier, so that the work order audit can be performed on the initial field table through the work order audit in the server. When the work order is audited by the auditor and the audit result represents that the audit is passed, the initial field table is updated to obtain the field table of the interface identifier corresponding to the interface management, namely the field table at the moment takes effect formally. Meanwhile, the initial field table can be modified and the like. The initial field table may also be referred to as an interface draft table, and the field table of the interface identifier may also be referred to as an interface table, where the interface draft table is shown in table 1 and the interface table is shown in table 2.
Table 1:
table 2:
in an embodiment, when the initial field table is updated, the server may further generate an interface version table corresponding to the interface identifier, where the interface version table is as shown in table 3, and is used to perform snapshot recording on a modification process of each interface configuration, so as to facilitate subsequent source tracing.
Table 3:
in this embodiment, the initial field table corresponding to the interface identifier can be configured in real time according to the interface construction requirements of the user in different scenes, and meanwhile, the work order is adopted to audit or modify the initial field table, so that only the formally effective initial field table can be used as the field table of the interface identifier, thereby ensuring the safety of the interface.
In one embodiment, in response to a configuration operation for a data identifier to be configured, obtaining a field table of the data identifier to be configured corresponding to a current management type includes: displaying a configuration interface comprising an interface identification list; in response to the association operation aiming at the application identifier and the interface identifier list, determining an associated interface identifier associated with the application identifier; responding to attribute configuration operation aiming at the application identifier to obtain attribute information of the application identifier; and integrating the associated interface identifier and the attribute information to obtain a field table of the application identifier corresponding to the application management.
The data identification to be configured comprises an application identification; the attribute information includes at least a user authority list and billing information.
Specifically, a configuration interface including a configuration list is displayed in the server, and when the data identifier to be configured is the application identifier, the configuration list is an interface identifier list. And the server responds to the selection operation of the user for the interface identification in the interface identification list, and takes the selected interface identification as the associated interface identification associated with the application identification. The associated interface identifier at this time may be regarded as having completed the related configuration operation, that is, completing the configuration between the application identifier and the interface identifier of the previous stage.
Further, the server responds to the attribute configuration operation aiming at the application identifier, and obtains the attribute information of the application identifier, such as whether the associated interface identifier is configured for charging, a user authority list and the like. The user authority list is used for limiting the ip address of the server of the calling party of the calling interface, and if the ip address is not in the user authority list, data access is refused. And the server integrates the associated interface identifier and the attribute information to obtain a field table of the application identifier corresponding to the application management. The field table of the application identifier may also be referred to as an application table, and the application table is shown in table 4.
Table 4:
in the embodiment, the interface identifiers are subjected to application management, so that the target applications to which the plurality of interface identifiers belong and the user permissions corresponding to different query users are determined, the server can trigger the data query request based on the target applications directly, most query processes are automatically completed, and the efficiency of data query is improved.
And step 508, determining the management type of the next level of the current management type, taking the management type of the next level as a new current management type, and returning to the step of determining the data identifier to be configured according to the current management type to continue until a field table of the data identifier to be configured corresponding to the management type of the last level is obtained.
In one embodiment, when the data identifier to be configured is a plurality of data source identifiers, that is, when data source management is performed, the server obtains a configured data source identifier list in response to creation and configuration operations of a user for each data source identifier, and displays the configured data source identifier list in the configuration interface.
In one embodiment, the management type of the last level may be any one of document system, data export, log management, and call statistics. When the management type of the last level is data export, the target interface may be configured to identify a corresponding export record, and the export record is shown in table 5.
Table 5:
in an embodiment, when the management type of the last level is a call statistic, the server configures the last level, where the call statistic may include single recording and recording by using a dimension of day, and each time an interface call is performed, a corresponding record is performed according to the serial number of the interface, and a call statistic table obtained by recording the call process performed this time is recorded. In addition, the calling statistics can also be used for interface charging, calling frequency records and the like, so that an external system can conveniently settle charges and provide specific details and the like. The call statistics table is shown in table 6.
Table 6:
step 510, synthesizing the field table corresponding to the management type of each hierarchy to obtain configuration information.
In this embodiment, the data identifier to be configured corresponding to the management type is determined, and then the configuration operation of the data identifier to be configured is completed, so as to obtain the field table corresponding to the data identifier to be configured, so that the configured field table can be accurately obtained subsequently when the target data source is determined, and the efficiency of data query is improved. Meanwhile, the user can flexibly configure the corresponding management type, so that the development cost and the configuration threshold are reduced, and the flexibility of data query is improved.
In one embodiment, after obtaining the query result corresponding to the target interface, the method includes: determining a target field table corresponding to the target interface identifier; recording the process of calling the target interface and the query result to obtain a current recording result, and judging whether the current recording result needs to be cached or not according to the caching information; if not, updating the calling record according to the preset recording period and the current recording result to obtain a new calling record.
The target field table comprises cache information and desensitization information, the cache information represents whether target data corresponding to a target interface needs to be cached after the target interface corresponding to the target interface identifier is called, and the desensitization information represents whether desensitization processing needs to be performed on the target data.
Specifically, referring to fig. 4, when the server obtains the target field table corresponding to the target interface identifier, it may determine whether the target data needs to be subjected to data desensitization according to desensitization information in the target field table, and if so, perform data desensitization processing; if not, directly recording the process of calling the target interface and the query result to obtain the current recording result. Wherein, the target data after the data desensitization processing can also be recorded. The server judges whether the current recording result needs to be cached or not according to the caching information in the target field table, and if so, the server writes the query result into the target cache; if not, carrying out asynchronous data statistics, namely updating the calling record according to a preset recording period and a current recording result to obtain a new calling record; meanwhile, the current recording result does not need to be cached, and can also be directly used as a data result and returned to an external system.
In the embodiment, the call records are updated, the memorability tracking of each call can be facilitated, and if the interface call is abnormal, the problem can be quickly positioned in a short time; meanwhile, big data analysis is conveniently carried out, information such as frequency and response time of each interface is displayed from different dimensions, and reliable reference is provided for speed optimization. In addition, for the whole data query process, the method and the system realize systematization and automation of the whole process from interface configuration, calling, recording, analysis, data export and the like, improve the efficiency of data query, and greatly reduce development and labor cost.
It should be understood that, although the steps in the flowcharts related to the embodiments are shown in sequence as indicated by the arrows, the steps are not necessarily executed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the above embodiments may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least a part of the steps or stages in other steps.
Based on the same inventive concept, the embodiment of the present application further provides a data query device for implementing the above-mentioned data query method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so specific limitations in one or more embodiments of the data query device provided below can refer to the limitations on the data query method in the foregoing, and details are not described here.
In one embodiment, as shown in fig. 6, there is provided a data query apparatus 600, including: a query request obtaining module 602, a query mode determining module 604, and a query result determining module 606, wherein:
a query request obtaining module 602, configured to obtain a data query request and determine a data identifier corresponding to the data query request; the data identification comprises a target interface identification needing to be called.
The query mode determining module 604 is configured to determine a call record of a target interface corresponding to the target interface identifier, and determine a target data source corresponding to the target interface according to preset configuration information; and when the calling record represents that the target interface is called for the first time, determining the interface type corresponding to the target interface, and determining a data query mode according to the interface type.
And the query result determining module 606 is configured to invoke the target interface, so as to query the target data source in a data query manner, and obtain a query result corresponding to the target interface.
In one embodiment, the data query apparatus 600 further includes a data configuration module 608, configured to obtain the data configuration request and determine the current management type in the data configuration request; the current management type at least comprises one of data source management, interface management of a next level of data source management or application management of a next level of interface management; determining a data identifier to be configured according to the current management type; responding to the configuration operation aiming at the data identification to be configured, and obtaining a field table of the data identification to be configured corresponding to the current management type; determining the management type of the next level of the current management type, taking the management type of the next level as a new current management type, and returning to the step of determining the data identifier to be configured according to the current management type to continue until a field table of the data identifier to be configured corresponding to the management type of the last level is obtained; and integrating the field table corresponding to the management type of each hierarchy to obtain configuration information.
In one embodiment, the data configuration module 608 is further configured to obtain an initial field table of the interface identifier in response to a configuration operation for the interface identifier; checking the work order of the initial field table to obtain a checking result; and when the verification result represents that the verification is passed, updating the initial field table to obtain a field table of the interface identifier corresponding to the interface management.
In one embodiment, the data configuration module 608 is further configured to present a configuration interface including a list of interface identifications; in response to the association operation aiming at the application identifier and the interface identifier list, determining an associated interface identifier associated with the application identifier; responding to attribute configuration operation aiming at the application identifier to obtain attribute information of the application identifier; the attribute information at least comprises a user authority list and charging information; and integrating the associated interface identifier and the attribute information to obtain a field table of the application identifier corresponding to the application management.
In an embodiment, the query mode determining module 604 further includes an interface identifier determining module 6041, configured to determine, according to preset configuration information, an application field table corresponding to the target application identifier; the application field table comprises an associated interface identifier and a user authority list; determining a query user corresponding to the data query request, and performing authority management on the query user through a user authority list to obtain a management result; and when the management result representation can be queried, taking the associated interface identification as a target interface identification.
In an embodiment, the query mode determining module 604 further includes a data source determining module 6042, configured to determine, according to preset configuration information, a target field table corresponding to the target interface identifier; the target field table includes an associated data source identification; determining a data source field table corresponding to the associated data source identifier; the data source field table comprises connection addresses; the data source field table is obtained by carrying out configuration operation on the associated data source identification; and taking the data source corresponding to the connection address in the data warehouse as a target data source.
In one embodiment, the query mode determining module 604 is further configured to determine an initial query parameter in the data query request when the interface type is a database type, and use a standard format of the target interface identifier as an auxiliary parameter; determining a database query format corresponding to the database type, and splicing the initial query parameters and the auxiliary parameters according to the database query format to obtain target query parameters; and querying from the target data source through the target query parameter to obtain a query result corresponding to the target interface.
In an embodiment, the query mode determining module 604 is further configured to, when the interface type is the special script type, obtain a target protocol, and establish communication with the target container through the target protocol; performing trigger operation on the target container; the triggering operation is used for triggering the target container to query the target data source to obtain a query result corresponding to the target interface; and acquiring a query result fed back by the target container.
In one embodiment, the data query apparatus 600 further includes a call statistics module 610 for determining a target field table corresponding to the target interface identifier; the target field table includes cache information; recording the process of calling the target interface and the query result to obtain a current recording result, and judging whether the current recording result needs to be cached or not according to the caching information; if not, updating the calling record according to the preset recording period and the current recording result to obtain a new calling record.
The modules in the data query device may be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 7. The computer device comprises a processor, a memory, an Input/Output (I/O) interface and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operating system and the computer program to run on the non-volatile storage medium. The database of the computer device is used for storing data query data. The input/output interface of the computer device is used for exchanging information between the processor and an external device. The communication interface of the computer device is used for connecting and communicating with an external terminal through a network. The computer program is executed by a processor to implement a data query method.
It will be appreciated by those skilled in the art that the configuration shown in fig. 7 is a block diagram of only a portion of the configuration associated with the present application, and is not intended to limit the computing device to which the present application may be applied, and that a particular computing device may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.
In an embodiment, a computer-readable storage medium is provided, in which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.
In one embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer-readable storage medium. The computer instructions are read by a processor of a computer device from a computer-readable storage medium, and the computer instructions are executed by the processor to cause the computer device to perform the steps in the above-mentioned method embodiments.
It will be understood by those skilled in the art that all or part of the processes in the methods according to the embodiments described above may be implemented by hardware instructed by a computer program, and the computer program may be stored in a non-volatile computer-readable storage medium, and when executed, may include the processes according to the embodiments of the methods described above. Any reference to memory, databases, or other media used in the embodiments provided herein can include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), magnetic Random Access Memory (MRAM), ferroelectric Random Access Memory (FRAM), phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.
All possible combinations of the technical features in the above embodiments may not be described for the sake of brevity, but should be considered as being within the scope of the present disclosure as long as there is no contradiction between the combinations of the technical features.
The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not to be construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, and these are all within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.
Claims (12)
1. A method for data query, the method comprising:
acquiring a data query request, and determining a data identifier corresponding to the data query request; the data identification comprises a target interface identification needing to be called;
determining a calling record of a target interface corresponding to the target interface identifier, and determining a target data source corresponding to the target interface according to preset configuration information;
when the calling record represents that the target interface is called for the first time, determining an interface type corresponding to the target interface, and determining a data query mode according to the interface type;
and calling the target interface to query the target data source in the data query mode to obtain a query result corresponding to the target interface.
2. The method of claim 1, wherein prior to the obtaining a data query request, the method further comprises:
acquiring a data configuration request, and determining a current management type in the data configuration request; the current management type at least comprises one of data source management, interface management of a next level of the data source management, or application management of a next level of the interface management;
determining a data identifier to be configured according to the current management type;
responding to the configuration operation aiming at the data identification to be configured, and obtaining a field table of the data identification to be configured corresponding to the current management type;
determining the management type of the next level of the current management type, taking the management type of the next level as a new current management type, and returning to the step of determining the data identifier to be configured according to the current management type to continue until a field table of the data identifier to be configured corresponding to the management type of the last level is obtained;
and integrating the field table corresponding to the management type of each hierarchy to obtain configuration information.
3. The method of claim 2, wherein the data identifier to be configured comprises an interface identifier; the current management type comprises interface management; the obtaining, in response to the configuration operation for the to-be-configured data identifier, a field table of the to-be-configured data identifier corresponding to the current management type includes:
responding to the configuration operation aiming at the interface identifier, and obtaining an initial field table of the interface identifier;
performing work order audit on the initial field table to obtain an audit result;
and when the verification result represents that the verification is passed, updating the initial field table to obtain a field table of the interface identifier corresponding to the interface management.
4. The method of claim 2, wherein the data identifier to be configured comprises an application identifier; the current management type comprises application management; the obtaining a field table of the to-be-configured data identifier corresponding to the current management type in response to the configuration operation for the to-be-configured data identifier includes:
displaying a configuration interface comprising an interface identification list;
in response to the association operation for the application identifier and the interface identifier list, determining an associated interface identifier associated with the application identifier;
responding to attribute configuration operation aiming at the application identifier to obtain attribute information of the application identifier; the attribute information at least comprises a user authority list and charging information;
and synthesizing the associated interface identification and the attribute information to obtain a field table of the application identification corresponding to the application management.
5. The method of claim 1, wherein the data identification comprises a target application identification; after the determining the data identifier corresponding to the data query request, the method further includes:
determining an application field table corresponding to the target application identifier according to preset configuration information; the application field table comprises an associated interface identifier and a user permission list;
determining a query user corresponding to the data query request, and performing authority management on the query user through the user authority list to obtain a management result;
and when the management result representation can be inquired, taking the associated interface identification as a target interface identification.
6. The method according to claim 1, wherein the determining a target data source corresponding to the target interface according to preset configuration information includes:
determining a target field table corresponding to the target interface identifier according to preset configuration information; the target field table includes an associated data source identification;
determining a data source field table corresponding to the associated data source identification; the data source field table comprises a connection address; the data source field table is obtained by carrying out configuration operation on the associated data source identification;
and taking the data source corresponding to the connection address in the data warehouse as a target data source.
7. The method of claim 1, wherein the data query comprises a first query; the querying the target data source by the data querying method to obtain a querying result corresponding to the target interface includes:
when the interface type is a database type, determining an initial query parameter in the data query request, and taking a standard format of the target interface identifier as an auxiliary parameter;
determining a database query format corresponding to the database type, and splicing the initial query parameter and the auxiliary parameter according to the database query format to obtain a target query parameter;
and querying from the target data source through the target query parameter to obtain a query result corresponding to the target interface.
8. The method of claim 1, wherein the data query means comprises a second query means; the target data source is deployed in a target container; the querying the target data source in the data querying manner to obtain a querying result corresponding to the target interface includes:
when the interface type is a special script type, acquiring a target protocol, and establishing communication with the target container through the target protocol;
performing trigger operation on the target container; the triggering operation is used for triggering the target container to query the target data source to obtain a query result corresponding to the target interface;
and acquiring the query result fed back by the target container.
9. The method according to claim 1, wherein after obtaining the query result corresponding to the target interface, the method further comprises:
determining a target field table corresponding to the target interface identifier; the target field table includes cache information;
recording the process of calling the target interface and the query result to obtain a current recording result, and judging whether the current recording result needs to be cached according to the caching information;
if not, updating the call record according to a preset recording period and the current recording result to obtain a new call record.
10. A data query apparatus, characterized in that the apparatus comprises:
the query request acquisition module is used for acquiring a data query request and determining a data identifier corresponding to the data query request; the data identification comprises a target interface identification needing to be called;
the query mode determining module is used for determining a calling record of a target interface corresponding to the target interface identifier and determining a target data source corresponding to the target interface according to preset configuration information; when the calling record represents that the target interface is called for the first time, determining an interface type corresponding to the target interface, and determining a data query mode according to the interface type;
and the query result determining module is used for calling the target interface to query the target data source in the data query mode to obtain a query result corresponding to the target interface.
11. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor realizes the steps of the method of any one of claims 1 to 9 when executing the computer program.
12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211576146.1A CN115658794B (en) | 2022-12-09 | 2022-12-09 | Data query method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211576146.1A CN115658794B (en) | 2022-12-09 | 2022-12-09 | Data query method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115658794A true CN115658794A (en) | 2023-01-31 |
| CN115658794B CN115658794B (en) | 2023-05-12 |
Family
ID=85019973
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211576146.1A Active CN115658794B (en) | 2022-12-09 | 2022-12-09 | Data query method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115658794B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116383083A (en) * | 2023-04-23 | 2023-07-04 | 中航信移动科技有限公司 | Multi-interface connection-based abnormal data source determining method and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111026564A (en) * | 2019-11-20 | 2020-04-17 | 中国航空工业集团公司西安航空计算技术研究所 | Naming service processing method and system |
| CN111563125A (en) * | 2020-05-08 | 2020-08-21 | 中国工商银行股份有限公司 | Data storage system, data query method and device |
| CN111988387A (en) * | 2020-08-11 | 2020-11-24 | 北京达佳互联信息技术有限公司 | Interface request processing method, device, server, equipment and storage medium |
| CN114547080A (en) * | 2022-02-24 | 2022-05-27 | 重庆紫光华山智安科技有限公司 | Data query method, system, electronic device and storage medium |
| CN115455103A (en) * | 2022-10-20 | 2022-12-09 | 广州明动软件股份有限公司 | Dynamic query system and method based on dynamic interface engine |
-
2022
- 2022-12-09 CN CN202211576146.1A patent/CN115658794B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111026564A (en) * | 2019-11-20 | 2020-04-17 | 中国航空工业集团公司西安航空计算技术研究所 | Naming service processing method and system |
| CN111563125A (en) * | 2020-05-08 | 2020-08-21 | 中国工商银行股份有限公司 | Data storage system, data query method and device |
| CN111988387A (en) * | 2020-08-11 | 2020-11-24 | 北京达佳互联信息技术有限公司 | Interface request processing method, device, server, equipment and storage medium |
| CN114547080A (en) * | 2022-02-24 | 2022-05-27 | 重庆紫光华山智安科技有限公司 | Data query method, system, electronic device and storage medium |
| CN115455103A (en) * | 2022-10-20 | 2022-12-09 | 广州明动软件股份有限公司 | Dynamic query system and method based on dynamic interface engine |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116383083A (en) * | 2023-04-23 | 2023-07-04 | 中航信移动科技有限公司 | Multi-interface connection-based abnormal data source determining method and storage medium |
| CN116383083B (en) * | 2023-04-23 | 2024-01-12 | 中航信移动科技有限公司 | Multi-interface connection-based abnormal data source determining method and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115658794B (en) | 2023-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11902313B2 (en) | Dynamic hierarchical tagging system and method | |
| US20220311794A1 (en) | Monitoring a software development pipeline | |
| CN111177252A (en) | Service data processing method and device | |
| US20220303295A1 (en) | Annotating changes in software across computing environments | |
| US11720825B2 (en) | Framework for multi-tenant data science experiments at-scale | |
| CN113254534A (en) | Data synchronization method and device and computer storage medium | |
| CN110659259A (en) | Database migration method, server and computer storage medium | |
| CN112860953A (en) | Data importing method, device, equipment and storage medium of graph database | |
| CN115658794B (en) | Data query method, device, computer equipment and storage medium | |
| CN116541372A (en) | Data asset management method and system | |
| CN115238247A (en) | Data processing method based on zero trust data access control system | |
| CN110941632A (en) | Database auditing method, device and equipment | |
| CN113836237A (en) | Method and device for auditing data operation of database | |
| CN116644250A (en) | Page detection method, page detection device, computer equipment and storage medium | |
| CN112835863A (en) | Processing method and processing device of operation log | |
| US20220075769A1 (en) | Logfile collection and consolidation | |
| US11782938B2 (en) | Data profiling and monitoring | |
| CN113779132A (en) | Data import method and device, computer equipment and storage medium | |
| CN116684282B (en) | Method and device for initializing newly-added cloud server and computer equipment | |
| WO2019242112A1 (en) | Method and apparatus for obtaining audit field information, computer device, and storage medium | |
| CN110544042B (en) | Book management method and device based on blockchain network | |
| CN117195201A (en) | Terminal application monitoring method and device, computer equipment and storage medium | |
| CN116756022A (en) | Data preparation method, device, computer equipment and storage medium | |
| CN117312307A (en) | Service data processing method, device, computer equipment and storage medium | |
| CN116880927A (en) | Rule management method, 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |