CN116737127A

CN116737127A - Low code development method, device, equipment and storage medium

Info

Publication number: CN116737127A
Application number: CN202310622078.6A
Authority: CN
Inventors: 王龙; 孙立生; 马相华; 桑国彪; 于潇; 孙梦椰; 张萌萌
Original assignee: Beijing Shenzhou Aerospace Software Technology Co ltd
Current assignee: Beijing Shenzhou Aerospace Software Technology Co ltd
Priority date: 2023-05-29
Filing date: 2023-05-29
Publication date: 2023-09-12

Abstract

The invention relates to the field of computers, and discloses a low-code development method, a device, equipment and a storage medium, wherein the method comprises the following steps: basic information and field information of a business data model are obtained, and an association relation between the business data model and a target data source is established; splicing the entity name of the data source carried in the basic information with the field information to obtain a data definition statement required by starting the target data source; executing a data definition statement in a target data source to obtain a target entity; splicing the received data operation instruction with field information of the business data model to obtain an operation statement for performing data operation on the target entity; the invention can directly analyze the operation information input by the user into the available data processing service without writing codes or generating codes, thereby improving the data processing efficiency and reducing the development technical threshold and the software development cost.

Description

Low code development method, device, equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a low code development method, apparatus, device, and storage medium.

Background

In recent years, with the development of the enterprise management software development industry, the drawbacks of the conventional hard-coded development mode are becoming more prominent, and in order to adapt to the changing external conditions and the rapid and efficient development requirements, more and more new development technologies, such as code generation technologies, componentization technologies, page modeling technologies, model driven development technologies, and the like, are beginning to be used.

In the conventional technology, since enterprises follow different standard specifications when developing software products, technical architecture is irregular, developers spend more time and effort writing program codes familiar with another software, and writing efficiency of the program codes needs to be improved. In recent years, low-code technology and model driven development technology are emerging, but the technology is limited to configuration of a user interface, transformation after code generation and data processing of a single data source, and has the problem of low service universality.

Disclosure of Invention

In view of the above, the present invention provides a low code development method, apparatus, device and storage medium, so as to solve the problem of weak service versatility of program code development mode in the conventional technology.

In a first aspect, the present invention provides a low code development method, the method comprising: basic information and field information of a business data model are obtained, and an association relation between the business data model and a target data source is established; splicing the entity name of the data source carried in the basic information with the field information to obtain a data definition statement required by starting the target data source; executing the data definition statement in a target data source to obtain a target entity; and splicing the received data operation instruction with field information of the business data model to obtain an operation statement for performing data operation on the target entity. Through the process, the operation information input by the user can be directly analyzed into the available data processing service without writing codes or generating codes, so that the data processing efficiency is improved, the development technical threshold is reduced, and the software development cost is reduced.

In an alternative embodiment, before executing the data definition statement in the target data source, the method further comprises:

receiving a login request, and calling a target database driver according to the login request;

importing the data source connection information carried in the login request into a target database driver;

establishing connection between a business data model and a target data source through a target database driver; wherein the data source type of the target data source comprises a relational database, and/or a non-relational database.

In an alternative embodiment, establishing a connection of a business data model to a target data source through a target database driver includes:

when the target database driver is successfully connected to the target data source, returning prompt information of successful connection;

and when the target database driver is not successfully connected to the target data source, returning a prompt message of connection failure.

In an alternative embodiment, the method further comprises:

splicing the received query parameters with the basic information of the view query model to obtain a first query statement; the view query model basic information comprises a model name, a model code, a model type, a data source and an associated model, wherein the model type comprises a statement type and a query statement corresponding to the statement type;

And displaying the query result obtained by executing the first query statement.

In an alternative embodiment, splicing the received data operation instruction with field information of the service data model to obtain an operation statement for performing data operation on the target entity, where the operation statement includes:

splicing the received preservation parameters with field information of the business data model to obtain a target preservation statement for preserving the target entity; wherein, the target saved sentences comprise newly added sentences and modified sentences;

splicing the received query parameters with field information of the business data model to obtain a second query statement for querying the target entity;

and splicing the received deletion parameters with field information of the business data model to obtain a target deletion statement for deleting the target entity.

In an alternative embodiment, the method further comprises:

performing association splicing on a plurality of query results obtained according to the first query statement to obtain a first association data set; or performing association splicing on a plurality of query results obtained according to the second query statement to obtain a second association data set; or performing association splicing on a plurality of query results obtained according to the first query statement and a plurality of query results obtained according to the second query statement to obtain a third triple data set.

In an optional implementation manner, after splicing the received data operation instruction with field information of the service data model to obtain an operation statement for performing data operation on the target entity, the method further includes:

acquiring custom extension configuration information, and triggering a custom extension configuration event based on the custom extension configuration information;

and executing the custom extension processing logic according to the custom extension configuration event, and displaying an execution result of the custom extension processing logic.

In a second aspect, the present invention provides a low-code development device, which mainly includes: the system comprises a relation determining module, a first splicing module, a statement executing module and a second splicing module; the relation determining module is used for acquiring basic information and field information of the service data model and establishing an association relation between the service data model and a target data source; the first splicing module is used for splicing the entity name of the data source carried in the basic information with the field information to obtain a data definition statement required by starting the target data source; the statement execution module is used for executing the data definition statement in the target data source to obtain a target entity; and the second splicing module is used for splicing the received data operation instruction with field information of the business data model to obtain an operation statement for performing data operation on the target entity. Through the process, the operation information input by the user can be directly analyzed into the available data processing service without writing codes or generating codes, so that the data processing efficiency is improved, the development technical threshold is reduced, and the software development cost is reduced.

