CN116089462A

CN116089462A - Data query method, device, electronic equipment and storage medium

Info

Publication number: CN116089462A
Application number: CN202211699906.8A
Authority: CN
Inventors: 谭锦志; 邱炜伟; 施德强; 尚璇; 李吉明
Original assignee: Hangzhou Qulian Technology Co Ltd
Current assignee: Hangzhou Qulian Technology Co Ltd
Priority date: 2022-12-28
Filing date: 2022-12-28
Publication date: 2023-05-09

Abstract

The application relates to a data query method, a data query device, electronic equipment and a storage medium, which are applied to the technical field of computers, wherein the method comprises the following steps: acquiring a query request, wherein the query request carries query data; analyzing the query data in the query request to obtain query parameters; determining a matching target orm frame with the database to be queried; the database to be queried is queried based on the query parameters and the target orm framework. In order to solve the problems that in the prior art, the interface is modified and newly added, repeated query writing business logic is possibly needed, and the maintained documents and codes are increasingly bulked.

Description

Data query method, device, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a data query method, a data query device, an electronic device, and a storage medium.

Background

The data of the client may need to be screened or ordered differently in different business scenarios. To meet these demands, the backend needs to meet the conditions of the service by developing new interfaces or adding new fields. As the required service is changed, the interface needs to be modified and added, and repeated service logic for writing the query may be needed, so that the maintained document and code are more and more bulky.

Disclosure of Invention

The application provides a data query method, a data query device, electronic equipment and a storage medium, which are used for solving the problems that in the prior art, repeated query writing business logic is possibly needed when a port is modified and added, and maintained documents and codes are increasingly and bloated.

In a first aspect, an embodiment of the present application provides a data query method, including:

acquiring a query request, wherein the query request carries query data;

analyzing the query data in the query request to obtain query parameters;

determining a matching target orm frame with the database to be queried;

the database to be queried is queried based on the query parameters and the target orm framework.

Optionally, the parsing the query data in the query request to obtain query parameters includes:

determining inquiry matters in the inquiry data;

acquiring initial parameters corresponding to each inquiry item;

the query parameters are determined based on the initial parameters.

Optionally, the determining the query parameter based on the initial parameter includes:

judging whether the initial parameter is empty or not under the condition that the query item is a query range, if so, setting the initial parameter and a preset parameter to obtain the query parameter; if not, determining the initial parameters as the query parameters;

and under the condition that the query item is query content, extracting a key field in the initial parameter, and determining the key field as the query parameter.

Optionally, after extracting the key field in the initial parameter, the method further includes:

judging whether the key field is consistent with a target field in the database to be queried;

and if the key fields are inconsistent, mapping the key fields into the target fields.

Optionally, the key fields include a query field, a filtering condition, and a query condition.

Optionally, the determining a matching target orm framework with the database to be queried includes:

obtaining a target database type of the database to be queried;

and determining a target orm frame corresponding to the target database class based on the corresponding relation between the pre-established database type and the orm frame.

Optionally, the querying the database to be queried based on the query parameters and the target orm framework includes:

converting the query parameters into target grammar recognizable by the target orm framework;

the target orm framework is invoked based on the target grammar to query the database to be queried through the target orm framework.

In a second aspect, an embodiment of the present application provides a data query apparatus, including:

the acquisition module is used for acquiring a query request, wherein the query request carries query data;

the analysis module is used for analyzing the query data in the query request to obtain query parameters;

a determining module for determining a matching target orm frame with the database to be queried;

and the query module is used for querying the database to be queried based on the query parameters and the target orm framework.

In a third aspect, an embodiment of the present application provides an electronic device, including: the device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;

the memory is used for storing a computer program;

the processor is configured to execute the program stored in the memory, and implement the data query method according to the first aspect.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program, where the computer program implements the data query method according to the first aspect when executed by a processor.

Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages: according to the method provided by the embodiment of the application, the query request is obtained, and the query request carries query data; analyzing the query data in the query request to obtain query parameters; determining a matching target orm frame with the database to be queried; the database to be queried is queried based on the query parameters and the target orm framework. In this way, query parameters in the query request are analyzed, and the target orm framework matched with the database to be queried is utilized, and because the determined target orm framework is matched with the database to be queried, the target orm framework can query the database to be queried by utilizing the query parameters, so that query of the database can be realized without re-writing query business logic, and document and code swelling is avoided.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.

In order to more clearly illustrate the embodiments of the invention or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, and it will be obvious to a person skilled in the art that other drawings can be obtained from these drawings without inventive effort.

Fig. 1 is an application scenario diagram of a data query method according to an embodiment of the present application;

FIG. 2 is a flowchart of a data query method according to an embodiment of the present disclosure;

FIG. 3 is a flowchart of a data query method according to another embodiment of the present application;

FIG. 4 is a block diagram of a data query device according to an embodiment of the present disclosure;

fig. 5 is a block diagram of an electronic device according to an embodiment of the present application.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present application based on the embodiments herein.

Before describing embodiments of the present invention in further detail, the terms and terminology involved in the embodiments of the present invention will be described, and the terms and terminology involved in the embodiments of the present invention will be used in the following explanation.

