Low-code development method and platform based on data driving

Abstract

The invention relates to the technical field of data drive development, in particular to a low-code development method and platform based on data drive. The platform comprises a data base layer, a page data layer, a page function driving layer, a page presentation layer and a business data driving layer, and the data base layer comprises a field module and a dictionary module and is used for obtaining database table unit data information; the page data layer comprises a page pre-representation unit and is used for generating a database metadata page form prototype; the page function driving layer comprises various types of page function submodules and is used for performing various types of Sql drive generation and delay lifting drive execution so as to generate various types of Sql execution statements; the page presentation layer comprises a page postposition design unit and is used for generating a database drawing board page layout optimization form; and the business data driving layer comprises a data maintenance module, a receipt module, a query module and an auditing module and is used for performing driving operation. According to the invention, the construction of a complex logic platform can be simplified.

Description

Technical Field

[0001] The present invention relates to the field of data-driven development technology, and in particular to a data-driven low-code development method and platform. Background Art

[0002] Low-code development platforms have been widely used in multiple industries, including but not limited to manufacturing, retail, education, the Internet, and the service industries. These platforms provide visual development tools, allowing non-professional developers to participate in the application building process, greatly reducing the development threshold. Low-code development currently focuses more on providing easy-to-use interfaces and tools while ensuring sufficient flexibility to meet the needs of different scenarios. However, most traditional low-code platforms usually provide a visual drag-and-drop interface that allows users to quickly build applications through pre-built templates and controls. This model performs well in processing simple business logic, but encounters challenges in complex data processing. For example, complex data relationships and statement delay-driven execution often require more professional data processing support, which is beyond the capabilities of traditional low-code platforms, resulting in deficiencies in the integration of low-code platforms with existing enterprise systems. Summary of the invention

[0003] Based on this, it is necessary for the present invention to provide a data-driven low-code development method and platform to solve at least one of the above-mentioned technical problems.

[0004] To achieve the above objectives, a data-driven low-code development platform includes the following module layers from bottom to top:

[0005] The data foundation layer includes a field module and a dictionary module, wherein the field module is used to obtain the field name and field value corresponding to the business data to obtain the business database table metadata column; the dictionary module is used to obtain the field type dictionary corresponding to the business data to generate the business database table field dictionary attributes; the business database table metadata column and the business database table field dictionary attributes are used as database form metadata information;

[0006] The page data layer includes a page front-end representation unit corresponding to the drawing board module, which is used to generate a page form based on the database form metadata information to generate a database metadata page form prototype;

[0007] The page function driver layer includes various page function sub-modules, which are used to generate various Sql drivers of the drawing board controls for the database metadata page form prototype, and generate various database page form control Sql driver statements; based on various database page form control Sql driver statements, the page form delay promotion driver execution is performed on the database metadata page form prototype to generate various form control delay promotion Sql execution statements, including maintenance Sql execution statements, document Sql execution statements, query Sql execution statements, and review Sql execution statements;

[0008] The page presentation layer includes a page post-design unit corresponding to the drawing board module, which is used to optimize the page layout design of the database metadata page form prototype to generate a database drawing board page layout optimization form;

[0009] The business data driving layer includes a data maintenance module, a document module, a query module and an audit module, wherein the data maintenance module is used to perform maintenance driving operations on the database drawing board page layout optimization form based on the maintenance Sql execution statement; the document module is used to perform document expansion calculation driving operations on the database drawing board page layout optimization form based on the document Sql execution statement; the query module is used to perform query driving operations on the database drawing board page layout optimization form based on the query Sql execution statement; the audit module is used to perform positive and negative audit driving operations on the database drawing board page layout optimization form based on the audit Sql execution statement.

[0010] Furthermore, the various types of page function sub-modules include a retrieval solution module, a page modification solution module, a document extraction solution module, an API solution module, a table editing solution module and a drawing board solution module.

[0011] Furthermore, the generation of various SQL drivers for the sketchpad control of the database metadata page form prototype includes:

[0012] By pressing the corresponding search control on the drawing board module through the search scheme module, the search scheme Sql driver is generated for the database metadata page form prototype, and the database page form search scheme Sql driver statement is generated;

[0013] Through the page modification scheme module, press the corresponding page modification control on the drawing board module in the document extraction scheme module to generate the page modification Sql driver for the database metadata page form prototype, and generate the database page form modification scheme Sql driver statement;

[0014] Through the document extraction scheme module, press the corresponding document extraction control on the drawing board module to generate the document extraction Sql driver for the database metadata page form prototype, and generate the database page form document extraction scheme Sql driver statement;

[0015] Through the API solution module, press the corresponding API review control on the drawing board module to generate the API review Sql driver for the database metadata page form prototype, and generate the database page form API review Sql driver statement;

[0016] Press the corresponding table editing control on the drawing board module through the table editing solution module to generate the table editing Sql driver for the database metadata page form prototype, and generate the database page form table editing Sql driver statement;

[0017] Through the drawing board scheme module, press the corresponding drawing board review control on the drawing board module to generate the drawing board scheme review Sql driver for the database metadata page form prototype, and generate the database page form scheme review Sql driver statement.

[0018] Furthermore, the page form delay promotion driving execution of the database metadata page form prototype based on various database page form control Sql driving statements includes:

[0019] Conduct detailed and in-depth mining and analysis of various database page form control SQL driver statements to obtain the properties, types and interaction methods corresponding to various form control SQL driver statements; conduct driver dependency evaluation and analysis of various database page form control SQL driver statements based on the properties, types and interaction methods corresponding to various form control SQL driver statements to generate the relative driver execution dependency and execution data flow between various form control SQL driver statements;

[0020] Based on the relative driving execution dependency between various form control Sql driving statements, the driving duration between various database page form control Sql driving statements is monitored to generate the execution driving response duration between various form control Sql driving statements; according to the execution driving response duration between various form control Sql driving statements, the page driving response analysis is performed on the database metadata page form prototype to obtain the execution driving response efficiency of the Sql statement page form;

[0021] Based on the execution drive response time and execution data flow between various form control Sql drive statements, the drive delay evaluation and analysis between various database page form control Sql drive statements are performed to obtain the Sql drive statement execution delay;

[0022] Based on the SQL statement page form execution drive response efficiency and the SQL drive statement execution delay delay, the statement drive delay adjustment calculation formula is used to adjust and calculate the drive delay timing corresponding to the SQL drive statement of various database page form controls, so as to obtain the drive delay adjustment execution timing corresponding to the SQL drive statement of various form controls;

[0023] According to the driving delay adjustment execution timing corresponding to the SQL driving statements of various form controls, the corresponding database page form control SQL driving statements are processed by statement driving promotion, so as to obtain various database page form SQL driving delay promotion statements;

[0024] Based on various database page form Sql driver delay promotion statements, the database metadata page form prototype is driven to execute page form delay promotion to generate various form control delay promotion Sql execution statements, including maintenance Sql execution statements, document Sql execution statements, query Sql execution statements and audit Sql execution statements, wherein the maintenance Sql execution statements include page modification Sql execution statements and table editing Sql execution statements, wherein the page modification Sql execution statements include running Sql execution statements, subquery Sql execution statements, adding or modifying verification Sql execution statements and deleting Sql execution statements, document Sql execution statements include document selection Sql execution statements, summary Sql execution statements, detail Sql execution statements and post-Sql execution statements, query Sql execution statements include retrieval pre-Sql execution statements and retrieval post-Sql execution statements, and audit Sql execution statements include API audit Sql execution statements and form solution audit Sql execution statements.

[0025] Furthermore, the statement-driven delay adjustment calculation formula is specifically:

[0026]

[0027] Where Y i The driver delay adjustment execution timing corresponding to the SQL driver statement of the i-th form control, n is the total number of SQL driver statements of the form control, i is the item index of the SQL driver statement of the form control, The execution start time of the SQL driver statement corresponding to the i-th form control. is the end time of the execution of the SQL driver statement corresponding to the i-th form control, t is the statement execution time variable parameter, τ is the integral time component, D i (t) is the form control interaction complexity corresponding to the SQL driver statement of the i-th form control at time t, α i is the interaction complexity adjustment coefficient corresponding to the SQL driver statement of the i-th form control, is the execution resource consumption corresponding to the SQL driver statement of the i-th form control at time t, β i is the resource consumption impact adjustment coefficient corresponding to the SQL driver statement of the i-th form control, Q(τ) is the SQL statement page form execution driver response efficiency at time τ, t s Execution delay for SQL-driven statements, γi is the execution response delay weight coefficient corresponding to the SQL driver statement of the i-th form control, and η is the correction coefficient of the driver delay adjustment execution timing.

[0028] Furthermore, the maintenance driving operation of optimizing the database drawing board page layout form based on the maintenance SQL execution statement includes:

[0029] Based on the table editing Sql execution statement, the database artboard page layout optimization form is driven to execute the page form editing, and the page editing interpretation is executed according to the running Sql execution statement. Click the page editing run button to execute, and the execution result is displayed in the detailed table below the artboard module;

[0030] According to the sub-query SQL execution statement, the database drawing board page layout optimization form is driven by the sub-query execution, and the driver clicks the page sub-query run button to execute the configuration page form sub-query detail table;

[0031] According to the addition or modification of the verification SQL execution statement, the database drawing board page layout optimization form is added or modified to drive the execution. The driver clicks the page addition or modification run button to execute the corresponding database verification maintenance driver job before the page form is added or modified;

[0032] According to the delete SQL execution statement, the database drawing board page layout optimization form is deleted and driven to execute. The driver clicks the page form deletion run button to execute the page form deletion maintenance driver job.

[0033] Furthermore, the document expansion calculation driving operation of optimizing the database drawing board page layout form based on the document SQL execution statement includes:

[0034] Based on the document selection SQL execution statement, the database drawing board page layout optimization form is driven by document selection execution, and the driver clicks the document selection run button to execute the page document selection drive job;

[0035] Based on the summary SQL execution statement, the database drawing board page layout optimization form is driven to execute the document summary, and the driver clicks the document summary run button to execute the page document summary driving job;

[0036] Based on the detailed SQL execution statement, the database drawing board page layout optimization form is driven by the document details to select or summarize the corresponding detailed information of the page document and fill it into the document detail table below;

[0037] Based on the post-SQL execution statement, the database canvas page layout optimization form is modified and executed post-document.