In a third aspect, the present invention provides a computer device comprising: the memory and the processor are in communication connection with each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the low-code development method of the first aspect or any implementation manner corresponding to the first aspect.

In a fourth aspect, the present invention provides a computer-readable storage medium having stored thereon computer instructions for causing a computer to execute the low code development method of the first aspect or any one of its corresponding embodiments.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic illustration of an application environment of an embodiment of the present invention;

FIG. 2 is a flow chart of a low code development method of an embodiment of the invention;

FIG. 3 is a flow chart of another low code development method of an embodiment of the present invention;

FIG. 4 is a flow chart of yet another low code development method of an embodiment of the present invention;

FIG. 5 is a flow chart of yet another low code development method according to an embodiment of the present invention;

FIG. 6 is a block diagram of a low code development device of an embodiment of the present invention;

fig. 7 is a schematic diagram of a hardware structure of a computer device according to an embodiment of the present invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

The terms first and second in the description and claims of the invention and in the above-mentioned figures are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the term "include" and any variations thereof is intended to cover non-exclusive protection. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus. The term "plurality" in the present invention may mean at least two, for example, two, three or more, and embodiments of the present invention are not limited.

Referring to fig. 1, fig. 1 is a schematic diagram of an application environment according to an embodiment of the present invention, where the schematic diagram includes a terminal 100, and the terminal 100 may include a display 101, a processor 102, and a memory 103. The terminal 100 may be communicatively connected to the server 200 via the network 300, and the server 200 may be configured to provide services (e.g., application services, etc.) to the server or clients installed on the server, and the database 201 may be provided on the server 200 or independent of the server 200 for providing data storage services to the server 200. In addition, a processing engine 202 may be run in the server 200, which processing engine 202 may be used to perform the steps performed by the server 200.

In a specific application, the terminal 100 is provided with web browser software, and the server 200 is provided with a low-code model database, wherein the low-code model database stores a service data model, a view query model and various data sources. The terminal 100 accesses the server through the browser and displays each configuration page. In the data source configuration page, the data source configuration supports multiple types of data sources, such as a common enterprise-level database, a domestic database, an unstructured database, a cache database, multiple data files and the like; the data source configuration not only configures the data source connection information, but also can specify the data source operation mode for realizing the data source dialect adaptation, and other types of data sources can be expanded in the future. In the model configuration page, the terminal 100 displays basic information and field information of a service data model corresponding to the configuration control; the field information is a database table or unstructured data in the target data source, wherein the query result set is formed by SQL and other database query languages in support of optimizing the query performance of the model. In the case of the terminal 100 model save trigger, the server 200 saves a service data model configuring basic information and field information. Under the condition of service data model instantiation, the server 200 splices the received data operation instruction with field information of the service data model to obtain an operation statement for performing data operation on the target entity. When the data is added, deleted and checked, the terminal 100 calls the low-code model database on the server 200 to realize the code-free data operation. Custom extension processing logic may be invoked to process data in the form of interface calls, request responses, and message queues before and after various operations of data augmentation and pruning.

Alternatively, the terminal 100 may be, but is not limited to, a terminal capable of calculating data, such as a mobile terminal (e.g., a mobile phone, a tablet computer), a notebook computer, a PC (Personal Computer, a personal computer) or the like, and the network may include, but is not limited to, a wireless network or a wired network. Wherein the wireless network comprises: bluetooth, WIFI (Wireless Fidelity ) and other networks that enable wireless communications. The wired network may include, but is not limited to: wide area network, metropolitan area network, local area network. The server 200 may include, but is not limited to, any hardware device that may perform calculations.

In addition, in this embodiment, the low-code development method may be applied, but not limited to, to a stand-alone processing device with a relatively high processing capability, without data interaction. For example, the processing device may be, but is not limited to, a more processing-capable terminal device, i.e., the various operations of the low-code development method described above may be integrated into a single processing device. The above is merely an example, and is not limited in any way in the present embodiment.

Alternatively, in the present embodiment, the low-code development method may be executed by the server 200, may be executed by the terminal 100, or may be executed by both the server 200 and the terminal 100. In which the terminal 100 performs the low code development method of the embodiment of the present invention may be performed by a client installed thereon.

In accordance with an embodiment of the present invention, a low code development method embodiment is provided, it being noted that the steps shown in the flowchart of the figures may be performed in a computer system, such as a set of computer executable instructions, and, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in an order other than that shown or described herein.

In this embodiment, a low code development method is provided, which may be used for the above terminal, where the terminal communicates with a server through a network, and fig. 2 is a flowchart of the low code development method according to an embodiment of the present invention, as shown in fig. 2, and the flowchart includes the following steps:

step S201, basic information and field information of a business data model are obtained, and an association relation between the business data model and a target data source is established.

