Disclosure of Invention
In view of the above problems, the present application provides a technical solution for automatically generating an interface based on a specific programming language, so as to solve the technical problems of complicated operation, low efficiency and the like of the existing code testing method based on a database.
To achieve the above object, in a first aspect, the present application provides a method for automatically generating an interface based on a specific programming language, the specific programming language including an SQL language or a Groovy language, the method comprising:
displaying an interface configuration interface at the front end, wherein the interface configuration interface comprises a plurality of input columns, different input columns are used for acquiring different input parameter information, and the input parameter information comprises interface identification information, interface names, related input sentences of a specific programming language and data source types;
after receiving a confirmation instruction of generating an interface, issuing all acquired input parameter information in a rest interface mode, acquiring related input sentences of the specific programming language, and packaging the related input sentences into json data and sending the json data to a rear end;
the back-end call parser parses the json data to obtain related input sentences, verifies the related input sentences based on the sentence specification of the specific programming language, and generates corresponding SQL query sentences based on the related input sentences after verification is passed;
executing the SQL query statement, acquiring a query result data set from a data source corresponding to the data source type, and displaying the query result data set at the front end.
Further, the verifying the related input sentence based on the sentence specification of the specific programming language includes:
and performing lexical analysis, grammar analysis and semantic analysis on the related input sentences to check whether the related input sentences accord with lexical specifications, grammar specifications and semantic specifications.
Further, before the front end displays the query result data set, the method further comprises: performing format conversion on the query result data set, and converting the query result data set into a preset format;
displaying the query result dataset at the front end includes: and displaying the query result data set subjected to format conversion at the front end.
Further, the method further comprises:
if the result of checking the related input statement based on the statement specification of the specific programming language is that the check is not passed, a result of executing error is returned at the front end, and prompt information is sent out.
Further, the method further comprises:
after the rest interfaces are distributed, the front end can access the rest interfaces after receiving the interface access instructions, and the interface access instructions are triggered after the user inputs the ip ports and the interface identification information.
Further, the related input statement includes condition information required by the SQL statement, and the condition information includes a table name, a field name and a limiting condition.
Further, the input fields further comprise a parameter input field, the parameter input field comprises a first parameter input field and a second parameter input field, the first parameter input field is used for receiving expansion parameters input by a user, and the second parameter input field is used for receiving paging parameters input by the user.
Further, the method further comprises:
and checking the identity of the user, and displaying the interface configuration interface at the front end after the identity check is passed.
In a second aspect, the present application provides a computer readable storage medium having stored thereon a computer program which when executed by a processor implements a method of automatically generating an interface based on a specific programming language as described in the first aspect of the present application.
In a third aspect, the present application provides an electronic device having stored thereon a computer program comprising a processor and a storage medium having stored thereon a computer program which, when executed by the processor, implements a method of automatically generating an interface based on a specific programming language as described in the first aspect of the present application
In contrast to the prior art, the method, medium and device for automatically generating an interface based on a specific programming language in the above technical solution, the method includes: displaying an interface configuration interface at the front end, wherein the interface configuration interface comprises a plurality of input columns, and different input columns are used for acquiring different input parameter information; after receiving a confirmation instruction of generating an interface, issuing all acquired input parameter information in a rest interface mode, acquiring related input sentences of the specific programming language, and packaging the related input sentences into json data and sending the json data to a rear end; the back-end call parser parses the json data to obtain related input sentences, verifies the related input sentences based on the sentence specification of the specific programming language, and generates corresponding SQL query sentences based on the related input sentences after verification is passed; executing the SQL query statement, acquiring a query result data set from a data source corresponding to the data source type, and displaying the query result data set at the front end. According to the method, the interface can be automatically generated according to the database structure or other conditions, so that the time and energy for manually writing the interface are saved, the execution result of related written input sentences can be presented in real time, the modification and debugging of research personnel are facilitated, and the research and development efficiency is improved.
The foregoing summary is merely an overview of the present application, and is provided to enable one of ordinary skill in the art to make more clear the present application and to be practiced according to the teachings of the present application and to make more readily understood the above-described and other objects, features and advantages of the present application, as well as by reference to the following detailed description and accompanying drawings.
Detailed Description
In order to describe the possible application scenarios, technical principles, practical embodiments, and the like of the present application in detail, the following description is made with reference to the specific embodiments and the accompanying drawings. The embodiments described herein are only used to more clearly illustrate the technical solutions of the present application, and are therefore only used as examples and are not intended to limit the scope of protection of the present application.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of the phrase "in various places in the specification are not necessarily all referring to the same embodiment, nor are they particularly limited to independence or relevance from other embodiments. In principle, in the present application, as long as there is no technical contradiction or conflict, the technical features mentioned in the embodiments may be combined in any manner to form a corresponding implementable technical solution.
Unless defined otherwise, technical terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present application pertains; the use of related terms herein is for the description of specific embodiments only and is not intended to limit the present application.
In the description of the present application, the term "and/or" is a representation for describing a logical relationship between objects, which means that there may be three relationships, e.g., a and/or B, representing: there are three cases, a, B, and both a and B. In addition, the character "/" herein generally indicates that the front-to-back associated object is an "or" logical relationship.
In this application, terms such as "first" and "second" are used merely to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual number, order, or sequence of such entities or operations.
Without further limitation, the use of the terms "comprising," "including," "having," or other like open-ended terms in this application are intended to cover a non-exclusive inclusion, such that a process, method, or article of manufacture that comprises a list of elements does not include additional elements in the process, method, or article of manufacture, but may include other elements not expressly listed or inherent to such process, method, or article of manufacture.
As in the understanding of the "examination guideline," the expressions "greater than", "less than", "exceeding", and the like are understood to exclude the present number in this application; the expressions "above", "below", "within" and the like are understood to include this number. Furthermore, in the description of the embodiments of the present application, the meaning of "a plurality of" is two or more (including two), and similarly, the expression "a plurality of" is also to be understood as such, for example, "a plurality of groups", "a plurality of" and the like, unless specifically defined otherwise.
In the description of the embodiments of the present application, spatially relative terms such as "center," "longitudinal," "transverse," "length," "width," "thickness," "up," "down," "front," "back," "left," "right," "vertical," "horizontal," "vertical," "top," "bottom," "inner," "outer," "clockwise," "counter-clockwise," "axial," "radial," "circumferential," etc., are used herein as terms of orientation or positional relationship based on the specific embodiments or figures, and are merely for convenience of description of the specific embodiments of the present application or ease of understanding of the reader, and do not indicate or imply that the devices or components referred to must have a particular position, a particular orientation, or be configured or operated in a particular orientation, and therefore are not to be construed as limiting of the embodiments of the present application.
Unless specifically stated or limited otherwise, in the description of the embodiments of the present application, the terms "mounted," "connected," "affixed," "disposed," and the like are to be construed broadly. For example, the "connection" may be a fixed connection, a detachable connection, or an integral arrangement; the device can be mechanically connected, electrically connected and communicated; it can be directly connected or indirectly connected through an intermediate medium; which may be a communication between two elements or an interaction between two elements. The specific meanings of the above terms in the embodiments of the present application can be understood by those skilled in the art to which the present application pertains according to the specific circumstances.
As shown in fig. 1, the present application provides a method for automatically generating an interface based on a specific programming language, wherein the specific programming language includes an SQL language or a Groovy language, and the method includes:
firstly, step S101 is carried out, an interface configuration interface is displayed at the front end, the interface configuration interface comprises a plurality of input columns, different input columns are used for acquiring different input parameter information, and the input parameter information comprises interface identification information, interface names, related input sentences of a specific programming language and data source types;
step S102 is carried out, after a confirmation instruction of generating an interface is received, all acquired input parameter information is issued in a rest interface mode, and relevant input sentences of the specific programming language are acquired and packaged into json data and sent to the rear end;
then entering a step S103, and calling a parser at the rear end to parse the json data to obtain related input sentences, checking the related input sentences based on the sentence specification of the specific programming language, and generating corresponding SQL query sentences based on the related input sentences after the verification is passed;
and then, step S104 is carried out to execute the SQL query statement, a query result data set is obtained from the data source corresponding to the data source type, and the query result data set is displayed at the front end.
According to the method, the interface can be automatically generated according to the database structure or other conditions, so that the time and energy for manually writing the interface are saved, the execution result of related written input sentences can be presented in real time, the modification and debugging of research personnel are facilitated, and the research and development efficiency is improved.
In some embodiments, the verifying the relevant input statement based on the statement specification of the particular programming language includes: and performing lexical analysis, grammar analysis and semantic analysis on the related input sentences to check whether the related input sentences accord with lexical specifications, grammar specifications and semantic specifications. Specifically, taking a sentence input by a user as an example of an SQL sentence, the lexical analysis refers to decomposing the SQL sentence input by the user into a series of lexical units, such as keywords, identifiers, operators, constants, and the like. The grammar analysis refers to combining lexical units into a grammar tree according to SQL grammar rules, and simultaneously verifying whether grammar is correct. The semantic analysis refers to semantic analysis of a syntax tree, verification of whether table names, field names and the like exist, processing of expressions, determination of an execution plan and the like. An execution plan may then be generated based on the results of the semantic analysis.
In some embodiments, as shown in fig. 2, before the front-end presents the query result dataset, further comprising: step S201, format conversion is carried out on the query result data set, and the query result data set is converted into a preset format; displaying the query result dataset at the front end includes: step S202 presents the format-converted query result dataset at the front end. The preset format may be json format. By the scheme, the format of the returned query result data set displayed at the front end can be ensured to be uniform and more standard.
In certain embodiments, the method further comprises: if the result of checking the related input statement based on the statement specification of the specific programming language is that the check is not passed, a result of executing error is returned at the front end, and prompt information is sent out.
In short, whether the related input statement accords with the corresponding writing specification or not, whether the related input statement is correct or not can be presented in real time, so that online debugging of research personnel is facilitated, and code modification and debugging efficiency is improved. The prompt information can be an acoustic prompt, a luminous prompt, a vibration prompt, or a text, a graphic prompt and the like on a display interface of the display device.
In certain embodiments, the method further comprises: after the rest interfaces are distributed, the front end can access the rest interfaces after receiving the interface access instructions, and the interface access instructions are triggered after the user inputs the ip ports and the interface identification information.
The rest (Representational State Transfer) interface is a web application programming interface design style that uses standardized rules and the HTTP-based protocol. It is a lightweight, flexible, scalable way to communicate between clients and servers.
Core principles of REST interface design include: (1) Resources: abstracting entities or data on a server as resources, each resource having a unique identifier (URI); (2) unified interface (Uniform Interface): operating and managing resources by using standard HTTP methods (GET, POST, PUT, DELETE, etc.); (3) Stateless (Stateless): each request contains enough information to complete processing by the server, and the server does not need to save the state of the client; (4) Client-server separation (Client-Server Separation): the point of interest separation between the client and the server allows them to evolve independently.
REST interfaces typically use JSON or XML formats to transfer data and can accommodate a variety of different clients, including web browsers, mobile applications, etc. By following the design principle of REST interface, the developer can create simple, reliable and extensible Web service, so that different application programs can perform seamless communication and data exchange through HTTP protocol.
In some embodiments, the related input statement includes condition information required for an SQL statement, the condition information including a table name, a field name, and a qualifying condition. For example, select name, age from user where username like '% # (KEYWORD)%' limit 5 can be written by looking up the name and age fields of the user list and returning only the first 5. By inputting the condition information required by different SQL sentences, the result meeting the corresponding condition information can be obtained from the corresponding data source.
In some embodiments, the input fields further include a parameter input field, the parameter input field including a first parameter input field for receiving an extended parameter entered by a user and a second parameter input field for receiving a paging parameter entered by the user.
Extension Parameter (Bind Parameter): an extension parameter is a mechanism for dynamically passing values in SQL statements. By using the extension parameter, the actual parameter value can be separated from the SQL statement, so that the safety and reusability of the code are improved. Typically, the extension parameters are represented in SQL statements by placeholders (e.g., name) to which the actual parameter values are then bound prior to execution of the SQL statement. The extension parameters can effectively prevent SQL injection attacks and support parameter reuse.
Paging parameter (Pagination Parameter): paging parameters refer to operations that partition the query result into multiple smaller pages when processing large amounts of data. The number of records returned per page and the number of pages requested may be specified by the paging parameter to display the paging data in the front-end application. Paging parameters typically include: page size (number of records per page) and page number (currently requested page number). In an SQL query, the paging function may be implemented using LIMIT and OFFSET statements, with LIMIT being used to LIMIT the number of records per page, and OFFSET being used to specify from which record to start.
For example, in MySQL, LIMIT and OFFSET are used to implement a paged query:
SELECT*FROM customers LIMIT 10OFFSET 20；
the query will return 10 records starting from record 21 for data presentation on page 3.
By using the expansion parameters and the paging parameters, the data in the database can be easily queried and operated, and the result can be flexibly controlled and displayed according to the requirement.
In certain embodiments, the method further comprises: and checking the identity of the user, and displaying the interface configuration interface at the front end after the identity check is passed. The verification of the identity of the user may be performed by checking an account number, a password, biometric information, a verification code, etc. input by the user. By the scheme, only the user passing the identity verification has authority to input information in the input field of the display interface configuration interface, so that the programming safety can be effectively improved.
In the following detailed description of the method related to the present application in combination with the actual application scenario, when the interface configuration interface is generated, the system needs to perform the following configuration operations:
(1) Designing a database schema: a database schema suitable for the method is designed and created, the tables and columns are determined, and the appropriate associations are determined.
(2) Writing SQL queries or Groovy methods: queries are written using the SQL language or the Groovy method to retrieve data from the database, generate definitions of API interfaces from the database table structure, and write logic to generate the API interfaces using the dynamic language properties of the Groovy.
(3) Creating an API endpoint: according to the application architecture, an API endpoint (e.g., REST API) is created that allows the application to communicate with the database via HTTP requests. An interactable API document is generated by using the Swagger design, an automated tool that builds a documented RESTful API.
(4) Writing back-end codes: back-end code is written to handle API requests of the application. And analyzing the request parameters, executing the corresponding SQL query or the Groovy method, and returning the result to the application program.
(5) Integrating Spring Security: user authentication and API access rights control are implemented using Spring Security to ensure proper Security and rights control when accessing the database.
The technical schemes related to the method are far more than the above, the technical schemes are integrated into the method, and the visual interface is supported to write SQL language or Groovy method, and the visual interface test and the result check after the interface is generated, etc.
In a specific use process, after a user logs in through identity information, the user enters into interface configuration in development and debugging, clicks a newly-added button, and displays the interface configuration interface. An exemplary schematic of the interface configuration interface is shown in fig. 3.
In the interface configuration interface shown, the information in the input field of the interface configuration includes: queryCode (interface unique identifier), name, SQL (SQL language), groovy, data source (support MySQL, oracle, es, etc.), extParam (extension parameters), pagequery model (paging parameters), etc.
Specifically, the information of each input field may be set by:
(1) The corresponding SQL is written with the conditions required by SQL, such as querying the name and age fields of the user list and returning only the first 5, the select name, age from user where username like '% # (KEYWORD)%' limit 5 can be written.
(2) For some more complex business logics, the page is also provided with a form for providing the Groovy, and a background can correspondingly analyze the Groovy method to solve the pain point that SQL can not meet business requirements.
(3) And selecting a data source on the page (namely an interface configuration interface), and selecting the data source which needs to be queried by the interface.
(4) Additional parameters and paging parameters are also provided on the page, not necessarily filled, and filled when paging is required.
(5) Each interface has a unique queryCode, and after the storage, the results returned by SQL or Groovy can be checked. After the storage, the method can be released in the form of rest interface by selecting one-key release. The later front end can be accessed through the ip port and the queryCode.
(6) And after clicking, storing and releasing the request, packaging the data into JSON data, transmitting the JSON data to the back end, and acquiring SQL or Groovy sentences by the back end mainly according to the queryCode, and carrying out corresponding analysis. For example, an SQL parser, an open source SQL parser library, such as ANTLR, JSQLParser, is utilized to perform secondary development on the basis, so that SQL sentences input by a user can be parsed and key information, such as table names, field names, conditions and the like, in the SQL sentences can be extracted.
(7) According to the information obtained by analysis, dynamically generating a corresponding SQL query statement, such as splicing front-end request parameters; executing query operation by using the generated SQL statement, and acquiring a result set; formatting the result set, such as converting the result set into a common format such as JSON; and returning the formatted result to the user to complete the automatic interface generation process.
(8) And after the operation is finished, testing is carried out, and the obtained mode is used for obtaining the returned result of the SQL or the Groovy, so that whether the result is correct or not is displayed. As shown in fig. 4, the quantitative information of SQL (SELECT ZS, BJSL, WBJSL, LASTZS, LASTBJSL, LASTWBJSL FROM dusl) statistics is shown.
In a second aspect, the present invention also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor implements a method of automatically generating an interface based on a specific programming language according to the first aspect of the present invention.
Wherein the computer readable storage medium may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory.
The non-volatile Memory may be a Read Only Memory (ROM), a programmable Read Only Memory (PROM, programmable Read Only Memory), an erasable programmable Read Only Memory (EPROM, erasable Programmable Read Only Memory), an electrically erasable programmable Read Only Memory (EEPROM, electrically Erasable Programmable Read Only Memory), a magnetic random access Memory (FRAM, ferromagnetic random access Memory), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical disk, or a compact disk Read Only (CD ROM, compact Disc Read Only Memory); the magnetic surface memory may be a disk memory or a tape memory.
The volatile memory may be random access memory (RAM, random Access Memory), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (SRAM, static Random Access Memory), synchronous static random access memory (SSRAM, synchronous Static Random Access Memory), dynamic random access memory (DRAM, dynamic Random Access Memory), synchronous dynamic random access memory (SDRAM, synchronous Dynamic Random Access Memory), double data rate synchronous dynamic random access memory (ddr SDRAM, double Data Rate Synchronous Dynamic Random Access Memory), enhanced synchronous dynamic random access memory (ESDRAM, enhanced Synchronous Dynamic Random Access Memory), synchronous link dynamic random access memory (SLDRAM, syncLink Dynamic Random Access Memory), direct memory bus random access memory (DRRAM, direct Rambus Random Access Memory). The computer-readable storage media described in connection with the embodiments of the present invention are intended to comprise these and any other suitable types of memory.
As shown in fig. 5, in a third aspect, the present invention provides an electronic device 10, including a processor 101 and a storage medium 102, the storage medium having stored thereon a computer program which, when executed by the processor, implements a method for automatically generating an interface based on a specific programming language according to the first aspect of the present invention.
In some embodiments, the processor may be implemented in software, hardware, firmware, or a combination thereof, and may use at least one of a circuit, a single or multiple integrated circuits for a specific application (Application Specific Integrated Circuit, ASIC), a digital signal processor (Digital Signal Processor, DSP), a digital signal processing device (Digital Signal Processing Device, DSPD), a programmable logic device (Programmable Logic Device, PLD), a field programmable gate array (Field Programmable Gate Array, FPGA), a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, a microprocessor, or a combination thereof, such that the processor may perform some or all of the steps in the method for automatically generating an interface based on a specific programming language described in various embodiments of the present application, or any combination thereof.
The invention has the following beneficial effects:
(1) Unified interface specification: the interface automatically generated by SQL or Groovy can ensure that the format returned by the interface is uniform, and the interface is returned by uniformly using a hump mode, so that the problem of field case is avoided, the error of interface design is reduced, and the stability and maintainability of the system are improved.
(2) An automatic generation interface: through SQL or Groovy script, the interface can be automatically generated according to the database structure or other conditions, thereby saving the time and effort for manually writing the interface
(3) Development efficiency is improved: the method for automatically generating the interface can greatly improve the development efficiency, reduce the workload of writing the interface from scratch and save the development cost. Compared with the personnel at the back end or the front end, the method has the advantages that the time cost is quite saved, the work of writing the interface is reduced at the back end, the time cost of mock is reduced at the front end, and the returned data can be directly tested and checked on line so as to be connected with the interface.
(4) Support online testing: the automatically generated interface supports an online test function, interface test can be performed in an interface mode, the test flow is simplified, and the correctness of the interface is rapidly verified according to the state code returned by the interface.
(5) And (3) authenticating security rights: the platform introduces authentication and API access authority control to avoid confidential data leakage or attack on the system.
(6) Flexibility and extensibility: and generating an interface through SQL or a Groovy script, flexibly expanding the functions and characteristics of the interface according to requirements, and meeting the requirements in different scenes.
Finally, it should be noted that, although the foregoing embodiments have been described in the text and the accompanying drawings of the present application, the scope of the patent protection of the present application is not limited thereby. All technical schemes generated by replacing or modifying equivalent structures or equivalent flows based on the essential idea of the application and by utilizing the contents recorded in the text and the drawings of the application, and the technical schemes of the embodiments are directly or indirectly implemented in other related technical fields, and the like, are included in the patent protection scope of the application.