CN118860361A - A method for online integration of SQL based on low-code platform - Google Patents

Abstract

The invention relates to the technical field of low codes, and provides a method for integrating SQL (structured query language) on line based on a low-code platform, which comprises the following steps: the user drags SQL operation nodes into the designed logic flow; writing a query SQL statement in the SQL operation node; generating corresponding JAVA calling query codes based on SQL operation nodes designed by users; the JAVA calling query code is integrated into the module item source code to integrate into the complete module item source code, and the invention directly opens SQL writing capability, allowing the user to directly write SQL statements to complete complex database operations in order to fulfill complex user business requirements. Compared with the method that query nodes in the logic flow are used for designing queries in a graphical mode, the method allows users to write SQL outside a select statement, such as delete operation and update operation, makes up the defects of the query nodes, enables the users to simply query the database when operating the database, enables complex query or operations outside the select to use the SQL nodes, and improves the operation capability of the low-code platform on the database.

Description

A method for online integration of SQL based on low-code platform

Technical Field

The present invention relates to the field of low-code technology, and in particular to a method for online integration of SQL based on a low-code platform.

Background Art

A low-code platform is a development platform that can quickly generate applications without coding or with a small amount of code. It allows developers to use easy-to-understand visual tools to build business processes, logic, and data models, and add their own code when necessary. The principle of a low-code platform is that operations that can be completed with a mouse should never be implemented by users writing code, but some complex designs are difficult to implement through simple "graphical building block assembly". When users design databases in a visual way for more complex queries, this visual way of writing complex and long queries. If an error occurs during the query process, the problem is difficult to troubleshoot, and subsequent maintenance is also very complicated.

Summary of the invention

The present invention is integrated into the logic flow function of the low-code platform, and uses SQL nodes to complete the design of SQL queries. When the user completes the design and generates code, the backend will generate a method for the SQL node to implement structured queries, thereby realizing the user's ability to design and execute SQL statements or operate databases on the low-code platform.

In order to achieve the above object, the present invention provides the following technical solutions:

The present invention provides a method for online integration of SQL based on a low-code platform, comprising:

(1) The user drags the SQL operation node into the designed logic flow;

(2) Write a query SQL statement in the SQL operation node;

(3) Generate corresponding JAVA call query code based on the SQL operation node designed by the user;

(4) Generate complete module project source code based on JAVA call query code. The JAVA call query code and the module project source code are compatible with each other and can be called normally to achieve the ability of the platform-generated module to support the execution of user-designed SQL; the logic flow is part of the module project.

Furthermore, in step (2), the query SQL statement allows the use of input parameters and local variables declared in the logic flow.

Furthermore, in step (3), the JAVA query code is an XML file that complies with the mybatis specification. With the help of the Mapper file and mybatis, the database query operation is implemented in the module execution environment. The parameters in the designed query SQL statement are set as query parameters. When the specific program is running, mybatis parses and processes and provides real database query capabilities. The Mapper file provides an interface to enable the program to call mybatis to implement specific database queries.

Furthermore, the xml file includes a query SQL statement designed by the user, a Mapper interface class generated in accordance with the mybatis framework specification, a query method corresponding to the interface class definition, and a binding relationship between the query SQL statement.

Furthermore, the binding relationship of the query SQL statement includes that the parameter name and quantity in the query SQL statement are consistent with the parameter name and quantity of the method defined in the interface class, forming a corresponding relationship, and will be automatically bound during execution.

Furthermore, the query method of the mybatis mapper interface class obtains the value of the parameter in the query SQL statement from the context of the logical flow execution in the generated source code, and uses this as a parameter to call the query method in the interface class.

Furthermore, the parameters of the query SQL statement are marked by placeholders, generally using placeholders such as @In1@Name.

Furthermore, when the logic flow is called, the source code corresponding to the SQL operation node of the logic flow executes the corresponding query through mybatis call and passes in the required parameters.

The present invention also provides an electronic device, comprising:

at least one processor;

as well as

a memory communicatively connected to the at least one processor; wherein,

The memory stores one or more computer programs that can be executed by the at least one processor, and the one or more computer programs are executed by the at least one processor so that the at least one processor can execute a method for online integration of SQL based on a low-code platform as described above.

The present invention also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the above-mentioned method of online integration of SQL based on a low-code platform.

The present invention has the following beneficial effects:

The present invention allows users to directly write SQL statements to complete complex database operations by directly opening up SQL writing capabilities, so as to meet complex user business needs. Compared with the query nodes in the logic flow that use a graphical method to design queries, the present invention allows users to write SQL other than select statements in SQL nodes, such as delete operations and update operations, which makes up for the shortcomings of query nodes. When users operate the database, simple queries can use query nodes, and complex queries or operations other than select can use SQL nodes, which improves the low-code platform's ability to operate the database.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flow chart of online integrated SQL in the present invention.

FIG. 2 is a relationship diagram of the actual implementation of the present invention.

DETAILED DESCRIPTION

The specific implementation methods of the present invention are described in detail below in conjunction with the accompanying drawings. It should be pointed out that the embodiments are only specific explanations of the invention and should not be regarded as limitations of the invention. The purpose of the embodiments is to enable those skilled in the art to better understand and reproduce the technical solutions of the present invention. The protection scope of the present invention shall still be based on the scope defined by the claims.

As shown in FIG1 , the present invention provides a method for online integration of SQL based on a low-code platform, comprising:

S1, the user drags the SQL operation node into the designed logic flow;

S2, write the query SQL statement in the SQL operation node;

The query SQL statement allows the use of input parameters and local variables declared in the logic flow.

S3, generates corresponding JAVA call query code based on the SQL operation node designed by the user;