In this embodiment, the basic information and the field information of the service data model are acquired, so that the basic information and the field information of the service data model are spliced with the instruction input by the user, thereby obtaining the data definition statement required by starting the target data source. By establishing the association relation between the business data model and the target data source, necessary conditions are provided for obtaining data definition sentences required by starting the target data source. The business data model is a data model capable of representing basic information and field information of business data.

In an alternative implementation manner, based on the type of the service data, the basic information and the field information of the service data model stored in the low-code model library storage can be directly obtained, and the association relationship between the service data model and the target data source is established.

In an alternative implementation manner, when a terminal where a user is located receives an instruction for configuring a data source, in a page for configuring data source information, different data source information can be configured by selecting a data source type, common data source information includes attributes such as a connection address, a user name, a password, a driver and other necessary parameters, default selectable common data source types such as a relational database (Mysql, oracle, postgresql, a dream, a personal Jin Cang, a miracle and other databases), a non-relational database (MongoDB, doris), a cache database (dis), a data file (Excel, CSV, JSON, XML), and other types of data sources can be expanded in the future. After receiving the data source configuration information to be stored sent by the terminal, the server configures the corresponding data source according to the data source information to obtain a target data source, and stores the target data source in the low-code model database.

For example, configuring data source information of a Mysql database requires configuring information such as a database connection address, a user name, a password, a driver and the like on a terminal page, and after receiving the data source configuration information sent by the terminal, the server configures a corresponding data source according to the data source configuration information to obtain a target data source and stores the target data source in a low-code model database.

In an optional implementation manner, when a terminal where a user is located receives an instruction for configuring a service data model, a service data model configuration page is firstly configured with basic information such as a name, a code, a data source name, a data source entity name, an association model, an association field, a primary key, a default ordering field and the like of the service data model, then a target data source corresponding to the data source name is queried from a low-code model library, and an association relation is established with the target data source. And finally, configuring the fields of the business data model, wherein the default automatic fields comprise a main key field, a creator, creation time, an updater, update time and the like. The field attributes such as field name, chinese name, type, default value, etc. can be configured. The default values can be set as default values in the new addition and default values in the modification, and support constants, current personnel, current time, primary key generation, automatic numbering and the like. The data source of the field may also be defined, such as from a dictionary table, from other models, etc., and whether the field is a query parameter may be set to create the necessary index for the field. Tables and other entities in the target data source can also be read from the server, the entity field information is read, and the entity field information is reversely filled into the business data model field information. After the model information of the service data model is filled, a 'save' button can be clicked, and the configuration information of the service data model is sent to a server for saving. After receiving the configuration information of the service data model, the server configures the basic information and the field information of the corresponding service data model according to the configuration information of the service data model, and stores the basic information and the field information in a low-code model database so as to directly acquire the basic information and the field information of the service data model when the target data source is spliced to start the required data definition statement.

For example, a service data model NAME is "BOOK" is configured on a terminal service data model PAGE, a BOOK is encoded, a Mysql data source is selected, a corresponding model encoding BOOK_INFO is configured, and fields include a unique primary key ID (default UUID), a NAME NAME, PAGE number PAGE, an OWNER (default value is the current user), and the like. The terminal requests the server and stores the configuration information of the business data model. After receiving the configuration information of the service data model, the server configures basic information and field information of the corresponding service data model according to the configuration information of the service data model, and stores the basic information and the field information in a low-code model database.

Step S202, splicing the data source entity name carried in the basic information with the field information to obtain a data definition statement required by starting the target data source.

In this embodiment, the server splices the field information with the name of the data source entity carried in the basic information of the service data model to obtain a data definition statement required for starting the target data source, so as to generate the target entity.

In an alternative implementation mode, a server acquires a service data model which is stored in a low-code model database and is updated with basic information and field information, and the service data model is spliced with the field information according to a data source entity name carried in the basic information of the service data model to obtain a data definition statement required by starting a target data source.

Based on step S201, for example, after the terminal requests the service data model to be instantiated, the server reads the service model information, concatenates the table DDL statement CREATE TABLE BOOK _info color (ID VARCHAR (64) PK, NAME VARCHAR (64)), PAGE NUMBER, OWNER VARCHAR (64)), then connects to the Mysql data source, executes the table DDL statement in the Mysql data source, and creates a book_info table (target entity).

Step S203, executing the data definition statement in the target data source to obtain the target entity.

In this embodiment, the target entity is obtained by executing the data definition statement in the target data source, so as to provide a basis for performing data operation on the target entity. The target entity is stored in a table form in a relational database, in a JSON format in a key value database, a document type database and a text file, and in a data form in a table file.

Step S204, splicing the received data operation instruction with field information of the business data model to obtain an operation statement for performing data operation on the target entity.

In this embodiment, the received data operation instruction is spliced with field information of the service data model to obtain an operation statement for performing data operation on the target entity, and the received data operation instruction is directly analyzed into the available data processing service without writing codes or generating codes.

In an alternative implementation manner, the received saving parameters are spliced with field information of the business data model to obtain a target saving statement for saving the target entity; wherein, the target saved sentences comprise newly added sentences and modified sentences; splicing the received query parameters with field information of the business data model to obtain a second query statement for querying the target entity; and splicing the received deletion parameters with field information of the business data model to obtain a target deletion statement for deleting the target entity.