[0038] Furthermore, the query-driven operation of optimizing the database drawing board page layout form based on the query SQL execution statement includes:

[0039] Based on the search pre-SQL execution statement, the database drawing board page layout optimization form is pre-searched to drive the execution of the corresponding page form summary and detailed summary operations;

[0040] Based on the post-search SQL execution statement, a post-search verification drive job is performed on the database page form after the pre-search.

[0041] Furthermore, the positive and negative review driving operation of optimizing the database drawing board page layout form based on the review SQL execution statement includes:

[0042] Perform API-driven review of the database artboard page layout optimization form based on the API review Sql execution statement;

[0043] Based on the form solution audit Sql execution statement, the database drawing board page layout optimization form after API drive is audited and the positive and negative audit driving operations corresponding to the audit opinions are performed.

[0044] Furthermore, the present invention also provides a data-driven low-code development method, which is applied to the data-driven low-code development platform as described above. The data-driven low-code development method includes the following steps:

[0045] Obtain the field name and field value corresponding to the business data to obtain the business database table metadata column; obtain the field type dictionary corresponding to the business data to generate the business database table field dictionary attribute; use the business database table metadata column and the business database table field dictionary attribute as database form metadata information;

[0046] Generate a page form based on the database form metadata information to generate a database metadata page form prototype;

[0047] Generate various SQL drivers for the drawing board controls of the database metadata page form prototype, and generate various SQL driver statements for the database page form controls; perform page form delay promotion driver execution on the database metadata page form prototype based on various database page form control SQL driver statements to generate various form control delay promotion SQL execution statements, including maintenance SQL execution statements, document SQL execution statements, query SQL execution statements, and review SQL execution statements;

[0048] Optimize the page layout design of the database metadata page form prototype to generate a database canvas page layout optimization form;

[0049] Based on the maintenance Sql execution statements, document Sql execution statements, query Sql execution statements and audit Sql execution statements, the database canvas page layout optimization form is maintained, the document expansion calculation, query and positive and negative audit drive operations are performed respectively, thereby driving the development to obtain the corresponding low-code development platform.

[0050] Beneficial effects of the present invention:

[0051] The data-driven low-code development platform proposed in the present invention is composed of a data foundation layer, a page data layer, a page function driving layer, a page presentation layer and a business data driving layer from bottom to top, wherein the data foundation layer includes a field module and a dictionary module, the page data layer includes a page front-end presentation unit, the page function driving layer includes a retrieval solution module, a page modification solution module, a document extraction solution module, an API solution module, a table editing solution module and a drawing board solution module, the page presentation layer includes a page post-design unit, and the business data driving layer includes a data maintenance module, a document module, a query module and an audit module. Compared with the prior art, the beneficial effect of the present application is that by obtaining the field names and field values ​​corresponding to the business data, a comprehensive understanding of the structure and attributes of the business data can be ensured, and the database table can be extracted through these field information. Metadata columns are the basis for building business database tables, covering every dimension of the data. By obtaining the field type dictionary, it provides a basis for the subsequent generation of database field dictionary attributes. The field type dictionary includes not only the data type, but also the length, precision, and whether the data is empty. These are the key elements to ensure that the database table can run effectively in practical applications. These metadata and field attribute information together constitute the unit data information of the database table, which provides a clear basis for the execution of subsequent steps. It systematically obtains and organizes the structured information of business data to ensure that the data is accurately and clearly reflected in the database table, and provides the necessary basic data for subsequent form generation, optimization, and execution, ensuring that the generated page form is highly consistent with the database table structure, thereby improving the accuracy and efficiency of platform data interaction. Secondly, the database form metadata information will be used to generate the database metadata page form prototype. The core of this process is to combine the metadata information with the page form structure to ensure that business data can be presented to users in a clear and intuitive manner. By generating page form prototypes based on field names, field types and field values, developers and business personnel can quickly understand the structure of the data and can quickly operate and modify it. Page form generation is not only the starting point of page design, but also a key step in the entire low-code development process. It greatly reduces the complexity and error rate of manual design and coding by automatically generating page form prototypes. Developers do not need to manually create form items corresponding to each field, and avoid manual adjustments due to changes in data structure, significantly improving platform development efficiency and page usability.Then, by generating SQL execution statements for various database page form controls based on the database metadata page form prototype, these SQL execution statements include maintenance SQL, document SQL, query SQL and audit SQL statements, which are the key to ensuring seamless connection between page forms and database operations. Specifically, maintenance SQL statements are used to update, insert or delete data in the database, document SQL statements are used to record documents in business processes, query SQL statements are used to retrieve form data from the database, and audit SQL statements are used to implement approval and audit operations in business processes. It automatically generates SQL execution statements by clicking on module controls and delaying the driver execution, thereby achieving a close binding of business logic and database operations. Through this automated drive, the workload of manually writing SQL statements is reduced, and errors caused by delays in the SQL statement driver execution process are avoided. The generation of SQL statements can be customized according to the actual needs of the page form to ensure that each page form control can perform precise database operations, thereby improving the data integration capabilities between the low-code platform and existing enterprise systems. Next, the database metadata page form prototype will undergo further page layout optimization design. The goal of this step is to ensure that the page form can not only display data correctly, but also provide users with a friendly interactive experience. The optimization design includes the arrangement, size, color matching of controls and the adjustment of the overall interface layout. The purpose is to improve the readability of the page and the convenience of operation. According to business needs and user feedback, the layout and style of the page form are carefully adjusted to ensure that the final interface meets the user experience standards and can efficiently complete data interaction. Finally, the database canvas page layout optimization form is driven by maintenance Sql execution statements, document Sql execution statements, query Sql execution statements, and audit Sql execution statements. Specifically, the purpose of this step is to perform actual data operations on the page form according to the Sql execution statements generated in the previous steps to ensure that the page form can smoothly add, delete, modify, and query data, and can support complex business processes such as forward and reverse audits in different business scenarios. This can realize the automated development function of the low-code platform. Through Sql drive, developers can quickly realize data interaction and business logic between the page and the database without writing a lot of code. Sql-driven execution statements can not only improve the execution efficiency of the development platform, but also greatly reduce the risk of errors caused by manual operations, thereby enhancing the overall flexibility and response speed. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments thereof made with reference to the following drawings:

[0053] Figure 1This is a schematic diagram of the module layer structure of the data-driven low-code development platform of the present invention;

[0054] Figure 2 This is a schematic diagram of the driving structure of the data maintenance module of the present invention;

[0055] Figure 3 This is a schematic diagram of the driving structure of the document module of the present invention;

[0056] Figure 4 This is a schematic diagram of the driving structure of the query module of the present invention;

[0057] Figure 5 It is a schematic diagram of the driving structure of the audit module of the present invention. DETAILED DESCRIPTION

[0058] The technical method of the present invention is described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by technicians in this field without creative work are within the scope of protection of the present invention.

[0059] To achieve this, please refer to Figures 1 to 5 The present invention provides a data-driven low-code development platform. In the embodiments of the present invention, please refer to Figure 1 As shown, it is a schematic diagram of the module layer structure of the data-driven low-code development platform of the present invention. In this example, the low-code development platform includes the following module layers from bottom to top:

[0060] The data foundation layer includes a field module and a dictionary module, wherein the field module is used to obtain the field name and field value corresponding to the business data to obtain the business database table metadata column; the dictionary module is used to obtain the field type dictionary corresponding to the business data to generate the business database table field dictionary attributes; the business database table metadata column and the business database table field dictionary attributes are used as database form metadata information;

[0061] In an embodiment of the present invention, the data foundation layer corresponding to the low-code development platform is composed of a field module and a dictionary module, wherein the field module extracts the metadata column (that is, the corresponding field name and field value) corresponding to the data table from the business data to execute SQL query statements such as SELECT column_name, column_value FROM<business_table> , get the field name (column_name) and the corresponding field value (column_value) of the database table. These data reflect the actual storage structure of the business data. The field name indicates the name of each column in the database table, and the field value indicates the data of each column. Through the API connecting to the database, these metadata are extracted from the database and organized into a field list. These field names and field values ​​will serve as the basis for generating the database form data structure in the subsequent steps, thereby obtaining the business database table metadata column. The dictionary module obtains the type dictionary information of each field to execute SELECT column_name,data_type FROM information_schema.columns WHERE table_name='<business_table> 'Such a query statement can obtain the type of each field from the metadata table of the database (such as information_schema.columns). The dictionary of field types is composed of field names and their corresponding data types (such as VARCHAR, INT, DATE, etc.). This dictionary is crucial when generating field attributes because it helps understand how each field should be rendered in the form. For example, the selection of controls such as text boxes, date selection boxes, and drop-down boxes will depend on the field type, thereby generating the dictionary attributes of the business database table field. At the same time, the data foundation layer generates the "unit data information" of the database table by aggregating the previously obtained field names, field values, field types and other information. This information includes the basic name of the field, the data value, and the type characteristics of the field. The metadata information of all fields will form a data structure, such as a dictionary or JSON object, which represents all columns in the database table and their corresponding attributes. This data structure provides the necessary basis for subsequent page generation. It not only contains the attributes of each field, but also contains relevant information on how these fields are displayed on the interface (such as the control type), and finally obtains the database form metadata information.

[0062] Preferably, the page data layer includes a page front-end representation unit corresponding to the drawing board module, which is used to generate a page form for the database form metadata information to generate a database metadata page form prototype;

[0063] In an embodiment of the present invention, a page data layer corresponding to the low-code development platform is constituted by a page front-end representation unit corresponding to the drawing board module. The page front-end representation unit automatically generates a prototype of the database form according to the previously generated database form metadata information, and determines the presentation form of each field in the form by parsing the metadata of each field, such as field type, length, etc. For text fields, a text box will be generated; for date fields, a date selection control will be generated; for numeric fields, a numeric input box will be generated, etc. These form controls will generate a preliminary database form prototype according to the business logic and user interface specifications. The generated page form prototype does not contain all the details, but it provides a structured interface layout and can support subsequent optimization and adjustment, and finally generates a database metadata page form prototype.

[0064] Preferably, the page function driver layer includes various page function sub-modules, which are used to generate various Sql drivers of the drawing board control for the database metadata page form prototype, and generate various database page form control Sql driver statements; based on various database page form control Sql driver statements, the database metadata page form prototype is driven to perform page form delay promotion to generate various form control delay promotion Sql execution statements, including maintenance Sql execution statements, document Sql execution statements, query Sql execution statements and review Sql execution statements;