The JAVA call query code is an xml file that complies with the mybatis specification, which includes the query SQL statement designed by the user, the Mapper interface class generated in accordance with the mybatis framework specification, the query method corresponding to the interface class definition, and the binding relationship of the query SQL statement.

The binding relationship of the query SQL statement includes that the parameter name and quantity in the query SQL statement are consistent with the parameter name and quantity of the method defined in the interface class, forming a corresponding relationship, and it will be automatically bound when executed.

The query method of the mybatis mapper interface class obtains the value of the parameter in the query SQL statement from the context of the logical flow execution in the generated source code, and uses it as a parameter to call the query method in the interface class.

The parameters of the query SQL statement are marked by placeholders, generally using placeholders such as @In1@Name.

JAVA calls the query code with the help of Mapper files and mybatis to implement database query operations in the module execution environment. The parameters in the designed query SQL statement are set as query parameters. When the specific program is running, mybatis parses and processes it and provides real database query capabilities. The Mapper file provides an interface to enable the program to call mybatis to implement specific database queries.

S4, based on JAVA call query code, generates complete module project source code. JAVA call query code and module project source code are compatible with each other and can be called normally to achieve the ability of the platform-generated module to support the execution of user-designed SQL; the logic flow is part of the module project.

As shown in Figure 2, when an external request is made and the logic flow is called, the source code corresponding to the SQL operation node of the logic flow executes the corresponding query through mybatis call and passes in the required parameters. Mybatis specifically parses and processes and provides real database query capabilities. The Mapper file provides an interface to enable the program to call mybatis to implement specific database queries.

The present invention also provides an electronic device, comprising:

at least one processor;

as well as

a memory communicatively connected to the at least one processor; wherein,

The memory stores one or more computer programs that can be executed by the at least one processor, and the one or more computer programs are executed by the at least one processor so that the at least one processor can execute a method for online integration of SQL based on a low-code platform as described above.

The present invention also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the above-mentioned method of online integration of SQL based on a low-code platform.

The above code is the source code generated by the SQL node in the logic flow. In the second line, you can see that the Map type parameter paramMap is declared, and the next line of code then inserts the variable pageId into it. Finally, through List<Map<String,Object>>list＝this.baseMapper.sql_5966935532036103_0(paramMap); this code calls sql_5966935532036103_0 in the Mapper interface class to execute the query.

@Repository("Mapper_5966935531905024")

@EnableMybatisProcess

public interface getRoleButtonByPathMapper{

List<Map<String,Object>>sql_5966935532036103_0(Map<String,Object>

paramMap);

}

The above code is the source code in the Mapper interface class getRoleButtonByPathMapper.java, which defines a method sql_5966935532036103_0, and the parameter type is also Map.

The above code is the content of the XML file getRoleButtonByPathMapper.xml, which is used to store the SQL statement designed by the user SQL node; it defines a select type query inside, and the value of the id attribute is sql_5966935532036103_0, which is consistent with the method name defined in the mapper interface class. The value of the namespace attribute in Xml is the fully qualified name of the corresponding Mapper interface class, completing the relationship binding between XML and the interface class. The parameters used in the above SQL statement are converted into the placeholder #{pageId} in the mybatis syntax. You can see that the entire query uses a parameter named pageId, which is consistent with the parameter in the variable paramMap in the logic flow source code.

Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

It should be noted that the technical features not described in detail in the present invention can be implemented by any existing technology.

Claims (10)

1. A method for integrating SQL on line based on a low code platform, comprising:

(1) The user drags SQL operation nodes into the designed logic flow;

(2) Writing a query SQL statement in the SQL operation node;

(3) Generating corresponding JAVA calling query codes based on SQL operation nodes designed by users;

(4) And generating complete module item source codes based on JAVA call query codes.

2. The method of claim 1, wherein in step (2), the query SQL statement allows use of input parameters and local variables declared in the logic flow.

3. The method for integrating SQL on line based on a low-code platform according to claim 1, wherein in the step (3), JAVA call query codes are xml files conforming to mybatis specifications, and database query operation is realized in a module execution environment by means of a Mapper file and mybatis to set parameters in a designed query SQL statement as query parameters.

4. The method for integrating SQL on line based on the low-code platform according to claim 3, wherein the xml file comprises query SQL statements designed by a user, a Mapper interface class generating a specification conforming to mybatis framework, a query method corresponding to interface class definition and a binding relation of the query SQL statements.

5. The method for integrating SQL on line based on the low-code platform according to claim 4, wherein the binding relation of the query SQL statement comprises the consistency of the parameter names and the number in the query SQL statement and the parameter names and the number of the methods defined in the interface class, so as to form a corresponding relation.

6. The method for integrating SQL on line based on low-code platform according to claim 4, wherein the query method of mybatis mapper interface class is to obtain the value of the parameter in the query SQL statement from the context of logic flow execution in the generated source code, and call the query method in the interface class by taking the value as the parameter.

7. The method for on-line integration of SQL based on the low-code platform according to claim 6, wherein the parameters of the query SQL statement are marked by placeholders.

8. The method for integrating SQL on line based on the low-code platform according to claim 1, wherein when the logic flow is called, the source code corresponding to the SQL operation node of the logic flow executes the corresponding query through mybatis call and transmits the required parameters.

9. An electronic device, characterized in that,

Comprising the following steps:

At least one processor;

And

A memory communicatively coupled to the at least one processor; wherein,

The memory stores one or more computer programs executable by the at least one processor, one or more of the computer programs being executable by the at least one processor, to enable the at least one processor to perform the method of any one of claims 1-8.

10. A computer-readable storage medium comprising,

The computer readable storage medium stores a computer program which, when executed by a processor, implements the method of any of claims 1-8.