According to the low-code development method provided by the embodiment, basic information and field information of a business data model are firstly obtained, and an association relation between the business data model and a target data source is established so as to splice instructions input by a user based on the basic information and the field information of the business model, thereby obtaining data definition sentences required by starting the target data source, and providing necessary conditions for obtaining the data definition sentences required by starting the target data source; the method comprises the steps of splicing a data source entity name carried in basic information with field information to obtain a data definition statement required by starting a target data source so as to generate a target entity; the target entity is obtained by executing the data definition statement in the target data source, so that a basis is provided for carrying out data operation on the target entity; by splicing the received data operation instruction with field information of the business data model, an operation statement for performing data operation on the target entity is obtained, namely the received data operation instruction is directly analyzed into available data processing service, and the code is not required to be written or generated, so that the data processing efficiency is greatly improved, the development technical threshold is reduced, and the software development cost is effectively reduced.

In this embodiment, a low code development method is provided, which may be used for the above terminal, where the terminal communicates with a server through a network, and fig. 3 is a flowchart of the low code development method according to an embodiment of the present invention, and as shown in fig. 3, the flowchart includes the following steps:

step S301, basic information and field information of a business data model are obtained, and an association relation between the business data model and a target data source is established.

Please refer to step S201 in the embodiment shown in fig. 2 in detail, which is not described herein.

Step S302, the data source entity name carried in the basic information is spliced with the field information to obtain the data definition statement required by starting the target data source.

Please refer to step S202 in the embodiment shown in fig. 2, which is not described herein.

Step S303, executing the data definition statement in the target data source to obtain a target entity.

In an alternative implementation manner, before executing a data definition statement in a target data source, receiving a login request initiated by a terminal, and calling a target database driver according to the login request; importing the data source connection information carried in the login request into a target database driver; establishing connection between a business data model and a target data source through a target database driver, and providing an execution basis for executing data definition sentences in the target data source; when the target database driver is successfully connected to the target data source, returning prompt information of successful connection so as to prompt a user to execute a data definition statement in the target data source; and when the target database driver is not successfully connected to the target data source, returning a prompt message of connection failure so as to prompt the user that the target data source cannot be accessed.

Step S304, splicing the received data operation instruction with field information of the business data model to obtain an operation statement for performing data operation on the target entity.

Specifically, the step S304 includes:

step S3041, splicing the received preservation parameters with field information of the business data model to obtain a target preservation statement for preserving the target entity.

In this embodiment, the received saving parameters are spliced with field information of the service data model to obtain a target saving statement for saving the target entity. Wherein the target save statement includes a new statement and a modified statement.

In an alternative embodiment, the terminal prepares the data and sends a save data request: when data is stored, a data storage request is initiated, and model coding and JSON object format data are required to be used as storage parameters. If the data is stored in a single data, the storage parameters are transferred by a JSON object structure, and the attribute names in the JSON correspond to the model field names. If a plurality of pieces of data are stored in batches, the JSON needs to be assembled in the form of JSON arrays. The associated sub-table uses a JSON array structure to transfer the storage parameters, the array name is the model code of the sub-model, and the JSON array can be nested in the JSON array. In addition, when one field in the main table corresponds to a plurality of pieces of data, the format of "submodel name # field" may be used as a key of the JSON object. In addition, the sub-table list is a "tiled" sub-table list with a fixed number of sub-tables and partial fields, and the "sub-model name [ i ] @ field" can be used as a key of the JSON object, where i is the number of data, and must be sequentially increased from 0. And after the terminal is ready to store parameters, calling a server data storage interface, and feeding back a data storage result.

The server data storage interface stores data: the method is mainly divided into two parts, namely model preservation and sub-model preservation.

Model preservation: after receiving the request for saving the parameters, the server firstly queries the corresponding service data model through the model code in the saving parameters, and acquires the basic information (one or more of name, code, target data source, data source entity name, association model, association field, primary key and default ordering field) and the field information of the service data model. Then analyzing the JSON data, and comparing the JSON data with the data of the business data model and the target entity to sort the data. First judging a main key, automatically generating the main key if the main key is not present in the target entity, if the main key value in the data is not present in the target entity, searching and modifying other fields carried by the data according to the main key if the main key value in the data is present in the target entity. Then, default values can be set for the fields in both new and modified cases, and if no data is entered in the save parameters (forms), the fields are filled with default values. The new default value only covers the original value when in new addition, and the original value is not covered when in new addition and modification. Fields that exist in the business data model but do not exist in the save parameters are not updated and fields that exist in the save parameters but do not exist in the business data model are ignored. After the data preparation is completed, splicing and storing sentences according to the field information of the business data model, connecting a target data source where the business data model data is located, and executing data new addition or sentence modification.

And (5) sub-model preservation: the submodel carried in JSON data will be converted into format and finally expanded into arrays. And (5) cycling the array of the sub-model data, and recursively calling a sub-model storage method. And filling the field values of the main model into the field values of the sub-model association according to the field configuration of the sub-model association main model. If the main key of the sub-model exists, the data is updated, if the main key does not exist, the data is newly added, if the original sub-model data is related to the data, and if the main key of the data does not exist at this time, the data can be deleted, and if the sub-model data does not exist, no operation is performed on the sub-model. After the target save statement is spliced, the data sent by the input terminal is used as save parameters, the data source where the business data model is located is connected, the target save statement is executed, and the result is fed back.