[0065] In an embodiment of the present invention, a page function driver layer corresponding to the low-code development platform is composed of various page function sub-modules (i.e., a retrieval solution module, a page modification solution module, a document extraction solution module, an API solution module, a table editing solution module, and a drawing board solution module). The page function driver layer analyzes and designs the database metadata page form prototype. Each form prototype corresponds to a specific database entity. The metadata defines the attributes, field types, constraints, and relationships of these entities. Prototype design is performed using professional graphical drawing board tools (such as UI design tools) to construct form module controls on the user interface (such as a retrieval solution module, a page modification solution module, a document extraction solution module, an API solution module, a table editing solution module, and a drawing board solution module, etc.). Once the prototypes of these controls are After being created, the next task is to generate the corresponding SQL driver statements. During the specific implementation, the development tool will automatically generate SQL operation statements corresponding to each control, such as INSERT, UPDATE, DELETE, SELECT, etc., according to the type of form control and the structure of the database table. The SQL driver statements of each control will interact at the database level to ensure that data can be correctly added, deleted, modified, and checked. When generating SQL statements, the tool will ensure that the SQL statements follow the constraints and field types of the database, especially in data type conversion and field mapping, avoiding manual coding errors and inconsistencies. In this way, developers do not need to manually write SQL, but only need to generate corresponding SQL drivers by dragging controls and selecting fields, thereby generating SQL driver statements for various database page form controls. At the same time, the previously generated SQL-driven statements are further optimized and designed for delayed execution through the development tool. In this process, different SQL execution requirements are first distinguished. For example, maintenance SQL execution statements are used for data addition and update operations, document SQL execution statements are used for specific document generation and processing, query SQL execution statements are used to display data and filter, and audit SQL execution statements are executed for the data audit process. Each type of SQL statement will be embedded in the event-driven logic of the form control, such as the submit button, query button, etc. The tool will design a delayed execution mechanism for each operation (addition, query, audit, etc.), that is, to delay the actual execution of SQL through certain trigger conditions (such as user operations, page loading, etc.). This delayed execution mechanism can avoid unnecessary database operations, optimize page loading and response time, and improve user experience. In specific implementation, the database-driven tool will perform syntax checks on each SQL statement to ensure that the generated SQL statement has no syntax errors, and prevent security issues such as SQL injection through parameterized queries. Finally, it optimizes the generation of various form controls to delay and improve SQL execution statements.

[0066] Preferably, the page presentation layer includes a page post-design unit corresponding to the drawing board module, which is used to optimize the page layout design of the database metadata page form prototype to generate a database drawing board page layout optimization form;

[0067] In an embodiment of the present invention, a page presentation layer corresponding to the low-code development platform is constructed through a page post-design unit corresponding to the drawing board module. The page presentation layer mainly focuses on the visual performance of the form and the improvement of the interactive process through the layout optimization design of the database drawing board page. In order to improve the convenience and readability of user operations, the layout of the form will be carefully adjusted through the layout drag function in the database drawing board module. It allows users to design and adjust the layout of the application interface through intuitive drag and drop operations. This function greatly simplifies the interface design process, allowing non-professional developers to easily create complex application interfaces. For example, the arrangement of fields, the size of controls, the display position of labels, the color matching of forms, etc. will all be adjusted. Optimize according to specific needs. The tool will automatically adjust the position and size of each control according to the field information, field length and type of the database table to avoid the interface being too crowded or difficult to operate. At the same time, based on the user's interaction habits, the tool will also design a responsive layout of controls to ensure that the form can be displayed correctly on different screen sizes. In addition, appropriate input validation rules will be set for each form control to ensure that the data format entered by the user complies with database constraints, such as the maximum length of text fields, the valid range of numeric fields, etc. Through these layout optimizations, the database page form can meet the standards of efficiency and ease of use in both visual and functional aspects, and finally design and generate a database canvas page layout optimized form.

[0068] Preferably, the business data driving layer includes a data maintenance module, a document module, a query module and an audit module, wherein the data maintenance module is used to perform maintenance driving operations on the database drawing board page layout optimization form based on the maintenance Sql execution statement; the document module is used to perform document expansion calculation driving operations on the database drawing board page layout optimization form based on the document Sql execution statement; the query module is used to perform query driving operations on the database drawing board page layout optimization form based on the query Sql execution statement; the audit module is used to perform positive and negative audit driving operations on the database drawing board page layout optimization form based on the audit Sql execution statement.