An object relational mapping (Object Relational Mapping, ORM for short) that solves the problem of data interaction between objects and relational databases.

The structured query language (Structured Query Language, abbreviated SQL) is a computer language used to store, retrieve, and modify data stored in relational databases.

An embodiment of the application provides a data query method. Alternatively, in the embodiment of the present application, the above-described data query method may be applied to a hardware environment configured by the terminal 101 and the server 102 as shown in fig. 1. As shown in fig. 1, the server 102 is connected to the terminal 101 through a network, which may be used to provide services (such as a query service, an application service, etc.) to the terminal or a client installed on the terminal, and a database may be provided on the server or independent of the server, for providing data storage services to the server 102, where the network includes, but is not limited to: the terminal 101 is not limited to a PC, a mobile phone, a tablet computer, or the like.

The data query method in the embodiment of the present application may be executed by the server 102, may be executed by the terminal 101, or may be executed by both the server 102 and the terminal 101. The terminal 101 may execute the data query method according to the embodiment of the present application, or may be executed by a client installed thereon.

Taking a terminal to execute the data query method according to the embodiment of the present application as an example, fig. 2 is a schematic flow chart of an alternative data query method according to the embodiment of the present application, as shown in fig. 2, a flow of the method may include the following steps:

step 201, obtaining a query request, where the query request carries query data.

In some embodiments, the query request may be triggered after the user enters search content within the search box. After obtaining the search content, the terminal can convert the search content into query data according to a format which can be identified by the computer. For example, the search content input by the user is a blockchain named hyperchain, and after being converted into query data, the search content can be name < eq > hyperchain.

And 202, analyzing the query data in the query request to obtain query parameters.

In some embodiments, after the query data is obtained, key information for query, that is, query parameters, in the query data may be determined by parsing the query data, so that a database to be queried is conveniently queried by using the query parameters.

In an alternative embodiment, the parsing the query data in the query request to obtain query parameters includes:

determining inquiry matters in the inquiry data;

acquiring initial parameters corresponding to each inquiry item;

the query parameters are determined based on the initial parameters.

In some embodiments, the query terms may be set by the developer according to actual needs. Illustratively, the query issue may include, but is not limited to, a start page (start), a page size (size), a sort condition (sort), and a required column (select).

Wherein the ordering condition filters the return parameter content, the basic grammar is composed of field < filter relation > conditions, such as name < eq > hyperchain.

In an alternative embodiment, determining the query parameter based on the initial parameter includes:

In some embodiments, the query scope may be the starting page and page size described above. The query content may be the ordering condition and the required column described above.

Illustratively, it is assumed that the query data carried by one http request (i.e., query request) is as follows:

start＝1&size＝10&filter＝name<eq>hyperchain,type<in>(1@2)&sort＝createTime desc

specifically, the start and size are checked first during analysis, and if they are empty, the default value is set. In the above example, the initial parameter of start is 1, and the initial parameter of size is 10, so that it is not necessary to set to a default value.

Resolving the sort=createtime desc into a sequence and a sequence relation, and resolving that the select is not null into a required sequence; analyzing the filter grammar, separating the character string into name < eq > hyperchain and type < in > (1@2), further adopting regular matching to judge whether the format is in line, and capturing the corresponding query parameters through the regular matching if the format is in line.

In the above example, after regular matching, the obtained data are shown in table 1 below:

TABLE 1

Column of	Screening relationships	Conditions (conditions)
			name	Equal to	hyperchain
type	in query	1@2

Wherein, the key fields comprise a query field, a screening condition and a query condition. In the above example, the query field includes name and type, the filter term includes equal-sum-in queries, and the query term includes hyperchain and 1@2.

In an optional embodiment, after the extracting the key field in the initial parameter, the method further includes:

In some embodiments, each column item after the filter text parsing is passed through a custom set of column interceptors. Through a column filtering interceptor, which fields to filter can be decided; through a column mapping interceptor, the database and front-end inconsistent fields and values can be mapped, such as when columns in the database are nickname, name can be mapped to nickname, and filtered values 1@2 can be mapped to available, unable for in-query.

Step 203, determining a matching target orm frame with the database to be queried.

In some embodiments, the data structures of the data stored in different databases are different, so that after the query parameters are obtained, the database to be queried may not be queried directly through the query parameters. Thus, a target orm frame capable of matching the database to be queried is determined, and the database to be queried is called through the target orm frame, so that a bridge between the target orm frame and the database to be queried is built.

In an alternative embodiment, the determining a matching target orm framework with the database to be queried includes:

obtaining a target database type of the database to be queried;

In some embodiments, the orm framework that it can match is also different for different databases to be queried. Based on this, by acquiring the target database type of the database to be queried, the data storage formats corresponding to the different database types are different, so orm frames matched with each database type can be preset, and the corresponding relationship between the orm frames and the orm frames can be established, so that after the target database type is acquired, the target orm frame can be determined based on the corresponding relationship.

And 204, querying the database to be queried based on the query parameters and the target orm framework.

In some embodiments, the target orm framework can be utilized to call the database to be queried through the determined query parameters and the target orm framework so as to query the data in the database corresponding to the query parameters.