By way of example: when the BOOK information is stored, the client fills in the BOOK information and transmits the encoded BOOK_INFO of the service data model, and a server storage interface is called. And the server queries service data model information according to the BOOK_INFO code of the service data model and splices the BOOK information filled in by the client with field information configured in the service data model. If the client side does not transmit the book ID, the client side automatically generates the ID, if the book ID is transmitted, the client side is connected with a target data source of the business data model, the book data is queried according to the ID, if the book data is not found, the book data is newly added, and if the book data is found, the book data is modified. Splicing INSERT sentences according to the transferred fields in the new process, splicing UPDATE sentences according to the transferred fields in the modification process, and finally executing.

Step S3042, splice the received query parameter and the field information of the business data model to obtain a second query statement for querying the target entity.

In this embodiment, the received query parameters are spliced with field information of the service data model to obtain a second query statement for querying the target entity, so that data can be queried directly according to the second query statement.

In an alternative embodiment, the terminal prepares the query parameters and sends a data query request: the model code and a plurality of query parameters need to be sent in JSON object format, and one query parameter contains a plurality of values for splicing. The terminal calls a server data query interface to display a data query result. The server data query interface queries data: firstly, inquiring a service data model in a low-code model database according to a model code carried in the inquiring parameter, and then splicing the received inquiring parameter and field information of the service data model to obtain a second inquiring statement for inquiring the target entity.

For example, the terminal invokes the server data model query interface after filling in the query parameters. According to fields configured in the business data model corresponding to the query parameters as conditions, splicing query sentences, connecting Mysql data sources, executing the query sentences, splicing query results into a JSON format, feeding back to the terminal, and displaying data by the terminal according to the JSON.

And step S3043, splicing the received deletion parameters with field information of the business data model to obtain a target deletion statement for deleting the target entity.

In this embodiment, the received deletion parameters are spliced with field information of the service data model to obtain a target deletion statement for deleting the target entity, so that the data deletion operation of the target entity is directly performed according to the deletion statement.

In an alternative embodiment, the terminal prepares the deletion parameter and sends a data deletion request: when deleting data, a data deleting request is initiated, and model coding and JSON object format data are required to be used as parameters. The JSON object format is { "primary key": "primary key value" }, multiple primary key values are spliced. And the terminal calls a server data deleting interface and feeds back a data deleting result. Server data deletion interface delete data: the model information (such as business data model) is first queried in the low code model database according to the model code and then the associated model information is queried. And splicing data deleting sentences according to the main key configured by the model information of the service data model and the target entity, taking the main key value sent by the input terminal as a parameter, connecting a data source where the service model data is, executing the data deleting sentences to delete the data, and feeding back the deleting result. And deciding whether to cascade delete the sub-models according to the configuration of whether the association model is cascade delete. When the sub-model data is deleted in cascade, according to the field configuration of the sub-model associated main model, the main model field value is used as a query condition to query and delete the data.

For example, when deleting BOOK information, the client selects and concatenates the data ID to be deleted and delivers the model code book_info, and invokes the data deletion interface of the server. The server queries service data model information according to the model code BOOK_INFO, generates a DELETE statement, and executes the DELETE statement by taking the data ID as a parameter.

In this embodiment, a low code development method is provided, which may be used for the above terminal, where the terminal communicates with a server through a network, and fig. 4 is a flowchart of the low code development method according to an embodiment of the present invention, as shown in fig. 4, and the flowchart includes the following steps:

step S401, obtaining basic information and field information of a business data model, and establishing an association relation between the business data model and a target data source.

Step S402, splicing the data source entity name carried in the basic information with the field information to obtain a data definition statement required by starting the target data source.

Step S403, executing the data definition statement in the target data source to obtain the target entity.

Please refer to step S303 in the embodiment shown in fig. 3 in detail, which is not described herein.

Step S404, splicing the received data operation instruction with the field information of the business data model to obtain an operation sentence for performing data operation on the target entity

Please refer to step S304 in the embodiment shown in fig. 3 in detail, which is not described herein.

Step S405, splicing the received query parameters and the view query model basic information to obtain a first query sentence, and displaying a query result obtained by executing the first query sentence.

In this embodiment, the received query parameters and the view query model basic information are spliced to obtain a first query statement, and a query result obtained by executing the first query statement is displayed, so that convenience and efficiency of user data query are improved. The view query model basic information comprises a model name, a model code, a model type, a data source and an associated model, wherein the model type comprises a statement type and a query statement corresponding to the statement type.

In an alternative embodiment, the terminal configures the view query model: the view query model configuration page can set basic information such as model names, model codes, model types, data sources, association models and the like. The association fields among the models are set to establish association relation, so that data joint inquiry across multiple data sources can be realized, and three association modes of connection (JOIN), main and sub (one-to-many) and addition (UNION) can be selected. The view query model configuration page is provided with a selection model type of SQL statement, corresponding SQL query statement is obtained according to the selected SQL statement, or the SQL query statement can be directly filled, the selection view query model type of interface can access a user-defined server data interface, the selection view query model type of document query is provided with a selection document data source, and the selection document query statement can be written for reading a document or a document database. The query parameters of the view query model may be set, wherein the dynamic parameters are not used as query parameters when no values are transferred, and the fixed parameters are always used as query parameters. The query parameters may perform various functional processes, support or and logic, providing a variety of operators and default settings, including, but not limited to "include", "equal to", "greater than", "less than", "present", etc. operators. The terminal can initiate a view query model query test, fill in necessary parameters, receive a query result fed back by the server and display the query result.