[0069] In the embodiment of the present invention, the business data driving layer corresponding to the low-code development platform is composed of a data maintenance module, a document module, a query module and an audit module, wherein the data maintenance module (such as Figure 2 As shown in the figure, the maintenance and modification of the database form is triggered by the previously generated maintenance SQL execution statement, which usually involves the addition and modification of data. The development tool generates specific SQL statements to insert and update data. The document module (such as Figure 3 As shown in the figure), the document expansion calculation is performed based on the document SQL execution statement, which is mainly used to generate and display specific business documents, such as invoices, orders, etc. At this time, the corresponding view will be generated according to the document template and related database records, and the relevant data will be automatically filled in; the query module performs query operations based on the query SQL execution statement, which generates dynamic query SQL statements according to the conditions entered by the user, and returns the data results that meet the conditions. The query statement will be optimized according to factors such as field type and index to improve query efficiency; the audit module performs audit operations based on the audit SQL execution statement, which generates SQL statements according to business rules to perform positive and negative audits of data, that is, "audit opinions". For example, in the positive audit stage, based on the feedback information provided by the automatic audit, it is judged whether the optimized form layout meets the project requirements to ensure the accuracy of page display and data interaction. Each element in the form will be confirmed to check the consistency of the layout and data, and at the same time confirm the SQL execution Whether the statement can be correctly bound to the front-end page elements. If there is no problem, confirm "review passed" through the system interface and trigger the subsequent form deployment process. In the reverse review stage, if problems are found in the form layout or SQL execution statement, such as non-compliant field positions, data query logic errors, or abnormal page display, reverse review can be triggered. The modification points will be prompted to modify the SQL execution statement or adjust the form layout according to the prompts. After the modification is completed, it will be reviewed again and the modified feedback results will be returned. Each SQL operation will be embedded in the corresponding form control to ensure that the correct SQL statement execution can be triggered when the user clicks the corresponding button. In addition, the development tool will automatically handle the parameter binding between form controls and SQL statements to ensure data consistency and correctness and reduce errors in manual intervention. Finally, the low-code platform will generate a complete background logic based on these business operations. Developers only need to perform a small amount of configuration to realize the operation of the entire low-code development platform.

[0070] Furthermore, the various types of page function sub-modules include a retrieval solution module, a page modification solution module, a document extraction solution module, an API solution module, a table editing solution module and a drawing board solution module.

[0071] Furthermore, the generation of various SQL drivers for the sketchpad control of the database metadata page form prototype includes:

[0072] By pressing the corresponding search control on the drawing board module through the search scheme module, the search scheme Sql driver is generated for the database metadata page form prototype, and the database page form search scheme Sql driver statement is generated;

[0073] In the embodiment of the present invention, through the corresponding search control on the drawing board module of the search scheme module, the user can perform a search operation on the database metadata page form prototype. Specifically, it is necessary to first select the search control and configure it on the drawing board. The control allows the input of the database table name, field name and corresponding search conditions. The caller module will automatically generate an SQL statement according to the search conditions entered by the user to drive the database to perform the search operation. After execution, it is determined according to the configuration whether to return the result to the caller module. If the result is returned, the caller module will determine to fill in the relevant drawing board module and detailed table control. The data drive in the search scheme configuration mainly involves the front-end SQL and the post-S ql, the front-end Sql is used to implement the retrieval function, and the post-Sql is used for verification or other functions after retrieval, which is determined by the Sql configuration personnel. The structure of the SQL statement is to automatically build the query conditions and generate the corresponding SELECT statement by analyzing the metadata of the database table (such as field type, field constraints, etc.). For example, if the user sets the retrieval condition to "age>30", the generated SQL statement will include the condition "WHEREage>30". The generated SQL statement will be executed in the background to retrieve the data in the database table and return the query results to the user for display, which will eventually drive the generation of the database page form retrieval solution Sql driver statement.

[0074] Preferably, the page modification scheme module presses the corresponding page modification control on the drawing board module in the document extraction scheme module to generate a page modification Sql driver for the database metadata page form prototype, and generates a database page form modification scheme Sql driver statement;

[0075] In an embodiment of the present invention, the operation is performed through the corresponding page modification control on the drawing board module of the page modification scheme module, the purpose of which is to modify the page form prototype of the database metadata page, and the design principle of the page modification scheme is to obtain data from the drawing board or the document detail table in the document module, and these data will be substituted into the SQL statement stored in the page modification scheme. After the SQL statement in the page modification scheme is executed in the document module, if the SQL statement modifies the two temporary tables (summary temporary table or detail temporary table) associated with the page modification scheme, and the tool platform is configured to write back the summary or write back the details, then the execution result related information will fill in the drawing board data or detail data on the document module. In the specific operation, the user sets the modification content through the page modification control on the drawing board, such as modifying the default value, field length or type of the field, and the corresponding UPDATE SQL statement is automatically generated according to the user's modification requirements. For example, if the user modifies the default value of the "age" field to "25", an UPDATE statement will be automatically generated, such as: "UPDATE table_name SETage=25WHERE id=?" This SQL statement will drive the database to update the value of the corresponding form field. It will verify whether the input modification is legal according to the structure and data type of the database table, ensure that the generated SQL statement meets the constraints of the database, and finally drive the generation of the database page form modification solution Sql driver statement.

[0076] Preferably, the document extraction scheme module is used to press the corresponding document extraction control on the drawing board module to generate the document extraction Sql driver for the database metadata page form prototype, and generate the database page form document extraction scheme Sql driver statement;

[0077] In the embodiment of the present invention, the document extraction control on the drawing board module of the document extraction scheme module can extract the specified document data from the database metadata page form prototype, and the module mainly stores several categories of Sql statements. When the button control is clicked, these Sql statements are executed to obtain the results, so as to achieve the purpose of data-driven. The document extraction scheme module maintains these categories of Sql statements: document selection Sql, summary Sql, detail Sql, post-position Sql, etc. The document selection Sql is responsible for the overall Sql basic statements of the document extraction scheme, and its function is to retrieve the basic results. The summary SQL and detail SQL will make further inquiries based on the conditions of certain columns in this result, and the summary information will be filled into the corresponding control of the drawing board, and the detail information will be filled into the document detail table below. In the specific operation, first select the document extraction control in the drawing board module and define the extraction conditions. The SQL statement will be generated according to the conditions set by the user, usually a SELECT statement containing a WHERE clause. For example, when the user sets the extraction condition to "status = 'approved'", the generated SQL statement is: "SELECT * FROM table_name WHERE status = 'approved'". At this time, the database background extracts the document data that meets the conditions according to the generated SQL statement, and returns the result to the user interface for further operation or display. Finally, it drives the generation of the database page form document extraction solution SQL driver statement.

[0078] Preferably, the API solution module presses the corresponding API review control on the drawing board module to generate an API review Sql driver for the database metadata page form prototype, and generates a database page form API review Sql driver statement;

[0079] In an embodiment of the present invention, an API audit can be performed on the database metadata page form prototype through the API audit control on the drawing board module of the API solution module. By selecting the control and setting relevant audit conditions, a corresponding SQL statement will be automatically generated to verify whether the form data of the API call meets the preset conditions. In the specific implementation process, an audit-driven SQL statement will be generated according to the audit standards configured by the user (such as API form data format, form parameter legitimacy, etc.). For example, if the user wants to verify whether the "status" field is in the "approved" state, the generated SQL statement is: "SELECT*FROMtable_name WHERE status='approved'". The audit process will call the generated SQL statement to verify whether the data in the database meets the specified audit standards, ensure whether to enter the subsequent form positive and negative audit work, and finally drive the generation of the database page form API audit Sql driver statement.

[0080] Preferably, the table editing solution module presses the corresponding table editing control on the drawing board module to generate a table editing Sql driver for the database metadata page form prototype, and generates a database page form table editing Sql driver statement;

[0081] In an embodiment of the present invention, a table editing operation can be performed on the database metadata page form prototype through the table editing control on the drawing board module of the table editing solution module. By selecting the table editing control and setting the table fields that need to be modified, such as adding new columns, modifying column names or adjusting column order, an ALTER TABLE statement will be automatically generated according to the user's modification requirements to modify the table structure in the database. For example, if the user requires adding an "email" field to the original table, the generated SQL statement is: "ALTER TABLE table_name ADD email VARCHAR(255)". This SQL statement will be executed, and the database table structure will be modified accordingly according to user requirements. The SQL statement will also be checked according to requirements such as data type and field length to ensure that all modifications comply with the structural constraints of the database, and finally drive the generation of the database page form table editing Sql driver statement.

[0082] Preferably, the corresponding drawing board review control on the drawing board module is pressed through the drawing board solution module to perform drawing board solution review Sql driver generation on the database metadata page form prototype, and generate the database page form solution review Sql driver statement.

[0083] In an embodiment of the present invention, a drawing board review control on the drawing board module of the drawing board solution module can be used to review the database metadata page form prototype. First, the drawing board review control is selected according to the non-compliant results of the previous API call review, and the review rules and parameters are set. According to the rules set by the user, a corresponding SQL statement is generated to check whether the form data meets the review standards. For example, the user can set an audit condition: only when the "amount" field is greater than 1000 can it be submitted. The automatically generated SQL statement is: "SELECT*FROM table_name WHEREamount>1000". When this SQL statement is executed, it will verify whether the form data meets the review rules. Only data that meets the conditions will be submitted or saved. This review process can ensure that data processing complies with business processes and rule requirements, and ultimately drives the generation of database page form solution review Sql driver statements.

[0084] Furthermore, the page form delay promotion driving execution of the database metadata page form prototype based on various database page form control Sql driving statements includes:

[0085] Conduct detailed and in-depth mining and analysis of various database page form control SQL driver statements to obtain the properties, types and interaction methods corresponding to various form control SQL driver statements; conduct driver dependency evaluation and analysis of various database page form control SQL driver statements based on the properties, types and interaction methods corresponding to various form control SQL driver statements to generate the relative driver execution dependency and execution data flow between various form control SQL driver statements;

[0086] In an embodiment of the present invention, by performing a refined and in-depth mining and analysis on the SQL driving statements of various database page form controls, firstly, by parsing the SQL driving statements of each form control line by line, the tables, fields, conditions, connections, sorting and other SQL syntax details involved are obtained. In specific operations, a database query analysis tool is used to capture and analyze the SQL statements triggered by the events of each form control (such as input boxes, drop-down boxes, buttons, etc.). For each SQL statement, its field type (for example: integer, string, date, etc.), input attributes (such as: single-line text, multi-line text, check box options, etc.) and interaction methods (such as: add, delete, modify, and query operations) are extracted. In this way, the attributes and execution methods of SQL driving statements can be systematically identified, ensuring that the relationship between each control and SQL is accurately described and classified, thereby obtaining the attributes, types and interaction methods corresponding to the SQL driving statements of various form controls. At the same time, based on the properties, types and interaction methods of each SQL statement obtained from the previous analysis, a dependency graph between SQL-driven statements is drawn. The graph reflects how different form controls influence each other, transfer data and dependencies through SQL statements. For example, the selection of a certain control will affect the display content of other controls (such as a linked drop-down box), or the input data of a control will be passed as a condition to the query SQL of subsequent controls. By using dependency analysis tools, the relative execution order, data flow direction and response mechanism of each control between SQL statements are detected, thereby generating a visual driver dependency relationship. The dependency evaluation process also needs to detect whether there is a circular dependency or a tightly coupled driver relationship. If so, it is necessary to optimize by adjusting the design structure or SQL statements. Finally, the relative driver execution dependency and execution data flow between various form control SQL-driven statements are analyzed and generated.

[0087] Preferably, based on the relative drive execution dependency relationship between various form control Sql drive statements, drive duration monitoring is performed between various database page form control Sql drive statements to generate the execution drive response duration between various form control Sql drive statements; according to the execution drive response duration between various form control Sql drive statements, page drive response analysis is performed on the database metadata page form prototype to obtain the Sql statement page form execution drive response efficiency;

[0088] In an embodiment of the present invention, the driving time between SQL driving statements of various database page form controls is monitored based on the dependency relationship between SQL driving statements. First, the execution time between each SQL driving statement and the next SQL driving statement is quantitatively measured. By setting a monitoring tool, the time from the completion of the triggering execution of each SQL statement to the triggering of the next SQL statement is recorded, and based on the dependency relationship of the SQL statements, the influencing factors of the triggering time of each control are analyzed. For example, when the input of a control affects the execution of multiple SQL statements, the monitoring tool will record the overall time from the triggering of the control to the execution of all related SQL statements, and calculate the response time of each SQL statement on this basis. This process ensures that the execution time lag between SQL driving statements can be monitored in real time, thereby generating the execution driving response time between various form control SQL driving statements. At the same time, by deeply analyzing the response time of each form control based on the execution time of each SQL driving statement previously recorded, for each control input or trigger operation, the overall driving response time of the operation to the database query response time (that is, SQL statement generation time), data return time and page display time is calculated, thereby quantifying the form control response efficiency, that is, the page Finally, the SQL statement page form execution driver response efficiency is obtained.

[0089] Preferably, based on the execution drive response time and execution data flow between various form control Sql drive statements, the drive time delay evaluation and analysis between various database page form control Sql drive statements are performed to obtain the Sql drive statement execution time delay;

[0090] In an embodiment of the present invention, the SQL-driven statement execution delay of each form control is calculated to analyze the time difference between the trigger operation of each control and the SQL execution according to the previously recorded SQL execution response time and the identified data flow direction. In a specific operation, a performance analysis tool is used to measure the SQL statement execution delay in segments, record the time required for each stage of SQL statement execution (such as query preparation, data processing, result return, etc.), and evaluate the impact of each form control on the SQL-driven delay based on the data flow direction. If it is found that the trigger operation of a certain control causes an obvious delay, it is necessary to optimize the related SQL statement (for example, optimize the index, reduce the query complexity, etc.). This process ensures that the execution efficiency of the SQL-driven statement is maximized by evaluating the delay, and finally obtains the SQL-driven statement execution delay.

[0091] Preferably, based on the Sql statement page form execution drive response efficiency and the Sql drive statement execution time delay, the statement drive delay adjustment calculation formula is used to adjust and calculate the drive delay timing corresponding to the Sql drive statement of each database page form control, so as to obtain the drive delay adjustment execution timing corresponding to the Sql drive statement of each form control;

[0092] In an embodiment of the present invention, a suitable statement-driven delay adjustment calculation formula is formed by combining the number parameter of the form control Sql-driven statement, the statement execution start time, the statement execution end time, the time variable parameter, the form control interaction complexity, the interaction complexity impact adjustment coefficient, the execution resource consumption, the resource consumption impact adjustment coefficient, the Sql statement page form execution drive response efficiency, the Sql-driven statement execution lag delay, the execution response lag delay weight coefficient and related parameters to adjust and calculate the drive delay timing corresponding to the various database page form control Sql-driven statements, so as to calculate the best adjustment timing, optimize the execution order and trigger timing of the database Sql statement, reduce the delay when the page is loaded, and finally obtain the drive delay adjustment execution timing corresponding to the various form control Sql-driven statements.

[0093] Preferably, according to the driving delay adjustment execution timing corresponding to each type of form control Sql driving statement, the corresponding database page form control Sql driving statement is subjected to statement driving promotion processing to obtain each type of database page form Sql driving delay promotion statement;

[0094] In an embodiment of the present invention, the corresponding database page form control SQL driven statement is statement driven improvement processing is performed by adjusting the execution timing according to the previously quantified delay of the SQL driven statement, analyzing the execution plan of each SQL statement, and identifying the SQL statement with performance bottleneck. For example, if the execution delay of some SQL statements is too long, resulting in slow response of the form control, it is necessary to optimize its performance by adjusting its execution logic, improve the execution speed of SQL statements by optimizing the query index, reducing the data set scanning, or using more efficient query syntax (such as avoiding unnecessary nested queries or redundant JOIN operations), and fine-tune the SQL statement by using performance monitoring tools (such as database log analysis, SQL optimization tools) to ensure that the execution order is reasonable and avoid unnecessary database operations. By adjusting the query conditions of the SQL statement, modifying the execution order or splitting complex queries, each SQL statement can get a faster response at the new execution time, thereby improving the execution efficiency of the overall form control and reducing the delay of repeated queries, and finally obtaining various database page form SQL driven delay improvement statements.

[0095] Preferably, based on various database page form Sql driven delayed promotion statements, the database metadata page form prototype is driven to execute page form delayed promotion to generate various form control delayed promotion Sql execution statements, including maintenance Sql execution statements, document Sql execution statements, query Sql execution statements and audit Sql execution statements, wherein the maintenance Sql execution statements include page modification Sql execution statements and table editing Sql execution statements, wherein the page modification Sql execution statements include running Sql execution statements, sub-query Sql execution statements, adding or modifying verification Sql execution statements and deleting Sql execution statements, the document Sql execution statements include document selection Sql execution statements, summary Sql execution statements, detail Sql execution statements and post-Sql execution statements, the query Sql execution statements include retrieval pre-Sql execution statements and retrieval post-Sql execution statements, and the audit Sql execution statements include API audit Sql execution statements and form solution audit Sql execution statements.

[0096] In an embodiment of the present invention, by performing page form delay promotion driven execution on the database metadata page form prototype based on various SQL-driven delay promotion statements that have been previously delayed, it is necessary to identify all SQL execution statements involved, especially SQL statements of maintenance, document, query and audit types in the page, and these SQL statements correspond to different database operation types, for example: maintenance operations include page modification SQL (such as update statements for modifying page content) and table editing SQL (such as add, delete and modify operations of table data); document operations include document selection SQL (such as document content query statements) and summary SQL (such as data summary statistics statements); query operations include pre-query SQL and post-query SQL (such as data retrieval operations before and after page loading); audit operations include API audit SQL and form scheme audit SQL. Core SQL (such as: review and approval operations of the background system), for each type of SQL execution statement, by comparing its execution time with the delay improvement requirements, optimize the execution strategy of SQL statements, adjust its execution order, reduce unnecessary waiting and data transmission delays, specific operation methods include asynchronous processing of page modification and table editing operations to avoid waiting for data updates when the page is loaded; execute query operations in segments to avoid page freezes caused by executing too many query operations at one time; for review-related operations, optimize the response time of the API call interface, and combine the transaction processing mechanism to ensure data consistency. All optimized SQL statements will be executed on demand during the form loading process, thereby greatly improving the overall response speed and interactive performance of the page, ensuring that the response delay of various form controls is effectively improved, and finally driving the generation of various form control delay improvement SQL execution statements.

[0097] Furthermore, the statement-driven delay adjustment calculation formula is specifically:

[0098]

[0099] Where, T i The driver delay adjustment execution timing corresponding to the SQL driver statement of the i-th form control, n is the total number of SQL driver statements of the form control, i is the item index of the SQL driver statement of the form control, The execution start time of the SQL driver statement corresponding to the i-th form control. is the end time of the execution of the SQL driver statement corresponding to the i-th form control, t is the statement execution time variable parameter, τ is the integral time component, D i (t) is the form control interaction complexity corresponding to the SQL driver statement of the i-th form control at time t, α i is the interaction complexity adjustment coefficient corresponding to the SQL driver statement of the i-th form control, is the execution resource consumption corresponding to the SQL driver statement of the i-th form control at time t, β i is the resource consumption impact adjustment coefficient corresponding to the SQL driver statement of the i-th form control, Q(τ) is the SQL statement page form execution driver response efficiency at time τ, t s Execution delay for SQL-driven statements, γ i is the execution response delay weight coefficient corresponding to the SQL driver statement of the i-th form control, and η is the correction coefficient of the driver delay adjustment execution timing.

[0100] The present invention obtains a statement-driven delay adjustment calculation formula by using a specific mathematical model and after verification, which is used to adjust and calculate the driving delay timing corresponding to the Sql driving statements of various database page form controls. The statement-driven delay adjustment calculation formula integrates multiple factors (such as interaction complexity, resource consumption, execution response lag, etc.) to calculate the driving delay adjustment execution timing of each type of form control Sql driving statement. This precise timing adjustment can ensure that the execution of the Sql driving statement is more optimized, reduce unnecessary waiting and resource waste, and thus improve the overall response efficiency of the low-code development platform. The interaction complexity is used to measure the complexity of the form control, which affects the execution time of the Sql driving statement. By modeling the interaction complexity of different form controls, the formula can adjust the execution timing according to the complexity of the control, avoiding the performance bottleneck caused by high-complexity interaction, and the interaction complexity impact adjustment coefficient further reflects the actual impact of the interaction complexity at a specific time, ensuring that the calculated delay adjustment is more targeted. The execution resource consumption and resource consumption impact adjustment coefficient indicate the impact of resource consumption on the execution of SQL statements. The formula can adjust the execution timing in a timely manner according to the dynamic changes of the current resource consumption, thereby avoiding excessive occupation of system resources and improving system stability and concurrent processing capabilities. Q(τ) is used to represent the page form execution efficiency at different time points. By considering the response efficiency, the formula can continuously optimize the timing adjustment during the execution process to ensure efficient execution and avoid delays during the peak of system load. At the same time, the SQL driver statement execution delay and execution response delay weight coefficient in the formula comprehensively consider the delay factors during execution. It ensures that when calculating the driver delay, the impact of the delay is weighed at the same time, helping to identify and adjust the statements with delays, and further optimize the execution timing. In addition, the introduction of the correction coefficient is used to fine-tune and correct the output of the formula to ensure that the adjustment result closely matches the actual situation. The correction coefficient can be adjusted in a timely manner according to the actual operating conditions to ensure the applicability and effect of the formula. In summary, the formula fully considers the driver delay adjustment execution timing T corresponding to the SQL driver statement of the i-th form control i , the total number of form control SQL driver statements n, the item index i of the form control SQL driver statement, the execution start time of the statement corresponding to the i-th form control SQL driver statement The execution end time of the SQL driver statement corresponding to the i-th form control Statement execution time variable parameter t, integral time component τ, form control interaction complexity D corresponding to the SQL driver statement of the i-th form control at time t i (t), the interaction complexity adjustment coefficient α corresponding to the SQL driver statement of the i-th form control i , the execution resource consumption corresponding to the SQL driver statement of the i-th form control at time t The resource consumption impact adjustment coefficient β corresponding to the SQL driver statement of the i-th form control i , the SQL statement page form execution driven response efficiency Q(τ) at time τ, the SQL driven statement execution delay t s , the execution response delay weight coefficient γ corresponding to the SQL driver statement of the i-th form control i , the correction coefficient η of the driver delay adjustment execution timing, according to the driver delay adjustment execution timing T corresponding to the SQL driver statement of the i-th form control i The correlation between the above parameters constitutes a functional relationship This formula can realize the adjustment calculation process of the driver delay timing corresponding to the SQL driver statements of various database page form controls. At the same time, by introducing the correction coefficient η of the driver delay adjustment execution timing, it can be adjusted according to the error situation occurring in the calculation process, thereby improving the accuracy and applicability of the statement driver delay adjustment calculation formula.

[0101] Furthermore, the maintenance driving operation of optimizing the database drawing board page layout form based on the maintenance SQL execution statement includes:

[0102] Based on the table editing Sql execution statement, the database artboard page layout optimization form is driven to execute the page form editing, and the page editing interpretation is executed according to the running Sql execution statement. Click the page editing run button to execute, and the execution result is displayed in the detailed table below the artboard module;

[0103] In an embodiment of the present invention, the page form editing is driven and executed on the database canvas page layout optimization form based on the table editing SQL execution statement to identify the table control in the page and the corresponding database table structure, and the defined table editing SQL statement is used to drive the pressing of the "Edit" button. In the canvas module, by binding the interaction logic between the table editing SQL statement and the form control, when the user clicks the "Edit" button in the page, the corresponding SQL statement is automatically triggered to edit the table content, such as UPDATE, INSERT, DELETE, etc. During the execution process, the SQL statement is parsed and run by the back-end server, and the result is returned to the low-code front-end interface. The specific operation is to use the low-code platform (such as Node-RED or a similar database driver development tool) to configure the database connection and SQL execution logic, and feed back the page form operation (such as modification, deletion, and addition) to the database through SQL execution instructions. The execution result is displayed at the bottom of the page through a graphical interface, that is, in the detailed table, and the update result of the database operation is displayed in real time. For example, if the user enters new data in the table, the result after execution will be displayed in real time in the page table to ensure that the user can see the change in time.

[0104] Preferably, the database drawing board page layout optimization form is subquery-driven and executed according to the subquery SQL execution statement, and the page subquery run button is driven to execute the configuration page form subquery detail table;

[0105] In an embodiment of the present invention, a subquery-driven execution is performed on the database drawing board page layout optimization form according to the subquery SQL execution statement generated by the response to determine the fields or data items in the form that need to execute the subquery. The execution of the subquery is performed by setting a trigger condition in the page control, such as a "query" button. When the button is clicked, the subquery SQL statement will be executed. Usually, this subquery will be nested in the main query statement, for example, using a SELECT statement to query certain detailed information in the database. These subqueries may include complex condition filtering, data aggregation and other operations, and use database query optimization tools, such as MySQL's EXPLAIN plan or SQL Server's query analysis tool, to ensure the efficiency of subquery execution. When the subquery statement is executed, the result will drive the update of the detailed table or list view on the page. For example, if a form needs to display the detailed information of a user, after clicking the "subquery" button, the page will automatically display the detailed record of the user, and any data changes will be reflected below the table.

[0106] Preferably, according to the addition or modification of the verification Sql execution statement, the database drawing board page layout optimization form is added or modified to drive the execution, and the driver clicks the page addition or modification run button to execute the corresponding database verification maintenance drive job before the page form is added or modified;

[0107] In an embodiment of the present invention, the database drawing board page layout optimization form is added or modified by driving the execution according to the addition or modification verification SQL execution statement, so as to determine which fields need data verification according to the type of page control (for example: text box, drop-down box, date selector, etc.). The addition or modification operation usually involves inserting or updating the data in the database. In specific implementation, SQL statements such as INSERT INTO and UPDATE are used to add or modify the data. Before performing this operation, the SQL statement is verified to ensure that the data entered by the user meets the constraints of the database form. This verification operation is usually triggered by triggering the click event of the "add" or "modify" button. In actual operation, the SQL statement will check the integrity of the data in the database, such as checking whether the required fields are empty, whether the data types match, and whether the data range is reasonable. If the data verification is successful, the subsequent insertion or update operation will continue to be executed. If the verification fails, the operation will be blocked and the corresponding error message will be displayed. For example, if the form requires a valid email address to be entered, when adding or modifying, the SQL statement will be used to verify the email format to ensure that the data meets the specifications, and finally the corresponding database verification maintenance drive job before the page form is added or modified is executed.

[0108] Preferably, the database drawing board page layout optimization form is deleted and driven to execute according to the delete Sql execution statement, and the driver clicks the page form deletion run button to execute the page form deletion maintenance drive job.

[0109] In an embodiment of the present invention, the database canvas page layout optimization form is deleted and driven to execute according to the deletion SQL execution statement to confirm the records or entries that need to be deleted in the page. These operations are usually associated with the delete button provided in the form. After the user clicks the button, the corresponding deletion SQL statement will be triggered. The deletion operation generally uses the DELETE statement to remove the specified data record from the database. Before executing the deletion operation, data verification and confirmation will be performed, such as confirming whether to delete a certain data row in a specific form. The deletion SQL statement usually has conditional constraints to ensure that only records that meet specific conditions are deleted. For example, in an order management system, when deleting an order, the SQL statement will perform a deletion operation based on the order ID. In the low-code development platform, the triggering of the deletion operation is combined with the data operation in the database table, and the SQL statement is called through the back-end interface for actual execution. After the operation is completed, the page will reflect the deletion results in real time, remove the corresponding data rows, and update the form view.

[0110] Furthermore, the document expansion calculation driving operation of optimizing the database drawing board page layout form based on the document SQL execution statement includes:

[0111] Based on the document selection SQL execution statement, the database drawing board page layout optimization form is driven by document selection execution, and the driver clicks the document selection run button to execute the page document selection drive job;

[0112] In an embodiment of the present invention, by combining the document selection SQL execution statement generated by the previous response, the driving operation of the database canvas page layout optimization form is performed. The specific implementation process is to design a form component on the page, which includes a document selection box, which can display the relevant document data in the database. After the user clicks the selection box, it connects to the database through the SQL statement, queries the document data that meets the conditions, and displays these data in the drop-down list or pop-up window of the page. After selecting a specific document in the document selection box, when the run button is clicked, the background SQL query statement will be executed again, and the relevant database records will be automatically filtered out according to the selected document parameters, and these records will be fed back to the page for display, and the page status will be updated to the selected document content. The page will automatically display all necessary information related to the selected document and provide data support for subsequent summary and detail processing.

[0113] Preferably, based on the summary SQL execution statement, the database drawing board page layout optimization form is driven to execute the document summary, and the document summary run button is driven to execute the page document summary drive job;

[0114] In an embodiment of the present invention, the document summary operation of the database canvas page form is completed by executing a summary SQL statement. Specifically, first, a summary SQL statement is constructed according to the user selection or input conditions of the current page. At this time, the summary SQL statement will group and count the selected documents, and generate summary results according to the set summary rules (such as aggregation calculation by date, customer, amount, etc.). The triggering of the summary operation is driven by clicking the "Document Summary" button on the page. When the user clicks the button, the summary SQL will be executed according to the input or selected conditions, and the summary results will be obtained and dynamically filled into the corresponding summary table or data display area on the page. In this process, it will be ensured that the various statistical data are clearly reflected in the summary results displayed on the page, and all data are summarized and displayed based on the latest records in the database.

[0115] Preferably, the document detail driven execution is performed on the database drawing board page layout optimization form based on the detail SQL execution statement, so as to select or summarize the corresponding detail information of the page document and fill it into the document detail table below;

[0116] In an embodiment of the present invention, the document details are displayed and filled in the database drawing board page based on the detailed SQL statement. When executing this step, the corresponding detailed SQL query statement will be first constructed according to the document or summary item selected by the user on the page. The detailed SQL will query the corresponding detailed data records based on the specific document or summary conditions. Usually, these data include the details involved, such as the time, amount, specific content, etc. of each transaction. After executing the query, the query results will be filled in the detailed table at the bottom of the page. The table will display each detail one by one according to the field information of the detailed record, and ensure that the display order and format of the data are correct. In this way, the user can clearly view all detailed information related to the selected document or summary item at the bottom of the page, and further perform data analysis or operation.

[0117] Preferably, a document post-modification execution operation is performed on the database drawing board page layout optimization form based on the post-SQL execution statement.

[0118] In an embodiment of the present invention, by executing post-SQL execution statements, subsequent modification operations are performed on relevant data in the database. These modifications usually occur in the data update stage after document selection, aggregation or detailed display. The specific operation is that after executing the document selection, aggregation or detailed query in the previous steps, a post-SQL statement will be generated according to the business rules to perform update, deletion or insertion operations on relevant records in the database. At this time, the post-SQL statement will execute specific update tasks through the database connection, such as modifying the document status, updating the field value, deleting redundant data, etc. After the execution is completed, the operation results will be fed back in time and the page content will be updated to ensure the consistency and real-time nature of the data. In actual operation, after the user clicks the "Execute" button on the page, the post-SQL execution task will be started and the execution result will be displayed to the user. If the data modification is successful, the page will display the updated data record. If it fails, an error message will be displayed to prompt the user to check the data or operation conditions.

[0119] Furthermore, the query-driven operation of optimizing the database drawing board page layout form based on the query SQL execution statement includes:

[0120] Based on the search pre-SQL execution statement, the database drawing board page layout optimization form is pre-searched to drive the execution of the corresponding page form summary and detailed summary operations;

[0121] In an embodiment of the present invention, by using the front-end SQL execution statement configured in the database drawing board interface, the specified database drawing board page layout optimization form is searched to obtain the required data set. In the implementation process, the SQL execution statement is first dynamically generated according to the conditions, filter items and field settings in the page form input by the user, and the SQL execution statement is passed to the database management system for execution through the database connection. After the execution is completed, the query results obtained will be used as the data source and filled into the display area of ​​the page form. Next, the summary calculation operation will be automatically performed according to the form layout and requirements. For example, if the page form needs to display statistical information such as the sum or average of a certain field, after obtaining the data, the corresponding data summary calculation will be performed based on the conditions and field definitions in the front-end SQL statement. Specifically, the total and summary of the detailed data will depend on the GROUP in the SQL query statement. Aggregate functions such as BY, SUM(), AVG(), etc., through these functions, the summary and totaling operations will be completed in the background, and then the results will be displayed in the specified area on the page. Through the front-end retrieval logic, it can be ensured that each time the page is loaded, all data will be synchronized according to the latest database content, and summarized and totaled according to specific logical rules to meet the needs of page display. For example, on some financial report pages, the form will display the expenditure details and total values ​​of each department within a certain period of time. Through the front-end SQL execution statement, these detailed data will be dynamically pulled and instantly totaled to ensure the real-time accuracy of the report.

[0122] Preferably, a post-search verification driving operation is performed on the database page form after the pre-search based on the post-search SQL execution statement.

[0123] In the embodiment of the present invention, the database page form obtained after the pre-search is verified and optimized by retrieving the post-SQL execution statement to ensure the accuracy and consistency of the data. A post-SQL statement will be generated according to the result after the pre-SQL execution. This statement will perform more complex verification operations on the data set retrieved from the pre-search. The execution of the post-SQL not only depends on the pre-data, but also dynamically adjusts according to other business logics or rules in the platform. During the implementation process, the post-SQL execution statement will verify the data set retrieved from the pre-search. For example, if the data type of some fields does not meet the preset standard, or the range of the data exceeds the defined threshold, the post-SQL will mark these data as abnormal data, record and provide detailed abnormal information. In addition, The post-search operation can also perform secondary calculations based on business needs, such as reviewing the compliance and rationality of certain values ​​in the pre-SQL query results to ensure that there is no data omission or duplication. Specifically, the SQL statement of the post-search includes additional conditions and query filtering logic, such as using JOIN to query data in other tables, verifying whether the relationship between data is reasonable, or checking the integrity of the data through calculation. For example, when processing financial data, the post-SQL needs to audit the aggregated amounts to verify the compliance of various expenses and the rationality of the amounts. Through the verification and optimization of the post-SQL, the pre-search data can be further refined to ensure that the data presented to the user meets the system design requirements and business rules, avoiding the final display errors caused by omissions or inaccuracies in the pre-search.

[0124] Furthermore, the positive and negative review driving operation of optimizing the database drawing board page layout form based on the review SQL execution statement includes:

[0125] Perform API-driven review of the database artboard page layout optimization form based on the API review Sql execution statement;

[0126] In the embodiment of the present invention, the API call corresponding to the database drawing board page layout optimization form is reviewed by combining the API review SQL execution statement generated by the previous driver. This SQL execution statement is usually used to query or operate the data in the database and affect the page layout of the database drawing board. These SQL execution statements are passed to the back-end API interface through the input box of the front-end page or the automation system, ready for review, so as to initiate an API request and use the SQL execution statement as the request body (Request The API request usually carries the necessary authentication information and SQL statements and is sent to the back-end audit interface through the POST or PUT method. After receiving the SQL execution statement, the back-end service uses the SQL parser to check its syntax, logic, and execution efficiency. For example, it checks whether the SQL statement complies with the best practices for database performance optimization and whether there are potential performance bottlenecks (such as full table scans, unused indexes, etc.). The audit process also determines whether the SQL statement affects the accuracy of the database canvas page layout and whether it causes unnecessary queries or update operations, thereby affecting the page rendering speed and data consistency. The audit result is returned to the front-end page through the API. If there is a problem with the SQL execution statement, detailed audit feedback information will be generated, including the error type, recommended improvement plan, etc. If the SQL statement complies with the specification, it returns to the "audit passed" status and prepares for the next step of processing to ensure that the SQL statement used in the database canvas page layout optimization process meets the performance and logic requirements.

[0127] Preferably, based on the form scheme audit Sql execution statement, the database drawing board page layout optimization form driven by the API is audited and the positive and negative audit driving operations corresponding to the audit opinions are performed.

[0128] In an embodiment of the present invention, by driving the audit result of the API in the previous step, the optimized database drawing board page layout form is further audited positively and negatively to ensure the rationality of the page layout and data interaction. After the API audits the SQL execution statement drive, the database drawing board page layout optimization form will be displayed to the auditor. The form scheme includes information such as the optimized database form layout, field display method, data association relationship, etc. The optimized form layout information is transmitted through the API and displayed on the front-end page. The SQL execution statement is audited according to the form scheme generated by the previous drive, providing a driving mechanism for positive and negative audits. The auditor triggers the positive or reverse audit operation through the interactive button on the form. The positive audit usually includes confirming whether the form layout and SQL execution statement meet expectations; while the reverse audit includes modifying, giving feedback and re-auditing the SQL execution statement and form layout with potential problems. In the positive audit stage, In the first stage, the auditor determines whether the optimized form layout meets the project requirements based on the feedback information provided by the automatic audit, ensures the accuracy of page display and data interaction, confirms each element in the form, checks the consistency of the layout and data, and confirms whether the SQL execution statement can be correctly bound to the front-end page elements. If there is no problem, the auditor confirms "Audit Passed" through the system interface and triggers the subsequent form deployment process. In the reverse audit stage, if the auditor finds that there are problems with the form layout or SQL execution statement, such as non-compliant field positions, data query logic errors, or abnormal page display, the auditor can trigger a reverse audit, which will prompt the modification point. The auditor modifies the SQL execution statement or adjusts the form layout according to the prompt. After the modification is completed, it will be reviewed again and the modified feedback results will be returned. The auditor continues to perform positive or reverse audits on the modified content until the form and SQL statement fully meet the requirements.

[0129] Furthermore, the present invention also provides a data-driven low-code development method, which is applied to the data-driven low-code development platform as described above. The data-driven low-code development method includes the following steps:

[0130] Obtain the field name and field value corresponding to the business data to obtain the business database table metadata column; obtain the field type dictionary corresponding to the business data to generate the business database table field dictionary attribute; use the business database table metadata column and the business database table field dictionary attribute as database form metadata information;

[0131] In the embodiment of the present invention, the metadata columns (i.e., the corresponding field names and field values) corresponding to the data table are extracted from the business data, and an SQL query statement such as SELECT column_name, column_value FROM<business_table> , can obtain the field name (column_name) and the corresponding field value (column_value) of the database table. These data reflect the actual storage structure of the business data. The field name indicates the name of each column in the database table, and the field value indicates the data of each column. Through the API connecting to the database, these metadata are extracted from the database and organized into a field list. These field names and field values ​​will serve as the basis for generating the database form data structure in the subsequent steps, thereby obtaining the business database table metadata column. In addition, by obtaining the type dictionary information of each field, by executing SELECTcolumn_name,data_type FROM information_schema.columns WHERE table_name='<business_table> 'Such a query statement can obtain the type of each field from the metadata table of the database (such as information_schema.columns). The dictionary of field types is composed of field names and their corresponding data types (such as VARCHAR, INT, DATE, etc.). This dictionary is crucial when generating field attributes because it helps understand how each field should be rendered in the form. For example, the selection of controls such as text boxes, date selection boxes, and drop-down boxes will depend on the field type, thereby generating the business database table field dictionary attributes. At the same time, by summarizing the previously obtained field names, field values, field types and other information, the "unit data information" of the database table is generated. This information includes the basic name of the field, the data value, and the type characteristics of the field. The metadata information of all fields will form a data structure, such as a dictionary or JSON object, which represents all columns in the database table and their corresponding attributes. This data structure provides the necessary basis for subsequent page generation. It not only contains the attributes of each field, but also contains relevant information on how these fields are displayed on the interface (such as the control type).

[0132] Preferably, a page form is generated for the database form metadata information to generate a database metadata page form prototype;

[0133] In an embodiment of the present invention, a prototype of a database form is automatically generated based on previously generated database form metadata information. By parsing the metadata of each field, such as field type, length, etc., the presentation form of each field in the form is determined. For text fields, a text box will be generated; for date fields, a date selection control will be generated; for numeric fields, a value input box will be generated, etc. These form controls will generate a preliminary database form prototype based on business logic and user interface specifications. The generated page form prototype does not contain all the details, but it provides a structured interface layout and can support subsequent optimization and adjustment, and finally generates a database metadata page form prototype.

[0134] Preferably, various types of Sql drivers of the drawing board control are generated for the database metadata page form prototype to generate various types of database page form control Sql driving statements; based on various types of database page form control Sql driving statements, the page form delay promotion drive execution is performed on the database metadata page form prototype to generate various types of form control delay promotion Sql execution statements, including maintenance Sql execution statements, document Sql execution statements, query Sql execution statements and review Sql execution statements;

[0135] In an embodiment of the present invention, by analyzing and designing the database metadata page form prototype, each form prototype corresponds to a specific database entity, and the metadata defines the attributes, field types, constraints and their relationships of these entities. By using a professional graphical drawing board tool (such as a UI design tool) for prototype design, form module controls on the user interface (such as a retrieval solution module, a page modification solution module, a document extraction solution module, an API solution module, a table editing solution module and a drawing board solution module, etc.) are constructed. Once the prototypes of these controls are created, the next task is to generate corresponding SQL driver statements. In specific implementation, the development tool will automatically generate SQL operation statements corresponding to each control according to the type of form control and the structure of the database table, such as INSERT, UPDATE, DELETE, SELECT, etc. The SQL driver statements of each control will interact at the database level to ensure that data can be correctly added, deleted, modified and checked. When generating SQL statements, the tool will ensure that the SQL statements follow the constraints and field types of the database, especially in data type conversion and field mapping, avoiding errors and inconsistencies in manual coding. In this way, developers do not need to write SQL manually, but only need to drag and drop controls and select fields to generate corresponding SQL drivers, thereby generating SQL driver statements for various database page form controls. At the same time, the previously generated SQL-driven statements are further optimized and designed for delayed execution through the development tool. In this process, different SQL execution requirements are first distinguished. For example, maintenance SQL execution statements are used for data addition and update operations, document SQL execution statements are used for specific document generation and processing, query SQL execution statements are used to display data and filter, and audit SQL execution statements are executed for the data audit process. Each type of SQL statement will be embedded in the event-driven logic of the form control, such as the submit button, query button, etc. The tool will design a delayed execution mechanism for each operation (addition, query, audit, etc.), that is, to delay the actual execution of SQL through certain trigger conditions (such as user operations, page loading, etc.). This delayed execution mechanism can avoid unnecessary database operations, optimize page loading and response time, and improve user experience. In specific implementation, the database-driven tool will perform syntax checks on each SQL statement to ensure that the generated SQL statement has no syntax errors, and prevent security issues such as SQL injection through parameterized queries. Finally, it optimizes the generation of various form controls to delay and improve SQL execution statements.

[0136] Preferably, the page layout of the database metadata page form prototype is optimized to generate a database drawing board page layout optimization form;

[0137] In the embodiment of the present invention, the layout optimization design of the database drawing board page mainly focuses on the visual performance of the form and the improvement of the interactive process. In order to improve the convenience and readability of user operation, the layout of the form will be carefully adjusted through the layout drag function in the database drawing board module. It allows users to design and adjust the layout of the application interface through intuitive drag and drop operations. This function greatly simplifies the interface design process, so that non-professional developers can easily create complex application interfaces. For example, the arrangement of fields, the size of controls, the display position of labels, the color matching of forms, etc. will be optimized according to specific needs. The tool will automatically adjust the position and size of each control according to the field information, length and type of the field in the database table to avoid the situation where the interface is too crowded or difficult to operate. At the same time, based on the user's interaction habits, the tool will also design a responsive layout of the controls to ensure that the form can be correctly displayed under different screen sizes. In addition, appropriate input validation rules will be set for each form control to ensure that the data format entered by the user complies with the database constraints, such as the maximum length of the text field, the valid range of the numeric field, etc. Through these layout optimizations, the database page form can achieve high efficiency and ease of use standards in both vision and function, and finally the database drawing board page layout optimization form is designed and generated.

[0138] Preferably, based on the maintenance Sql execution statements, document Sql execution statements, query Sql execution statements and audit Sql execution statements, the database drawing board page layout optimization form is maintained, the document expansion calculation, query and positive and negative audit driving operations are performed respectively, thereby driving the development to obtain the corresponding low-code development platform.

[0139] In an embodiment of the present invention, based on previously generated SQL execution statements (such as maintenance SQL execution statements, document SQL execution statements, query SQL execution statements, and audit SQL execution statements), specific business operations are designed for the form after the database page layout is optimized. These operations include form maintenance, query, document expansion calculation and audit, etc. Each operation will trigger the execution of different SQL statements, wherein maintenance operations usually involve the addition and modification of data, and the development tool implements the insertion and update operations of data by generating specific SQL statements; the query operation generates dynamic query SQL statements according to the conditions entered by the user, returns the data results that meet the conditions, and the query statements are optimized according to factors such as field types and indexes to improve the query efficiency; the document expansion calculation is mainly used to generate and display specific business documents, such as invoices, orders, etc. At this time, the corresponding view will be generated according to the document template and the relevant database records, and the relevant data will be automatically filled in; the audit operation generates SQL statements according to business rules to perform positive and negative audits of data, that is, "audit opinions". For example, in the positive audit stage, according to the feedback information provided by the automatic audit, it is judged whether the optimized form layout is In order to meet the project requirements and ensure the accuracy of page display and data interaction, each element in the form will be confirmed, the layout and data consistency will be checked, and whether the SQL execution statement can be correctly bound to the front-end page elements will be confirmed. If there is no problem, the system interface will confirm "Audit Pass" and trigger the subsequent form deployment process. In the reverse audit stage, if problems are found in the form layout or SQL execution statement, such as non-compliant field positions, data query logic errors, or abnormal page display, reverse audit can be triggered. The modification point will be prompted to modify the SQL execution statement or adjust the form layout according to the prompts. After the modification is completed, the modified feedback results will be reviewed and returned. Each SQL operation will be embedded in the corresponding form control to ensure that the correct SQL statement execution can be triggered when the user clicks the corresponding button. In addition, the development tool will automatically handle the parameter binding between form controls and SQL statements to ensure data consistency and correctness and reduce errors in manual intervention. Finally, the low-code platform will generate a complete background logic based on these business operations. Developers only need to perform a small amount of configuration to realize the operation of the entire system, thereby driving the development of the corresponding low-code development platform.

[0140] The above description is only a specific embodiment of the present invention, so that those skilled in the art can understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but should conform to the widest scope consistent with the principles and novel features invented herein.

Claims

1. A data-driven low-code development platform, characterized in that: For executing the data-driven low-code development method as claimed in claim 10, the low-code development platform includes the following module layers from bottom to top: The data foundation layer includes a field module and a dictionary module, wherein the field module is used to obtain the field name and field value corresponding to the business data to obtain the business database table metadata column; the dictionary module is used to obtain the field type dictionary corresponding to the business data to generate the business database table field dictionary attributes; the business database table metadata column and the business database table field dictionary attributes are used as database form metadata information; The page data layer includes a page front-end representation unit corresponding to the drawing board module, which is used to generate a page form based on the database form metadata information to generate a database metadata page form prototype; The page function driver layer includes various page function sub-modules, which are used to generate various SQL drivers for the drawing board controls of the database metadata page form prototype, and generate SQL driver statements for various database page form controls; Based on various database page form control SQL driver statements, the database metadata page form prototype is driven to execute page form delay promotion to generate various form control delay promotion SQL execution statements, including maintenance SQL execution statements, document SQL execution statements, query SQL execution statements, and review SQL execution statements; The page presentation layer includes a page post-design unit corresponding to the drawing board module, which is used to optimize the page layout design of the database metadata page form prototype to generate a database drawing board page layout optimization form; The business data driving layer includes the data maintenance module, the document module, the query module and the audit module. The data maintenance module is used to perform maintenance driving operations on the database drawing board page layout optimization form based on the maintenance Sql execution statement; The document module is used to perform document expansion calculation drive operations on the database drawing board page layout optimization form based on the document SQL execution statement; The query module is used to query the database drawing board page layout optimization form based on the query SQL execution statement to perform query-driven operations; The audit module is used to drive positive and negative audits on the database canvas page layout optimization form based on the audit SQL execution statement.

2. The data-driven low-code development platform according to claim 1, characterized in that: The various types of page function sub-modules include a retrieval solution module, a page modification solution module, a document extraction solution module, an API solution module, a table editing solution module and a drawing board solution module.

3. The data-driven low-code development platform according to claim 2, characterized in that: The generation of various SQL drivers for the sketchpad control of the database metadata page form prototype includes: By pressing the corresponding search control on the drawing board module through the search scheme module, the search scheme Sql driver is generated for the database metadata page form prototype, and the database page form search scheme Sql driver statement is generated; Through the page modification scheme module, press the corresponding page modification control on the drawing board module in the document extraction scheme module to generate the page modification Sql driver for the database metadata page form prototype, and generate the database page form modification scheme Sql driver statement; Through the document extraction scheme module, press the corresponding document extraction control on the drawing board module to generate the document extraction Sql driver for the database metadata page form prototype, and generate the database page form document extraction scheme Sql driver statement; Through the API solution module, press the corresponding API review control on the drawing board module to generate the API review Sql driver for the database metadata page form prototype, and generate the database page form API review Sql driver statement; Press the corresponding table editing control on the drawing board module through the table editing solution module to generate the table editing Sql driver for the database metadata page form prototype, and generate the database page form table editing Sql driver statement; Through the drawing board scheme module, press the corresponding drawing board review control on the drawing board module to generate the drawing board scheme review Sql driver for the database metadata page form prototype, and generate the database page form scheme review Sql driver statement.

4. The data-driven low-code development platform according to claim 3 is characterized in that: The page form delay promotion driving execution of the database metadata page form prototype based on various database page form control Sql driving statements includes: Conduct detailed and in-depth mining and analysis of various database page form control SQL driver statements to obtain the properties, types and interaction methods corresponding to various form control SQL driver statements; conduct driver dependency evaluation and analysis of various database page form control SQL driver statements based on the properties, types and interaction methods corresponding to various form control SQL driver statements to generate the relative driver execution dependency and execution data flow between various form control SQL driver statements; Based on the relative driving execution dependency between various form control Sql driving statements, the driving duration between various database page form control Sql driving statements is monitored to generate the execution driving response duration between various form control Sql driving statements; according to the execution driving response duration between various form control Sql driving statements, the page driving response analysis is performed on the database metadata page form prototype to obtain the execution driving response efficiency of the Sql statement page form; Based on the execution drive response time and execution data flow between various form control Sql drive statements, the drive delay evaluation and analysis between various database page form control Sql drive statements are performed to obtain the Sql drive statement execution delay; Based on the SQL statement page form execution drive response efficiency and the SQL drive statement execution delay delay, the statement drive delay adjustment calculation formula is used to adjust and calculate the drive delay timing corresponding to the SQL drive statement of various database page form controls, so as to obtain the drive delay adjustment execution timing corresponding to the SQL drive statement of various form controls; According to the driving delay adjustment execution timing corresponding to the SQL driving statements of various form controls, the corresponding database page form control SQL driving statements are processed by statement driving promotion, so as to obtain various database page form SQL driving delay promotion statements; Based on various database page form Sql driver delay promotion statements, the database metadata page form prototype is driven to execute page form delay promotion to generate various form control delay promotion Sql execution statements, including maintenance Sql execution statements, document Sql execution statements, query Sql execution statements and audit Sql execution statements, wherein the maintenance Sql execution statements include page modification Sql execution statements and table editing Sql execution statements, wherein the page modification Sql execution statements include running Sql execution statements, subquery Sql execution statements, adding or modifying verification Sql execution statements and deleting Sql execution statements, document Sql execution statements include document selection Sql execution statements, summary Sql execution statements, detail Sql execution statements and post-Sql execution statements, query Sql execution statements include retrieval pre-Sql execution statements and retrieval post-Sql execution statements, and audit Sql execution statements include API audit Sql execution statements and form solution audit Sql execution statements.

5. The data-driven low-code development platform according to claim 4, characterized in that: The statement-driven delay adjustment calculation formula is specifically: Where, T i The driver delay adjustment execution timing corresponding to the SQL driver statement of the i-th form control, n is the total number of SQL driver statements of the form control, i is the item index of the SQL driver statement of the form control, The execution start time of the SQL driver statement corresponding to the i-th form control. is the end time of the execution of the SQL driver statement corresponding to the i-th form control, t is the statement execution time variable parameter, τ is the integral time component, D i (t) is the form control interaction complexity corresponding to the SQL driver statement of the i-th form control at time t, α i is the interaction complexity adjustment coefficient corresponding to the SQL driver statement of the i-th form control, is the execution resource consumption corresponding to the SQL driver statement of the i-th form control at time t, β i is the resource consumption impact adjustment coefficient corresponding to the SQL driver statement of the i-th form control, Q(τ) is the SQL statement page form execution driver response efficiency at time τ, t s Execution delay for SQL-driven statements, γ i is the execution response delay weight coefficient corresponding to the SQL driver statement of the i-th form control, and η is the correction coefficient of the driver delay adjustment execution timing.

6. The data-driven low-code development platform according to claim 4, characterized in that: The maintenance driving operation of optimizing the database drawing board page layout form based on the maintenance SQL execution statement includes: Based on the table editing Sql execution statement, the database artboard page layout optimization form is driven to execute the page form editing, and the page editing interpretation is executed according to the running Sql execution statement. Click the page editing run button to execute, and the execution result is displayed in the detailed table below the artboard module; According to the sub-query SQL execution statement, the database drawing board page layout optimization form is driven by the sub-query execution, and the driver clicks the page sub-query run button to execute the configuration page form sub-query detail table; According to the addition or modification of the verification SQL execution statement, the database drawing board page layout optimization form is added or modified to drive the execution. The driver clicks the page addition or modification run button to execute the corresponding database verification maintenance driver job before the page form is added or modified; According to the delete SQL execution statement, the database drawing board page layout optimization form is deleted and driven to execute. The driver clicks the page form deletion run button to execute the page form deletion maintenance driver job.

7. The data-driven low-code development platform according to claim 4, characterized in that: The document expansion calculation driving operation of optimizing the database drawing board page layout form based on the document SQL execution statement includes: Based on the document selection SQL execution statement, the database drawing board page layout optimization form is driven by document selection execution, and the driver clicks the document selection run button to execute the page document selection drive job; Based on the summary SQL execution statement, the database drawing board page layout optimization form is driven to execute the document summary, and the driver clicks the document summary run button to execute the page document summary driving job; Based on the detailed SQL execution statement, the database drawing board page layout optimization form is driven by the document details to select or summarize the corresponding detailed information of the page document and fill it into the document detail table below; Based on the post-SQL execution statement, the database canvas page layout optimization form is modified and executed post-document.

8. The data-driven low-code development platform according to claim 4, characterized in that: The query-driven operation of optimizing the database drawing board page layout form based on the query SQL execution statement includes: Based on the search pre-SQL execution statement, the database drawing board page layout optimization form is pre-searched to drive the execution of the corresponding page form summary and detailed summary operations; Based on the post-search SQL execution statement, a post-search verification drive job is performed on the database page form after the pre-search.

9. The data-driven low-code development platform according to claim 4, characterized in that: The positive and negative review driving operation of optimizing the database drawing board page layout form based on the review SQL execution statement includes: Perform API-driven review of the database artboard page layout optimization form based on the API review Sql execution statement; Based on the form solution audit Sql execution statement, the database drawing board page layout optimization form after API drive is audited and the positive and negative audit driving operations corresponding to the audit opinions are performed.

10. A data-driven low-code development method, characterized in that: Applied to the data-driven low-code development platform as claimed in claim 1, the data-driven low-code development method comprises the following steps: Obtain the field name and field value corresponding to the business data to obtain the business database table metadata column; obtain the field type dictionary corresponding to the business data to generate the business database table field dictionary attribute; use the business database table metadata column and the business database table field dictionary attribute as database form metadata information; Generate a page form based on the database form metadata information to generate a database metadata page form prototype; Generate various SQL drivers for the drawing board controls of the database metadata page form prototype, and generate various SQL driver statements for the database page form controls; perform page form delay promotion driver execution on the database metadata page form prototype based on various database page form control SQL driver statements to generate various form control delay promotion SQL execution statements, including maintenance SQL execution statements, document SQL execution statements, query SQL execution statements, and review SQL execution statements; Optimize the page layout design of the database metadata page form prototype to generate a database canvas page layout optimization form; Based on the maintenance Sql execution statement, document Sql execution statement, query Sql execution statement and audit Sql execution statement Do not perform maintenance on the database drawing board page layout optimization form, document expansion calculation, query, and positive and negative review drive operations, This drives the development of a corresponding low-code development platform.

Images