In an alternative embodiment, querying the database to be queried based on the query parameters and the target orm framework includes:

In some embodiments, different orm frames may be selected in the project according to different service scenarios, so that the parsed parameters need to be converted into corresponding orm frame grammars.

The bottom layer difference of the database is realized by a orm framework, the configurator calls orm the method of the framework, and the analyzed query parameters are used as parameter calls. For example, in the configurator, the start, the size may change limit (start-1, size×start), the syntax after the filter parsing is directly converted into the corresponding where, in condition, and the related business logic such as where the where condition composed of the authentication parameters may be inserted in the configurator.

In a specific embodiment, the data query method of the present application, the data to be queried is sql, and the method specifically includes:

the first, front end carries request data start, size, filter, sort, select via a Web request.

And secondly, after the rear end receives the request, the parser performs checksum parsing on the filter and the sort grammar.

Specifically, the query parameter analysis process includes: a parameter parser may be provided that performs a check, parse, and filter on the request parameters to complete paging, and filter the extraction of the ordering condition.

Referring to fig. 3, the parser obtains the request data, first determines whether the paging data in the query range is empty, if yes, sets a default value, if not, determines whether the query content accords with the regular matching, if not, returns an error, and if so, parses the query content. And inputs the fields to the column interceptor to determine the fields to be screened through the column interceptor and to determine the relationship of the silver snakes, thereby completing the parsing.

Third, different oxrm's are converted by the generator according to backend integration.

Fourth, executing oxrm converts the condition into native sql execution.

Based on the data query method, the front end can quickly iterate the product, the back end does not need to be adjusted according to the query condition of the front end, and SQL resource screening can be completed through the unified field of the API. Codes can be reduced, repeated paging screening and sorting work is greatly reduced, and a part of inquiry functions are opened to the front end. The query process can be safer, the column mapping relation can be established, and the quick screening field can be determined. Compatibility is improved, and implementation can be customized to be compatible with different databases and different ORM frameworks.

Based on the same conception, the embodiment of the present application provides a data query device, and the specific implementation of the device may be referred to the description of the embodiment of the method, and the repetition is omitted, as shown in fig. 4, where the device mainly includes:

an obtaining module 401, configured to obtain a query request, where the query request carries query data;

the parsing module 402 is configured to parse the query data in the query request to obtain a query parameter;

a determining module 403 for determining a matching target orm frame with the database to be queried;

a query module 404, configured to query the database to be queried based on the query parameters and the target orm framework.

Based on the same concept, an embodiment of the present application provides an electronic device, as shown in fig. 5, where the electronic device mainly includes: processor 501, communication interface 502, memory 503, and communication bus 504, wherein processor 501, communication interface 502, and memory 503 communicate with each other via communication bus 504. The memory 503 stores a program executable by the processor 501, and the processor 501 executes the program stored in the memory 503 to implement the following steps:

acquiring a query request, wherein the query request carries query data;

analyzing the query data in the query request to obtain query parameters;

determining a matching target orm frame with the database to be queried;

The communication bus 504 mentioned in the above electronic device may be a peripheral component interconnect standard (Peripheral Component Interconnect, abbreviated to PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated to EISA) bus, or the like. The communication bus 504 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 5, but not only one bus or one type of bus.

The communication interface 502 is used for communication between the electronic device and other devices described above.

The memory 503 may include a random access memory (Random Access Memory, simply referred to as RAM) or may include a non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor 501.

The processor 501 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), a digital signal processor (Digital Signal Processing, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a Field programmable gate array (Field-Programmable Gate Array, FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware components.

In yet another embodiment of the present application, there is also provided a computer-readable storage medium having stored therein a computer program which, when run on a computer, causes the computer to perform the data query method described in the above embodiments.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with the embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, by a wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, microwave, etc.) means from one website, computer, server, or data center to another. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape, etc.), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk), etc.

It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing is only a specific embodiment of the invention to enable those skilled in the art to understand or practice the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of querying data, comprising:

acquiring a query request, wherein the query request carries query data;

analyzing the query data in the query request to obtain query parameters;

determining a matching target orm frame with the database to be queried;

2. The data query method according to claim 1, wherein the parsing the query data in the query request to obtain query parameters includes:

determining inquiry matters in the inquiry data;

acquiring initial parameters corresponding to each inquiry item;

the query parameters are determined based on the initial parameters.

3. The data query method of claim 2, wherein said determining said query parameters based on said initial parameters comprises:

4. The data query method of claim 3, wherein the extracting key fields in the initial parameters further comprises:

5. The data query method of claim 3, wherein the key fields include a query field, a filter condition, and a query condition.

6. The data query method of claim 1, wherein the determining a matching target orm framework with a database to be queried comprises:

obtaining a target database type of the database to be queried;

7. The data query method of claim 1, wherein the querying the database to be queried based on the query parameters and the target orm framework comprises:

8. A data query device, comprising:

9. An electronic device, comprising: the device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;

the memory is used for storing a computer program;

the processor is configured to execute a program stored in the memory, and implement the data query method of any one of claims 1 to 7.

10. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the data query method of any of claims 1-7.