For example, a view query model of an SQL query is configured, a model name and a model code are filled in, the view query model type is selected as the SQL query, the target data source is Mysql data source, the SQL query statement select_info write Owner= #user is filled in, the fixed parameter USER is newly added, the default value is the login USER ID, the dynamic parameter time is newly added, and the query operator is "including" and model information is saved. And when the interface is tested, the server inquires two parameters, namely a USER and a NAME, and returns to the terminal for filling in test data, wherein the USER defaults to fill in the USER ID value. After the terminal fills in parameters, the terminal inquires, a server splices an inquiry statement select_info write OWNER = #USER } (AND NAME LIKE '% $ { time }') if NAME attributes are transmitted, namely after the inquiry conditions/parameters are spliced with a first inquiry statement carried in a view inquiry model, the terminal is connected with a Mysql data source, the first inquiry statement is executed, an inquiry result is spliced into a JSON format and fed back to the terminal, and the terminal displays data according to the JSON.

In an optional implementation manner, a plurality of query results obtained according to the first query statement are subjected to association splicing to obtain a first association data set; or performing association splicing on a plurality of query results obtained according to the second query statement to obtain a second association data set; or performing association splicing on a plurality of query results obtained according to the first query statement and a plurality of query results obtained according to the second query statement to obtain a third triple data set.

In specific implementation, the terminal inquires parameters and sends a data inquiry request: the model code and a plurality of query parameters need to be sent in JSON object format, and one query parameter contains a plurality of values for splicing. The terminal calls a server data query interface to display a data query result. The server data query interface queries data: the model information is first queried in a low code model database according to the model code and then the associated model information is queried. And splicing the query statement according to the model configuration in the business data model, and querying by using the query statement or calling interface in the view query model. After generating the query statement, the terminal is taken to transfer the fixed parameters and the default parameters of the model in the query parameters, and the query statement is spliced. And then packaging the results of the query statement, splicing the results into dynamic query conditions according to the input dynamic parameters, and carrying out secondary filtering on the query results. And connecting a target data source where the business data model and the view query model are located, and executing a query statement or calling an interface to acquire a feedback result. And then carrying out association model data query, and carrying out data assembly according to the model association relation. The assembly mode of the association model is divided into three types of connection (JOIN), main sub (one-to-many) and additional (UNION). The connection (JOIN) mode queries that the data of a plurality of models are matched according to the configuration of the associated fields of the models, is combined into a JSON object, and forms a JSON array return. The main sub (one-to-many) mode takes main model data as a JSON array, wherein each piece of data is matched according to the management field configuration of the model, and is brought into the JSON array formed by a plurality of pieces of data of the sub model. The additional (UNION) mode is to put the main model data into the JSON array, and then add the associated model data to the main model data.

The low-code development method provided by the embodiment firstly obtains basic information and field information of a service data model, establishes an association relation between the service data model and a target data source so as to splice instructions input by a user based on the basic information and the field information of the service model, thereby obtaining data definition sentences required by starting the target data source, and providing necessary conditions for obtaining the data definition sentences required by starting the target data source; the method comprises the steps of splicing a data source entity name carried in basic information with field information to obtain a data definition statement required by starting a target data source so as to generate a target entity; the target entity is obtained by executing the data definition statement in the target data source, so that a basis is provided for carrying out data operation on the target entity; the method comprises the steps of splicing a received data operation instruction with field information of a business data model to obtain an operation statement for performing data operation on a target entity, or splicing a received query parameter with a query statement carried in a view query model to obtain a first query statement, displaying a query result obtained by executing the first query statement, namely directly analyzing the received data operation instruction into available data processing service without writing codes or generating codes; the correlation splicing query of various data sources and heterogeneous data is supported through the relation among the models, so that the convenience and performance concurrency of the data query are improved, the data processing efficiency is greatly improved, the development technical threshold is reduced, and the software development cost is effectively reduced.

In this embodiment, a low code development method is provided, which may be used for the above terminal, where the terminal communicates with a server through a network, and fig. 5 is a flowchart of the low code development method according to an embodiment of the present invention, as shown in fig. 5, and the flowchart includes the following steps:

step S501, basic information and field information of a business data model are obtained, and an association relation between the business data model and a target data source is established.

Please refer to step S201 of the embodiment shown in fig. 2 for details.

Step S502, splicing the data source entity name carried in the basic information with the field information to obtain a data definition statement required by starting the target data source.

Please refer to step S202 in the embodiment shown in fig. 2 for details.

Step S503, executing the data definition statement in the target data source to obtain the target entity.

Step S504, splicing the received data operation instruction with field information of the business data model to obtain an operation statement for performing data operation on the target entity.

Step S505, the received query parameters and the view query model basic information are spliced to obtain a first query sentence, and a query result obtained by executing the first query sentence is displayed.

Please refer to step S405 in the embodiment shown in fig. 4 in detail, which is not described herein.

Step S506, acquiring the custom extension configuration information, and triggering the custom extension configuration event based on the custom extension configuration information.

In this embodiment, by acquiring the custom extension configuration information and triggering the custom extension configuration event based on the custom extension configuration information, necessary processing can be performed on the data before and after the data operation, so as to ensure the expandability of the program.

Step S507, executing the custom expansion processing logic according to the custom expansion configuration event, and displaying the execution result of the custom expansion processing logic.

In this embodiment, the user-defined expansion processing logic is executed according to the user-defined expansion configuration event, and the execution result of the user-defined expansion processing logic is displayed, so that the user can obtain the result of expanding the data in time.

An alternative implementation is that the client configures custom extension information and saves it in the server: the client configures the custom extension information, and can write the information such as the name, the code, the association model, the trigger event type, the execution condition, the execution sequence number, the extension type, the custom extension access mode and the like of the custom extension. And transmitting the configured data, and storing the configured data in a low-code model database by a low-code server.

Writing code development custom extensions: custom extensions may be developed in the form of interface calls, request responses, or message queues. The interface calling extension needs to be packaged into a package to be issued together with the low code platform, and the low code platform directly calls the extension code. The request response extension requires the development of independently initiated HTTP-enabled services and provides an interface in the form of Webservice or JSONP. Message queue extension requires listening to the broadcast event of the message queue and pushing the completion message after logic is completed.

The server performs custom extensions: before and after executing target entity deletion, the server queries the configuration information of the custom expansion, triggers a configuration event in the custom expansion and executes custom expansion processing logic. And calling the custom code in the modes of interface calling, request response or message queue and the like according to different types of events. Custom extensions support synchronous calls or asynchronous calls. The custom extension supports chained task processing and can be called by a condition, a sequence, a parallel and a loop. When the server calls the custom extension, the data in the current target entity is transferred to the custom extension, the event processing interface performs various custom business logic operations according to the data in the current target entity, and returns an operation result, and the operation result enters the next custom extension. The problem of program expansibility is solved by custom event and chained task processing.

According to the low-code development method provided by the embodiment, basic information and field information of a business data model are firstly obtained, and an association relation between the business data model and a target data source is established so as to splice instructions input by a user based on the basic information and the field information of the business model, thereby obtaining data definition sentences required by starting the target data source, and providing necessary conditions for obtaining the data definition sentences required by starting the target data source; the method comprises the steps of splicing a data source entity name carried in basic information with field information to obtain a data definition statement required by starting a target data source so as to generate a target entity; the target entity is obtained by executing the data definition statement in the target data source, so that a basis is provided for carrying out data operation on the target entity; the received data operation instruction is spliced with field information of the business data model to obtain an operation statement for performing data operation on a target entity, namely the received data operation instruction is directly analyzed into available data processing service without writing codes or generating codes, so that the data processing efficiency is greatly improved, the development technical threshold is reduced, and the software development cost is effectively reduced; and meanwhile, the data is subjected to necessary processing through a custom expansion processing logic before and after the data operation, so that the expandability of the program is ensured.

In this embodiment, a low-code development device is further provided, and the device is used to implement the foregoing embodiments and preferred embodiments, and will not be described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

The present embodiment provides a low code development apparatus, as shown in fig. 6, including:

the relationship determining module 601 is configured to obtain basic information and field information of the service data model, and establish an association relationship between the service data model and the target data source.

The first splicing module 602 is configured to splice the entity name of the data source carried in the basic information with the field information, so as to obtain a data definition statement required for starting the target data source.

The statement execution module 603 is configured to execute the data definition statement in the target data source to obtain the target entity.

In some alternative embodiments, the statement execution module 603 includes:

the drive calling unit is used for receiving a login request and calling a target database drive according to the login request;

The information importing unit is used for importing the data source connection information carried in the login request into a target database driver;

the connection creation unit is used for establishing connection between the business data model and the target data source through the target database driver; wherein the data source type of the target data source comprises a relational database, and/or a non-relational database.

The first indicating unit is used for returning prompt information of successful connection when the target database driver is successfully connected to the target data source;

and the second indicating unit is used for returning the indicating information of connection failure when the target database drive is not successfully connected to the target data source.

And the second splicing module 604 is configured to splice the received data operation instruction with field information of the service data model to obtain an operation statement for performing data operation on the target entity.

In some alternative embodiments, the second stitching module 604 includes:

the save statement splicing unit is used for splicing the received save parameters with field information of the business data model to obtain a target save statement for saving the target entity; wherein, the target saved sentences comprise newly added sentences and modified sentences;

The query statement splicing unit is used for splicing the received query parameters with field information of the business data model to obtain a second query statement for querying the target entity;

and the deleting statement splicing unit is used for splicing the received deleting parameters with field information of the service data model to obtain a target deleting statement for deleting the target entity.

In some alternative embodiments, the apparatus further comprises:

and the third splicing module is used for splicing the received query parameters with the basic information of the view query model to obtain a first query statement.

And the display module is used for displaying the query result obtained by executing the first query statement.

The fourth splicing unit is used for carrying out association splicing on a plurality of query results obtained according to the first query statement to obtain a first association data set; or performing association splicing on a plurality of query results obtained according to the second query statement to obtain a second association data set; or performing association splicing on a plurality of query results obtained according to the first query statement and a plurality of query results obtained according to the second query statement to obtain a third triple data set.

The custom expansion module is used for acquiring custom expansion configuration information and triggering a custom expansion configuration event based on the custom expansion configuration information; and executing the custom extension processing logic according to the custom extension configuration event, and displaying an execution result of the custom extension processing logic.

And the message broadcasting module is used for broadcasting the refreshing message in the local area network through a link layer management protocol.

The low code development device in this embodiment is presented in the form of functional units, where the units refer to ASIC circuits, processors and memories executing one or more software or firmware programs, and/or other devices that can provide the functionality described above.

Further functional descriptions of the above respective modules and units are the same as those of the above corresponding embodiments, and are not repeated here.

The embodiment of the invention also provides computer equipment, which is provided with the low-code development device shown in the figure 6.

Referring to fig. 7, fig. 7 is a schematic structural diagram of a computer device according to an alternative embodiment of the present invention, as shown in fig. 7, the computer device includes: one or more processors 10, memory 20, and interfaces for connecting the various components, including high-speed interfaces and low-speed interfaces. The various components are communicatively coupled to each other using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions executing within the computer device, including instructions stored in or on memory to display graphical information of the GUI on an external input/output device, such as a display device coupled to the interface. In some alternative embodiments, multiple processors and/or multiple buses may be used, if desired, along with multiple memories and multiple memories. Also, multiple computer devices may be connected, each providing a portion of the necessary operations (e.g., as a server array, a set of blade servers, or a multiprocessor system). One processor 10 is illustrated in fig. 7.

The processor 10 may be a central processor, a network processor, or a combination thereof. The processor 10 may further include a hardware chip, among others. The hardware chip may be an application specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general-purpose array logic, or any combination thereof.

Wherein the memory 20 stores instructions executable by the at least one processor 10 to cause the at least one processor 10 to perform a method for implementing the embodiments described above.

The memory 20 may include a storage program area that may store an operating system, at least one application program required for functions, and a storage data area; the storage data area may store data created from the use of the computer device of the presentation of a sort of applet landing page, and the like. In addition, the memory 20 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, memory 20 may optionally include memory located remotely from processor 10, which may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

Memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk, or solid state disk; the memory 20 may also comprise a combination of the above types of memories.

The computer device also includes a communication interface 30 for the computer device to communicate with other devices or communication networks.

The embodiments of the present invention also provide a computer readable storage medium, and the method according to the embodiments of the present invention described above may be implemented in hardware, firmware, or as a computer code which may be recorded on a storage medium, or as original stored in a remote storage medium or a non-transitory machine readable storage medium downloaded through a network and to be stored in a local storage medium, so that the method described herein may be stored on such software process on a storage medium using a general purpose computer, a special purpose processor, or programmable or special purpose hardware. The storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, a solid state disk or the like; further, the storage medium may also comprise a combination of memories of the kind described above. It will be appreciated that a computer, processor, microprocessor controller or programmable hardware includes a storage element that can store or receive software or computer code that, when accessed and executed by the computer, processor or hardware, implements the methods illustrated by the above embodiments.

Although embodiments of the present invention have been described in connection with the accompanying drawings, various modifications and variations may be made by those skilled in the art without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope of the invention as defined by the appended claims.

Claims

1. A method of low code development, the method comprising:

basic information and field information of a business data model are obtained, and an association relation between the business data model and a target data source is established;

splicing the entity name of the data source carried in the basic information with field information to obtain a data definition statement required by starting the target data source;

executing the data definition statement in the target data source to obtain a target entity;

and splicing the received data operation instruction with the field information of the business data model to obtain an operation statement for performing data operation on the target entity.

2. The method of claim 1, wherein prior to executing the data definition statement in the target data source, the method further comprises:

Importing the data source connection information carried in the login request into the target database driver;

establishing connection between the business data model and a target data source through the target database driver; wherein the data source type of the target data source comprises a relational database and/or a non-relational database.

3. The method of claim 2, wherein establishing a connection of the business data model with a target data source through the target database driver comprises:

4. A method according to claim 3, characterized in that the method further comprises:

5. The method of claim 3, wherein concatenating the received data manipulation instruction with field information of the business data model to obtain the manipulation statement for manipulating the data of the target entity, comprises:

splicing the received preservation parameters with field information of the business data model to obtain a target preservation statement for preserving the target entity; wherein the target save statement comprises a new statement and a modified statement;

and splicing the received deletion parameters with the field information of the business data model to obtain a target deletion statement for deleting the target entity.

6. The method according to claim 4 or 5, further comprising;

7. The method according to any one of claims 1 to 5 or claim 6, wherein after splicing the received data operation instruction with field information of the service data model to obtain an operation statement for performing a data operation on the target entity, the method further includes:

8. A low code development device, the device comprising:

the relation determining module is used for acquiring basic information and field information of the service data model and establishing an association relation between the service data model and a target data source;

the first splicing module is used for splicing the entity name of the data source carried in the basic information with the field information to obtain a data definition statement required by starting the target data source;

the statement executing module is used for executing the data definition statement in the target data source to obtain a target entity;

And the second splicing module is used for splicing the received data operation instruction with the field information of the business data model to obtain an operation statement for performing data operation on the target entity.

9. A computer device, comprising:

a memory and a processor in communication with each other, the memory having stored therein computer instructions which, upon execution, cause the processor to perform the method of any of claims 1 to 7.

10. A computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method of any one of claims 1 to 7.