A data-driven low-code development method and platform

Abstract

This invention relates to the field of data-driven development technology, and more particularly to a low-code development method and platform based on data-driven approaches. The platform includes a data foundation layer, a page data layer, a page function-driven layer, a page presentation layer, and a business data-driven layer. The data foundation layer includes a field module and a dictionary module for acquiring database form metadata information. The page data layer includes a front-end page presentation unit for generating database metadata page form prototypes. The page function-driven layer includes various page function sub-modules for generating various SQL statements and performing delay-enhancing execution to generate various SQL execution statements. The page presentation layer includes a back-end page design unit for generating database canvas page layout optimization forms. The business data-driven layer includes a data maintenance module, a document module, a query module, and an approval module for performing driven operations. This invention simplifies the construction of complex logic platforms.

Description

Technical Field

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

[0002] Low-code development platforms have been widely adopted across various industries, including but not limited to manufacturing, retail, education, internet, and service. These platforms provide visual development tools, enabling non-professional developers to participate in the application building process, significantly lowering the development threshold. Current low-code development focuses 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 typically offer visual drag-and-drop interfaces, allowing users to quickly build applications using pre-built templates and controls. This model performs well in handling simple business logic, but it faces challenges in complex data processing. For example, complex data relationships and delayed statement execution often require more specialized data processing support, which exceeds the capabilities of traditional low-code platforms. This results in shortcomings in the integration of low-code platforms with existing enterprise systems. Summary of the Invention

[0003] Therefore, 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 comprises the following module layers from bottom to top:

[0005] The data foundation layer includes a field module and a dictionary module. The field module is used to obtain the field names and values ​​corresponding to the business data to obtain the metadata columns of the business database table. The dictionary module is used to obtain the dictionary of field types corresponding to the business data to generate the dictionary attributes of the business database table fields. The metadata columns of the business database table and the dictionary attributes of the business database table fields are used as the metadata information of the database form.

[0006] The page data layer includes the page front-end representation unit corresponding to the canvas module, which is used to generate page forms from database form metadata information to generate a database metadata page form prototype.

[0007] The page function-driven layer includes various page function submodules, which are used to generate various SQL drivers for the canvas controls on the database metadata page form prototype, and generate various SQL driver statements for the database page form controls. Based on the various SQL driver statements for the database page form controls, the page form deferred execution is performed on the database metadata page form prototype to generate various deferred execution statements for the form controls, including maintenance SQL statements, document SQL statements, query SQL statements, and audit SQL statements.

[0008] The page presentation layer includes the page post-design unit corresponding to the canvas module, which is used to optimize the page layout of the database metadata page form prototype to generate the database canvas page layout optimized form.

[0009] The business data-driven layer includes a data maintenance module, a document module, a query module, and an approval module. The data maintenance module performs maintenance-driven operations on the database canvas page layout optimization form based on maintenance SQL statements. The document module performs document expansion calculations on the database canvas page layout optimization form based on document SQL statements. The query module performs query-driven operations on the database canvas page layout optimization form based on query SQL statements. The approval module performs positive and negative approval operations on the database canvas page layout optimization form based on approval SQL statements.

[0010] Furthermore, the various page function sub-modules include a retrieval scheme module, a page modification scheme module, a document extraction scheme module, an API scheme module, a table editing scheme module, and a canvas scheme module.

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

[0012] By pressing the corresponding search control on the canvas module in the search scheme module, the database metadata page form prototype is generated using the search scheme SQL driver, and the database page form search scheme SQL driver statement is generated.

[0013] By using the page modification scheme module, the corresponding page modification control on the canvas module within the document extraction scheme module is pressed to modify the database metadata page form prototype using SQL driver generation, generating the database page form modification scheme SQL driver statement.

[0014] By pressing the corresponding document extraction control on the canvas module in the document extraction scheme module, the document extraction SQL driver is generated for the database metadata page form prototype, and the database page form document extraction scheme SQL driver statement is generated.

[0015] By pressing the corresponding API audit control on the canvas module in the API solution module, the database metadata page form prototype is generated using API audit SQL driver, and the database page form API audit SQL driver statement is generated.

[0016] By pressing the corresponding table editing control on the canvas module in the table editing scheme module, the SQL driver for table editing of the database metadata page form prototype is generated, and the SQL driver statement for table editing of the database page form is generated.

[0017] By pressing the corresponding canvas approval control on the canvas module, the canvas approval SQL driver is generated for the database metadata page form prototype, and the database page form approval SQL driver statement is generated.

[0018] Furthermore, the step of using SQL-driven statements for various database page form controls to perform page form delay boosting on the database metadata page form prototype includes:

[0019] We conduct detailed and in-depth analysis of the SQL driver statements for various database page form controls to obtain the attributes, types, and interaction methods corresponding to the SQL driver statements for each form control. Based on the attributes, types, and interaction methods of the SQL driver statements for various database page form controls, we perform driver dependency evaluation and analysis to generate the relative driver execution dependencies and execution data flow between the SQL driver statements for various form controls.

[0020] Based on the relative execution dependencies between SQL driver statements of various form controls, the driving duration of SQL driver statements of various database page form controls is monitored to generate the execution driving response duration of SQL driver statements of various form controls; based on the execution driving response duration of SQL driver statements of various form controls, page driving response analysis is performed on the database metadata page form prototype to obtain the SQL statement page form execution driving response efficiency.

[0021] Based on the execution response time and data flow of SQL driver statements for various form controls, the driving time delay of SQL driver statements for various database page form controls is evaluated and analyzed to obtain the execution time delay of SQL driver statements.

[0022] Based on the SQL statement page form execution drive response efficiency and SQL statement execution delay, the drive delay timing corresponding to the SQL statement of various database page form controls is adjusted and calculated using the statement drive delay adjustment calculation formula, so as to obtain the drive delay adjustment execution timing corresponding to the SQL statement of various form controls.

[0023] Based on the execution timing of the SQL driver statements corresponding to various form controls, statement-driven hoisting is performed on the corresponding database page form control SQL driver statements to obtain various database page form SQL driver delay hoisting statements.

[0024] Based on various database page form SQL-driven deferred boosting statements, the prototype of the database metadata page form is executed with page form deferred boosting to generate various form control deferred boosting SQL execution statements. These include maintenance SQL statements, document SQL statements, query SQL statements, and audit SQL statements. Maintenance SQL statements include page modification SQL statements and table editing SQL statements. Page modification SQL statements include run SQL statements, subquery SQL statements, add or modify validation SQL statements, and delete SQL statements. Document SQL statements include document selection SQL statements, summary SQL statements, detail SQL statements, and post-processing SQL statements. Query SQL statements include retrieval pre-processing SQL statements and retrieval post-processing SQL statements. Audit SQL statements include API audit SQL statements and form scheme audit SQL statements.

[0025] Furthermore, the specific formula for calculating the statement-driven delay adjustment is as follows:

[0026]

[0027] In the formula, Y i The execution timing of the driver delay is adjusted for the SQL driver statement corresponding to the i-th type of form control, where n is the total number of SQL driver statements for form controls, and i is the item index of the SQL driver statement for the form control. This represents the start time of statement execution corresponding to the SQL driving statement for the i-th type of form control. Let t be the execution end time of the SQL statement corresponding to the i-th type of form control, τ be the statement execution time variable parameter, and D be the integral time component. i (t) represents the interaction complexity of the form control at time t, where α is the SQL driving statement for the i-th type of form control. i Adjust the interaction complexity factor for the SQL driving statement corresponding to the i-th type of form control. Let β be the execution resource consumption of the SQL driving statement for the i-th type of form control at time t. i Let Q(τ) be the resource consumption impact adjustment coefficient corresponding to the SQL driving statement for the i-th type of form control, and let Q(τ) be the SQL statement page form execution driving response efficiency at time τ. s γ is the delay in the execution of SQL-driven statements.i η is the execution response delay weighting coefficient corresponding to the SQL driving statement of the i-th type of form control, and η is the correction coefficient for adjusting the timing of the driving delay.

[0028] Furthermore, the maintenance-driven operation for optimizing the database canvas page layout form based on maintenance SQL execution statements includes:

[0029] The SQL statement for table editing drives the page form editing of the database canvas page layout optimization form. The SQL statement is executed and the page editing is interpreted and executed. When the page editing is executed by clicking the page editing run button, the execution result is displayed in the details table below the canvas module.

[0030] The database canvas page layout optimization form is driven by a subquery SQL execution statement. Clicking the subquery run button on the page will execute the configuration page form subquery detail table.

[0031] The database canvas page layout optimization form is added or modified based on the SQL statement to be added or modified. Clicking the "Add or Modify" button on the page will execute the corresponding database verification and maintenance job before the form was added or modified.

[0032] The SQL statement for deleting forms is used to drive the deletion of forms on the database canvas page layout optimization form. Clicking the "Delete Form Run" button on the page will then execute the form deletion maintenance job.

[0033] Furthermore, the document expansion calculation-driven operation for optimizing the database canvas page layout form based on document SQL execution statements includes:

[0034] Based on the document selection SQL execution statement, the database canvas page layout optimization form is executed with document selection driven execution, which drives the click of the document selection run button to execute the page document selection driven job;

[0035] Based on the summary SQL execution statement, the form of the database canvas page layout optimization is executed by summarizing the documents. Clicking the document summary run button will then execute the document summary driven job on the page.

[0036] Based on the detailed SQL execution statement, the database canvas page layout optimization form is executed in a document detail-driven manner, so that the page document selection or summary corresponding detailed information is filled into the document detail table below;

[0037] This involves performing a post-execution job on the database canvas page layout optimization form based on a SQL statement.

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

[0039] The database canvas page layout optimization form is driven by a pre-retrieval SQL execution statement to perform corresponding page form summary and detailed summary operations.

[0040] This is a post-retrieval validation-driven job based on the SQL execution statement following the retrieval, which performs a post-retrieval validation on the database page forms after the preceding retrieval.

[0041] Furthermore, the positive and negative audit-driven operation of the database canvas page layout optimization form based on the audit SQL execution statement includes:

[0042] API-driven auditing of database canvas page layout optimization forms based on SQL execution statements for auditing;

[0043] Based on the form-based scheme, SQL execution statements are used to perform positive and negative review operations on the database canvas page layout optimization form after API-driven review.

[0044] Furthermore, the present invention also provides a data-driven low-code development method, applied to the data-driven low-code development platform described above, the data-driven low-code development method comprising the following steps:

[0045] Obtain the field names and values ​​corresponding to the business data to get the business database table metadata columns; obtain the field type dictionary corresponding to the business data to generate the business database table field dictionary attributes; use the business database table metadata columns and business database table field dictionary attributes as database form metadata information;

[0046] Generate a page form from the database form metadata information to generate a prototype of the database metadata page form;

[0047] The database metadata page form prototype generates various SQL drivers for canvas controls, producing SQL driver statements for various database page form controls. Based on these SQL driver statements, the database metadata page form prototype is then executed with page form delay boosting to generate various form control delay boosting SQL execution statements, including maintenance SQL execution statements, document SQL execution statements, query SQL execution statements, and audit SQL execution statements.

[0048] The page layout of the database metadata page form prototype is optimized to generate an optimized database canvas page layout form.

[0049] Based on the maintenance of SQL execution statements, document SQL execution statements, query SQL execution statements, and audit SQL execution statements, the database canvas page layout optimization forms are maintained, documents are expanded and calculated, queries are performed, and positive and negative auditing are driven, thereby driving the development of a corresponding low-code development platform.

[0050] The beneficial effects of this invention are:

[0051] The data-driven low-code development platform proposed in this invention comprises, from bottom to top, a data foundation layer, a page data layer, a page function-driven layer, a page presentation layer, and a business data-driven layer. The data foundation layer includes a field module and a dictionary module; the page data layer includes a front-end page presentation unit; the page function-driven 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 canvas solution module; the page presentation layer includes a back-end page design unit; and the business data-driven layer includes a data maintenance module, a document module, a query module, and an approval module. Compared with existing technologies, the beneficial effect of this application is that by obtaining the field names and values ​​corresponding to the business data, a comprehensive understanding of the structure and attributes of the business data can be ensured. Through this field information, the database table can be extracted. Metadata columns form the foundation for building business database tables, covering every dimension of the data. By retrieving a field type dictionary, this provides a basis for subsequent generation of database field dictionary attributes. The field type dictionary includes not only data types but also attributes such as data length, precision, and whether it is nullable. These are key elements to ensure the effective operation of the database tables in practical applications. Together, this metadata and field attribute information constitute the unit data information of the database table, providing a clear foundation for the execution of subsequent steps. By systematically acquiring and organizing the structured information of business data, it ensures that the data is accurately and clearly reflected in the database tables and provides the necessary basic data for subsequent form generation, optimization, and execution. This ensures that the generated page forms are highly consistent with the database table structure, thereby improving the accuracy and efficiency of platform data interaction. Secondly, database form metadata information will be used to generate database metadata page form prototypes. The core of this process is to combine metadata information with the page form structure to ensure that business data can be presented to users in a clear and intuitive way. By generating page form prototypes based on field names, field types, and field values, developers and business personnel can quickly understand the data structure and perform operations and modifications rapidly. Page form generation is not only the starting point of page design but also a key step in the entire low-code development process. By automatically generating page form prototypes, it greatly reduces the complexity and error rate of manual design and coding. 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, SQL execution statements for various database page form controls are generated based on the database metadata page form prototype. These SQL execution statements include maintenance SQL, document SQL, query SQL, and approval SQL statements. They are key to ensuring seamless integration 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 business process documents; query SQL statements are used to retrieve form data from the database; and approval SQL statements are used to implement approval and review operations in the business process. This automatic generation of SQL execution statements is achieved by clicking on module controls and delaying execution, thus tightly binding business logic with database operations. This automated process reduces the workload of manually writing SQL statements and avoids errors caused by delays in SQL statement execution. The generated SQL statements can be customized according to the actual needs of the page form, ensuring 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 not only displays data correctly but also provides users with a user-friendly interactive experience. The optimization design includes the arrangement, size, and color scheme of controls, as well as adjustments to the overall interface layout. The aim is to improve the readability of the page and the ease of operation. Based on business needs and user feedback, the layout and style of the page form will be carefully adjusted to ensure that the final interface meets user experience standards and can efficiently complete data interaction. Finally, the database canvas page layout optimization form is driven by maintenance SQL statements, document SQL statements, query SQL statements, and audit SQL statements. Specifically, this step aims to perform actual data operations on the page form based on the SQL statements generated in the previous steps, ensuring that the page form can smoothly perform data addition, deletion, modification, and query operations, and can support complex business processes such as forward and reverse audits in different business scenarios. This enables the automated development function of the low-code platform. Through SQL-driven operation, 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 not only improve the execution efficiency of the development platform, but also significantly reduce the risk of errors caused by manual operation, thereby enhancing the overall flexibility and response speed. Attached Figure Description

[0052] Other features, objects, and advantages of the invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying 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 This is a schematic diagram of the driving structure of the review module of this invention. Detailed Implementation

[0058] The technical method of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0059] To achieve the above objectives, please refer to Figures 1 to 5 This invention provides a data-driven low-code development platform. In the embodiments of this invention, please refer to... Figure 1 The diagram shown illustrates the module layer structure of the data-driven low-code development platform of this 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. The field module is used to obtain the field names and values ​​corresponding to the business data to obtain the metadata columns of the business database table. The dictionary module is used to obtain the dictionary of field types corresponding to the business data to generate the dictionary attributes of the business database table fields. The metadata columns of the business database table and the dictionary attributes of the business database table fields are used as the metadata information of the database form.

[0061] In this embodiment of the invention, the data infrastructure layer of the low-code development platform is composed of a field module and a dictionary module. The field module extracts the metadata columns (i.e., the corresponding field names and values) of the data tables from the business data to execute SQL query statements such as SELECT column_name, column_value FROM<business_table> The process involves retrieving the column names (column_name) and corresponding column values ​​(column_value) from the database table. This data reflects the actual storage structure of the business data. The column names represent the names of each column in the database table, and the column values ​​indicate the data in each column. Using the database API, this metadata is extracted from the database and organized into a list of fields. These field names and values ​​will serve as the basis for generating the database form data structure in subsequent steps, thus obtaining the business database table metadata columns. The dictionary module retrieves the type dictionary information for each field to execute `SELECT column_name, data_type FROM information_schema.columns WHERE table_name = '`.<business_table> Such a query can retrieve the type of each field from the database's metadata table (such as information_schema.columns). The dictionary of field types consists 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 pickers, and dropdown lists depends on the field type, thus generating the business database table field dictionary attributes. Simultaneously, this data foundation layer aggregates the previously obtained field names, field values, and field types to generate "cell data information" for the database table. This information includes the basic name of the field, its data value, and its type characteristics. All the field metadata information forms a data structure, such as a dictionary or JSON object, representing 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 information about how these fields are displayed on the interface (such as control types), ultimately yielding the database form metadata information.

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

[0063] In this embodiment of the invention, the page data layer of the low-code development platform is constituted by the page front-end representation unit corresponding to the canvas module. This page front-end representation unit automatically generates a prototype of the database form based on the previously generated database form metadata information. By parsing the metadata of each field, such as field type and length, it determines the presentation format of each field in the form. 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 details, but it provides a structured interface layout and can support subsequent optimization and adjustment, ultimately generating the database metadata page form prototype.

[0064] Preferably, the page function driving layer includes various page function sub-modules, used to generate various SQL drivers for the canvas control of the database metadata page form prototype, and generate various SQL driver statements for the database page form control; based on the various SQL driver statements for the database page form control, the page form delay boosting driving execution is performed on the database metadata page form prototype to generate various form control delay boosting SQL execution statements, including maintenance SQL execution statements, document SQL execution statements, query SQL execution statements, and audit SQL execution statements;

[0065] In this embodiment of the invention, a low-code development platform's corresponding page function driving layer is composed of various page function sub-modules (i.e., retrieval scheme module, page modification scheme module, document extraction scheme module, API scheme module, table editing scheme module, and canvas scheme module). This page function driving layer analyzes and designs the database metadata page form prototypes. Each form prototype corresponds to a specific database entity, and the metadata defines the attributes, field types, constraints, and relationships of these entities. Using professional graphical canvas tools (such as UI design tools), prototype design is performed to construct the form module controls on the user interface (such as the retrieval scheme module, page modification scheme module, document extraction scheme module, API scheme module, table editing scheme module, and canvas scheme module, etc.). Once the prototypes of these controls are completed... Once created, the next task is to generate the corresponding SQL driving statements. In practice, the development tool automatically generates SQL operation statements, such as INSERT, UPDATE, DELETE, and SELECT, based on the type of form control and the structure of the database table. The SQL driving statements for each control will interact at the database level to ensure that data can be correctly added, deleted, modified, and queried. When generating SQL statements, the tool ensures that the SQL statements comply with database constraints and field types, especially in terms of data type conversion and field mapping, avoiding errors and inconsistencies from manual coding. This way, developers do not need to manually write SQL; they can simply drag and drop controls and select fields to generate the corresponding SQL drivers, thereby generating SQL driving statements for various database page form controls. Simultaneously, the previously generated SQL-driven statements are further optimized and designed with delayed execution using development tools. This process first distinguishes different SQL execution requirements. For example, maintenance SQL statements are used for data addition and update operations; document SQL statements are used for specific document generation and processing; query SQL statements are used to display and filter data; and audit SQL statements are used for the data audit process. Each type of SQL statement is embedded into the event-driven logic of form controls, such as submit and query buttons. The tool designs a delayed execution mechanism for each operation (add, query, audit, etc.), delaying the actual execution of the SQL based on certain triggering conditions (such as user operation, page loading, etc.). This delayed execution mechanism avoids unnecessary database operations, optimizes page loading and response time, and improves user experience. In practice, the database-driven tool performs syntax checks on each SQL statement to ensure there are no syntax errors and uses parameterized queries to prevent security issues such as SQL injection. Ultimately, this optimizes the generation of various form controls and improves the delayed SQL execution.

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

[0067] In this embodiment of the invention, the page presentation layer of the low-code development platform is constituted by the page post-design unit corresponding to the canvas module. This page presentation layer, through layout optimization design of the database canvas page, mainly focuses on improving the visual presentation of forms and the interaction flow. To enhance user convenience and readability, the layout of forms is carefully adjusted using the layout drag-and-drop function in the database canvas module. This 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, enabling non-professional developers to easily create complex application interfaces. For example, the arrangement of fields, the size of controls, the display position of labels, and the color scheme of forms are all adjusted. Based on specific needs, the tool automatically adjusts the position and size of each control according to the field information, length, and type of the database table, avoiding an overly crowded or difficult-to-operate interface. Simultaneously, based on user interaction habits, the tool designs a responsive layout for the controls, ensuring the form displays correctly on different screen sizes. Furthermore, it sets appropriate input validation rules for each form control to ensure that user-input data conforms to database constraints, such as the maximum length of text fields and the valid range of numeric fields. Through these layout optimizations, the database page form achieves high efficiency and ease of use in both visual appeal and functionality, ultimately generating an optimized database canvas page layout form.

[0068] Preferably, the business data-driven layer includes a data maintenance module, a document module, a query module, and an approval module. The data maintenance module is used to perform maintenance-driven operations on the database canvas page layout optimization form based on maintenance SQL statements; the document module is used to perform document expansion calculations on the database canvas page layout optimization form based on document SQL statements; the query module is used to perform query-driven operations on the database canvas page layout optimization form based on query SQL statements; and the approval module is used to perform positive and negative approval operations on the database canvas page layout optimization form based on approval SQL statements.

[0069] In this embodiment of the invention, a business data-driven 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 (e.g., ...) is a business data-driven layer corresponding to the low-code development platform. Figure 2 As shown, the corresponding database form maintenance and modification work is triggered by executing the previously generated maintenance SQL statement, which usually involves adding and modifying data. The development tool generates specific SQL statements to implement the data insertion and update operations; document module (such as Figure 3 The document module (as shown) performs calculations based on SQL statements, primarily for generating and displaying specific business documents such as invoices and orders. It generates corresponding views based on document templates and related database records, and automatically populates relevant data. The query module performs queries based on SQL statements, generating dynamic query SQL statements according to user input and returning data results that meet the conditions. The query statements are optimized based on field types, indexes, and other factors to improve query efficiency. The audit module performs audit operations based on SQL statements, generating SQL statements according to business rules to perform positive and negative audits of data, i.e., "audit comments." For example, in the positive audit phase, based on feedback provided by automatic auditing, it judges whether the optimized form layout meets project requirements, ensuring the accuracy of page display and data interaction. It confirms each element in the form, checks the consistency between layout and data, and confirms SQL execution. If the statements are correctly bound to the front-end page elements, and there are no issues, the system interface confirms "approved" and triggers the subsequent form deployment process. During the reverse review stage, if problems are found in the form layout or SQL execution statements, such as non-standard field positions, data query logic errors, or abnormal page display, a reverse review can be triggered, prompting for corrections. Based on these prompts, the SQL execution statements or form layout are modified. After modification, a re-review is conducted, and the revised feedback result is returned. Each SQL operation is embedded in the corresponding form control to ensure that the correct SQL statement is executed when the user clicks the corresponding button. Furthermore, the development tool automatically handles parameter binding between form controls and SQL statements, ensuring data consistency and correctness and reducing errors from manual intervention. Ultimately, the low-code platform generates complete backend logic based on these business operations, requiring only minimal configuration from the developer to enable the entire low-code development platform to operate.

[0070] Furthermore, the various page function sub-modules include a retrieval scheme module, a page modification scheme module, a document extraction scheme module, an API scheme module, a table editing scheme module, and a canvas scheme module.

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

[0072] By pressing the corresponding search control on the canvas module in the search scheme module, the database metadata page form prototype is generated using the search scheme SQL driver, and the database page form search scheme SQL driver statement is generated.

[0073] In this embodiment of the invention, users can perform retrieval operations on the database metadata page form prototype through the corresponding retrieval control on the canvas module of the retrieval scheme module. Specifically, users first need to select the retrieval control and configure it on the canvas. This control allows input of the database table name, field name, and corresponding retrieval conditions. The calling module will automatically generate an SQL statement based on the user's input retrieval conditions, driving the database to perform the retrieval operation. After execution, the system determines whether to return the result to the calling module based on the configuration. If the result is returned, the calling module will then fill in the relevant canvas module and detail table control. The data driving in the retrieval scheme configuration mainly involves the front-end SQL and the back-end SQL. SQL is divided into two parts: front-end SQL for implementing retrieval functions and back-end SQL for post-retrieval validation or other functions, determined by the SQL configuration personnel. The structure of the SQL statement is automatically constructed by analyzing the metadata of the database table (such as field types, field constraints, etc.) and generating the corresponding SELECT statement. For example, if the user sets the search condition to "age>30", the generated SQL statement will include the condition "WHERE age>30". The generated SQL statement will be executed in the background, retrieving data from the database table and returning the query results to the user for display. Ultimately, it drives the generation of SQL-driven statements for the database page form retrieval scheme.

[0074] Preferably, the corresponding page modification control on the canvas module within the document extraction scheme module is pressed through the page modification scheme module to generate the SQL driver for modifying the database metadata page form prototype, thereby generating the SQL driver statement for modifying the database page form.

[0075] In this embodiment of the invention, operations are performed using the corresponding page modification controls on the canvas module of the page modification scheme module. The purpose is to modify the prototype of the database metadata page form. The design principle of this page modification scheme is to obtain data from the canvas in the document module or from the document detail table. This data is then substituted into the SQL statements stored in the page modification scheme. After the SQL statements in the page modification scheme are executed in the document module, if the SQL statements modify the two types of temporary tables associated with the page modification scheme (summary temporary table or detail temporary table), and the tool platform is configured to write back the summary or write back the detail, then the relevant information of the execution result will be filled back into the canvas data or detail data in the document module. In specific operations, the user sets the modification content through the page modification controls on the canvas, such as modifying the default value, field length, or type of a field. Based on the user's modification needs, the corresponding UPDATE SQL statement is automatically generated. For example, if the user changes the default value of the "age" field to "25", an UPDATE statement will be automatically generated, such as: "UPDATE table_name SET age=25WHERE". The SQL statement `id=?"` will drive the database to update the value of the corresponding form field. It will verify the validity of the input modification based on the database table structure and data type, ensuring that the generated SQL statement meets the database constraints, and ultimately drive the generation of the SQL statement for modifying the form on the database page.

[0076] Preferably, the document extraction scheme module uses the corresponding document extraction control on the canvas module to generate the document extraction SQL driver for the database metadata page form prototype, thereby generating the database page form document extraction scheme SQL driver statement.

[0077] In this embodiment of the invention, the document extraction control on the canvas module of the document extraction scheme module can extract specified document data from the form prototype on the database metadata page. This module mainly stores several types of SQL statements. When the button control is clicked, these SQL statements are executed to obtain the results, achieving the purpose of data-driven processing. The document extraction scheme module maintains these types of SQL statements: document selection SQL, summary SQL, detail SQL, and post-processing 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 detailed SQL queries then perform further queries based on certain column conditions in the results. The summary information is filled into the corresponding controls on the canvas, and the detailed information is filled into the document detail table below. In actual operation, first, select the document extraction control in the canvas module and define the extraction conditions. The system will generate an SQL statement based on the conditions set by the user. It is usually a SELECT statement with a WHERE clause. For example, if 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 backend extracts the document data that meets the conditions based on the generated SQL statement and returns the results to the user interface for further operation or display. Finally, it drives the generation of the SQL driver statement for the document extraction scheme in the database page form.

[0078] Preferably, the API solution module uses the corresponding API approval control on the canvas module to generate the API approval SQL driver for the database metadata page form prototype, and generates the database page form API approval SQL driver statement.

[0079] In this embodiment of the invention, the API audit control on the canvas module of the API solution module can perform API audit on the prototype of the database metadata page form. By selecting the control and setting relevant audit conditions, the corresponding SQL statement will be automatically generated to verify whether the form data called by the API meets the preset conditions. In the specific implementation process, the audit-driven SQL statement will be generated according to the audit standards configured by the user (such as API form data format, form parameter validity, etc.). For example, if the user wants to verify whether the "status" field is in the "approved" state, the generated SQL statement is: "SELECT * FROM table_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, to ensure whether to proceed to the subsequent positive and negative form audit work, and finally drive the generation of the database page form API audit SQL statement.

[0080] Preferably, the table editing SQL driver is generated for the database metadata page form prototype by pressing the corresponding table editing control on the canvas module through the table editing scheme module, and the table editing SQL driver statement for the database page form is generated.

[0081] In this embodiment of the invention, the table editing control on the canvas module of the table editing scheme module allows for table editing operations on the prototype of the database metadata page form. By selecting the table editing control and setting the table fields to be modified, such as adding new columns, changing column names, or adjusting column order, an ALTER TABLE statement will be automatically generated according to the user's modification requirements. This statement is used to modify the table structure in the database. For example, if the user requests to add an "email" field to the original table, the generated SQL statement will be: "ALTER TABLE table_name ADD email VARCHAR(255)". This SQL statement will be executed, and the database table structure will be modified accordingly based on the user's needs. The SQL statement will also be checked according to data type, field length, and other requirements to ensure that all modifications comply with the database's structural constraints. Ultimately, this drives the generation of the database page form table editing SQL statement.

[0082] Preferably, by pressing the corresponding canvas approval control on the canvas module, the canvas approval SQL driver is generated for the database metadata page form prototype, and the database page form approval SQL driver statement is generated.

[0083] In this embodiment of the invention, the canvas approval control on the canvas module of the canvas scheme module can be used to approve the prototype of the database metadata page form. First, the canvas approval control is selected based on the non-compliance results of the previous API call approval, and approval rules and parameters are set. According to the user-defined rules, the corresponding SQL statement is generated to check whether the form data meets the approval standards. For example, the user can set an approval condition: only when the "amount" field is greater than 1000 can the form be submitted. The automatically generated SQL statement is: "SELECT * FROM table_name WHERE amount > 1000". When this SQL statement is executed, it verifies whether the form data meets the approval rules. Only data that meets the conditions will be submitted or saved. This approval process can ensure that the data processing complies with the business process and rule requirements, and finally drives the generation of the database page form scheme approval SQL driving statement.

[0084] Furthermore, the step of using SQL-driven statements for various database page form controls to perform page form delay boosting on the database metadata page form prototype includes:

[0085] We conduct detailed and in-depth analysis of the SQL driver statements for various database page form controls to obtain the attributes, types, and interaction methods corresponding to the SQL driver statements for each form control. Based on the attributes, types, and interaction methods of the SQL driver statements for various database page form controls, we perform driver dependency evaluation and analysis to generate the relative driver execution dependencies and execution data flow between the SQL driver statements for various form controls.

[0086] In this embodiment of the invention, the SQL driving statements of various database page form controls are analyzed in detail. First, the SQL driving statements of each form control are parsed line by line to obtain the tables, fields, conditions, joins, sorting, and other SQL syntax details involved. Specifically, a database query analysis tool is used to capture and analyze the SQL statements triggered by events (such as input boxes, drop-down boxes, buttons, etc.) of each form control. For each SQL statement, its field type (e.g., integer, string, date, etc.), input attributes (e.g., single-line text, multi-line text, checkbox options, etc.), and interaction method (e.g., add, delete, modify, query operations) are extracted. In this way, the attributes and execution methods of SQL driving statements can be systematically identified, ensuring an accurate description and classification of the relationship between each control and SQL, thereby obtaining the attributes, types, and interaction methods corresponding to the SQL driving statements of various form controls. Simultaneously, based on the previously analyzed attributes, types, and interaction methods of each SQL statement, a dependency graph is drawn between SQL-driven statements. This graph reflects how different form controls influence each other, pass data, and establish dependencies through SQL statements. For example, the selection of one control can affect the display content of other controls (such as linked dropdown lists), or the input data of one control can 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 mechanisms of each control can be detected, thereby generating a visual driver dependency relationship. The dependency evaluation process also needs to detect whether there are circular dependencies or tightly coupled driver relationships. If so, optimization is required by adjusting the design structure or SQL statements. Finally, the relative driver execution dependencies and execution data flow between various form control SQL-driven statements are analyzed and generated.

[0087] Preferably, the driving duration of SQL driving statements for various database page form controls is monitored based on the relative driving execution dependencies between various form control SQL driving statements to generate the execution driving response duration between various form control SQL driving statements; and the page driving response of the database metadata page form prototype is analyzed based on the execution driving response duration between various form control SQL driving statements to obtain the SQL statement page form execution driving response efficiency.

[0088] In this embodiment of the invention, the driving time of SQL driving statements for various database page form controls is monitored based on the dependencies between SQL driving statements. First, the execution time between each SQL driving statement and the next is quantitatively measured. A monitoring tool is set up to record the time from the completion of each SQL statement's trigger execution to the triggering of the next SQL statement. Based on the dependencies between SQL statements, the influencing factors of each control's trigger time are analyzed. For example, when the input of a control affects the execution of multiple SQL statements, the monitoring tool records the overall time from the triggering of that control to the execution of all related SQL statements, and calculates the response time of each SQL statement. This process ensures real-time monitoring of the execution lag between SQL driving statements, thereby generating the execution driving response time between SQL driving statements for various form controls. Simultaneously, based on the previously recorded execution times of each SQL driving statement, the response time of each form control is analyzed in depth. For each control's input or trigger operation, the overall driving response time for the database query response time (i.e., SQL statement generation time), data return time, and page display time is calculated, thereby quantifying the form control's response efficiency, i.e., the page's response time. Ultimately, the efficiency of SQL statement execution driving the page form response is obtained.

[0089] Preferably, the execution delay of SQL driving statements between various database page form controls is evaluated and analyzed based on the execution response time and execution data flow of SQL driving statements between various forms, so as to obtain the execution delay of SQL driving statements.

[0090] In this embodiment of the invention, the execution delay of the SQL-driven statement for each form control is calculated to analyze the time difference between the triggering operation of each control and the SQL execution based on the previously recorded SQL execution response time and the identified data flow direction. Specifically, performance analysis tools are used to measure the delay of SQL statement execution in segments, recording the time required for each stage of SQL statement execution (such as query preparation, data processing, result return, etc.), and evaluating the impact of each form control on the SQL-driven delay based on the data flow direction. If it is found that the triggering operation of a certain control causes a significant delay, the related SQL statement needs to be optimized (e.g., optimizing the index, reducing query complexity, etc.). This process ensures that the execution efficiency of the SQL-driven statement is maximized through the evaluation of the delay, and finally obtains the SQL-driven statement execution delay.

[0091] Preferably, the driving delay timing corresponding to the SQL statement driving response efficiency and the SQL statement driving delay is adjusted and calculated using the statement driving delay adjustment calculation formula based on the SQL statement driving response efficiency and the SQL statement driving delay, so as to obtain the driving delay adjustment execution timing corresponding to the SQL statement driving response of various database page form controls.

[0092] In this embodiment of the invention, a suitable formula for adjusting the driving delay is constructed by combining parameters such as the number of SQL driving statements for form controls, the start time of statement execution, the end time of statement execution, time variable parameters, the interaction complexity of form controls, the adjustment coefficient for the impact of interaction complexity, the amount of execution resources consumed, the adjustment coefficient for the impact of resource consumption, the efficiency of SQL statement page form execution driving response, the execution delay of SQL driving statements, the weight coefficient of execution response delay, and related parameters. This formula is used to adjust the driving delay timing corresponding to various database page form control SQL driving statements, in order to calculate the optimal adjustment timing, optimize the execution order and triggering timing of database SQL statements, reduce the delay during page loading, and finally obtain the driving delay adjustment execution timing corresponding to various form control SQL driving statements.

[0093] Preferably, the SQL driving statements of the corresponding database page form controls are subjected to statement-driven hoisting processing according to the execution timing of the driving delay adjustment of the SQL driving statements of various forms, so as to obtain the SQL driving delay hoisting statements of various database page forms.

[0094] In this embodiment of the invention, the SQL-driven statements of the corresponding database page form control are improved by adjusting the execution timing of the SQL-driven statements based on the previously quantified delay. The execution plan of each SQL statement is analyzed to identify SQL statements with performance bottlenecks. For example, if the execution time of some SQL statements is too long, causing the form control to respond slowly, its performance needs to be optimized by adjusting its execution logic. This can be achieved by optimizing the query with indexes, reducing dataset scanning, or using more efficient query syntax (e.g., avoiding unnecessary nested queries or redundant JOIN operations). The SQL statements are then fine-tuned using performance monitoring tools (e.g., database log analysis, SQL optimization tools) to ensure a reasonable execution order and avoid unnecessary database operations. By adjusting the query conditions of the SQL statements, modifying the execution order, or splitting complex queries, each SQL statement can receive a faster response under the new execution timing, thereby improving the overall execution efficiency of the form control and reducing the delay of repeated queries. Finally, various database page form SQL-driven delay improvement statements are obtained.

[0095] Preferably, the database metadata page form prototype is executed using SQL-driven deferred boosting statements based on various database page forms to generate deferred boosting SQL execution statements for various form controls. These include maintenance SQL statements, document SQL statements, query SQL statements, and audit SQL statements. The maintenance SQL statements include page modification SQL statements and table editing SQL statements. The page modification SQL statements include run SQL statements, subquery SQL statements, add or modify validation SQL statements, and delete SQL statements. The document SQL statements include document selection SQL statements, summary SQL statements, detail SQL statements, and post-query SQL statements. The query SQL statements include retrieval pre-query SQL statements and retrieval post-query SQL statements. The audit SQL statements include API audit SQL statements and form scheme audit SQL statements.

[0096] In this embodiment of the invention, the page form delay-driven execution is performed on the database metadata page form prototype based on various SQL-driven delay-boosted statements that have been previously delayed. This requires identifying all involved SQL execution statements, especially maintenance, document, query, and approval SQL statements on the page. These SQL statements correspond to different database operation types. For example: maintenance operations include page modification SQL (e.g., update statements for modifying page content) and table editing SQL (e.g., add, delete, and modify table data); document operations include document selection SQL (e.g., document content query statements) and summary SQL (e.g., data summary and statistics statements); query operations include pre-query SQL and post-query SQL (e.g., data retrieval operations before and after page loading); and approval operations include API approval SQL and form scheme approval SQL. For core SQL statements (such as approval operations in the backend system), for each type of SQL execution statement, the execution strategy is optimized by comparing its execution time and latency improvement requirements, adjusting its execution order, and reducing unnecessary waiting and data transmission delays. Specific methods include asynchronous processing of page modifications and table editing operations to avoid waiting for data updates while the page loads; segmenting query operations to avoid page lag caused by executing too many queries at once; optimizing the response time of API calls for approval-related operations and combining transaction processing mechanisms to ensure data consistency. All optimized SQL statements are executed on demand during form loading, thereby significantly improving the overall page response speed and interactive performance, ensuring effective improvement in the response latency of various form controls, and ultimately driving the generation of SQL execution statements for various form controls with improved latency.

[0097] Furthermore, the specific formula for calculating the statement-driven delay adjustment is as follows:

[0098]

[0099] In the formula, T i The execution timing of the driver delay is adjusted for the SQL driver statement corresponding to the i-th type of form control, where n is the total number of SQL driver statements for form controls, and i is the item index of the SQL driver statement for the form control. This represents the start time of statement execution corresponding to the SQL driving statement for the i-th type of form control. Let t be the execution end time of the SQL statement corresponding to the i-th type of form control, τ be the statement execution time variable parameter, and D be the integral time component. i (t) represents the interaction complexity of the form control at time t, where α is the SQL driving statement for the i-th type of form control. i Adjust the interaction complexity factor for the SQL driving statement corresponding to the i-th type of form control. Let β be the execution resource consumption of the SQL driving statement for the i-th type of form control at time t. i Let Q(τ) be the resource consumption impact adjustment coefficient corresponding to the SQL driving statement for the i-th type of form control, and let Q(τ) be the SQL statement page form execution driving response efficiency at time τ. s γ is the delay in the execution of SQL-driven statements. i η is the execution response delay weighting coefficient corresponding to the SQL driving statement of the i-th type of form control, and η is the correction coefficient for adjusting the timing of the driving delay.

[0100] This invention, through the use of a specific mathematical model and verification, derives a formula for adjusting the execution timing of SQL-driven statements for various database page form controls. This formula integrates multiple factors (such as interaction complexity, resource consumption, and execution response lag) to calculate the appropriate execution timing for each type of form control's SQL-driven statements. This precise timing adjustment ensures optimized execution of SQL-driven statements, reducing unnecessary waiting and resource waste, thereby improving the overall response efficiency of low-code development platforms. Interaction complexity is used to measure the complexity of form controls, affecting the execution time of SQL-driven statements. By modeling the interaction complexity of different form controls, the formula can adjust the execution timing according to the complexity of the controls, avoiding performance bottlenecks caused by high-complexity interactions. The interaction complexity impact adjustment coefficient further reflects the actual impact of interaction complexity at specific times, ensuring that the calculated delay adjustment is more targeted. The resource consumption and resource consumption impact adjustment coefficients indicate the influence of resource consumption on SQL statement execution. The formula can adjust the execution timing in a timely manner based on the dynamic changes in current resource consumption, thereby avoiding excessive system resource consumption and improving system stability and concurrency processing capabilities. Q(τ) represents the page form execution efficiency at different time points. By considering response efficiency, the formula can continuously optimize timing adjustments during execution, ensuring efficient execution and avoiding delays during peak system loads. Simultaneously, the SQL driver statement execution delay and execution response delay weighting coefficients in the formula comprehensively consider delay factors during execution. This ensures that the impact of delay is weighed when calculating driver delay, helping to identify and adjust statements with delays, further optimizing execution timing. Furthermore, the introduction of a correction coefficient is used to fine-tune and correct the formula's output, ensuring that the adjustment results closely match the actual situation. This correction coefficient can be adjusted in a timely manner according to actual operating conditions, ensuring the applicability and effectiveness of the formula. In summary, this formula fully considers the driver delay adjustment execution timing T corresponding to the SQL driver statement of the i-th type of form control. i The total number of SQL statements driving the form controls, n; the item index i of the SQL statements driving the form controls; and the start time of execution of the statement corresponding to the SQL statement driving the i-th type of form control. The execution end time of the SQL driving statement corresponding to the i-th type of form control. The statement execution time variable parameter t, the integral time component τ, and the interaction complexity D of the form control corresponding to the SQL-driven statement for the i-th type of form control at time t. i (t), the interaction complexity adjustment coefficient α corresponding to the SQL driving statement of the i-th type of form control. i The resource consumption of the SQL driving statement for the i-th type of form control at time t. The resource consumption impact adjustment coefficient β corresponding to the SQL driving statement of the i-th type of form control. i The SQL statement execution efficiency Q(τ) at time τ is the page form execution-driven response efficiency, and the SQL statement execution latency t is the delay. s The execution response delay weighting coefficient γ for the SQL driving statement corresponding to the i-th type of form control. i The correction coefficient η for adjusting the execution timing of the drive delay is determined based on the execution timing T of the drive delay adjustment corresponding to the SQL drive statement of the i-th type of form control. i The interrelationships between the above parameters constitute a functional relationship. This formula can realize the adjustment and calculation process of the driving delay timing corresponding to SQL driving statements for various database page form controls. At the same time, by introducing the correction coefficient η for the driving delay adjustment execution timing, it can be adjusted according to the error situation that occurs during the calculation process, thereby improving the accuracy and applicability of the statement driving delay adjustment calculation formula.

[0101] Furthermore, the maintenance-driven operation for optimizing the database canvas page layout form based on maintenance SQL execution statements includes:

[0102] The SQL statement for table editing drives the page form editing of the database canvas page layout optimization form. The SQL statement is executed and the page editing is interpreted and executed. When the page editing is executed by clicking the page editing run button, the execution result is displayed in the details table below the canvas module.

[0103] In this embodiment of the invention, the form layout optimization form of the database canvas is driven by table editing SQL execution statements. This identifies the table controls and corresponding database table structures on the page, and uses predefined table editing SQL statements to drive the pressing of the "Edit" button. In the canvas module, the interaction logic between the table editing SQL statements and form controls is bound. When the user clicks the "Edit" button on the page, the corresponding SQL statement, such as UPDATE, INSERT, or DELETE, is automatically triggered to edit the table content. During execution, the backend server parses and executes the SQL statement and returns the result to the low-code frontend interface. Specifically, the database connection and SQL execution logic are configured using a low-code platform (such as Node-RED or similar database driver development tools). The operations on the page form (such as modification, deletion, and addition) are fed back to the database through SQL execution instructions. The execution result is displayed at the bottom of the page, i.e., in the detailed table, through a graphical interface, showing the updated results of the database operation in real time. For example, if the user enters new data in the table, the result after execution will be displayed in the page table in real time, ensuring that the user can see the changes promptly.

[0104] Preferably, the database canvas page layout optimization form is executed by subquery-driven execution based on the subquery SQL execution statement, which drives the clicking of the page subquery run button to execute the configuration page form subquery detail table;

[0105] In this embodiment of the invention, the database canvas page layout optimization form is executed using subquery-driven execution based on the subquery SQL execution statement generated from the response. This determines the fields or data items in the form that require subquery execution. Subquery execution is triggered by setting trigger conditions in page controls, such as a "Query" button. When this button is clicked, the subquery SQL statement is executed. Typically, such subqueries are nested within the main query statement; for example, a SELECT statement might be used to query detailed information from the database. These subqueries may include complex conditional filtering, data aggregation, and other operations. Database query optimization tools, such as MySQL's EXPLAIN plan or SQL Server's query analysis tools, are used to ensure the efficiency of subquery execution. After the subquery statement is executed, the result drives the updating of detailed tables or list views on the page. For example, if a form needs to display detailed information for a user, clicking the "Subquery" button will automatically display the user's detailed records, and any data changes will be reflected below the table.

[0106] Preferably, the database canvas page layout optimization form is added or modified according to the added or modified SQL execution statement, and the click of the add or modify run button on the page is driven to execute the database verification and maintenance drive job corresponding to the page form before the addition or modification.

[0107] In this embodiment of the invention, the database canvas page layout optimization form is driven to add or modify data based on the SQL execution statement for adding or modifying validation. This is done by determining which fields require data validation based on the type of page controls (e.g., text boxes, dropdown lists, date pickers, etc.). Adding or modifying operations typically involve inserting or updating data in the database. Specifically, SQL statements such as INSERT INTO and UPDATE are used to add or modify data. Before this operation, the SQL statement is validated to ensure that the user-input data conforms to the constraints of the database form. This validation operation is usually triggered by clicking the "Add" or "Modify" button. In practice, the SQL statement checks the integrity of the data in the database, such as whether required fields are empty, whether the data types match, and whether the data range is reasonable. If the data validation is successful, subsequent insert or update operations will continue. If the validation fails, the operation will be blocked, and the corresponding error message will be displayed. For example, if the form requires a valid email address, when adding or modifying, an SQL statement will be used to validate the email format to ensure the data conforms to the specifications. Finally, the database validation and maintenance driven operation corresponding to the page form addition or modification is executed.

[0108] Preferably, the deletion driver is executed on the database canvas page layout optimization form according to the deletion SQL execution statement, and the driver clicks the page form deletion run button to execute the page form deletion maintenance driver job.

[0109] In this embodiment of the invention, the database canvas page layout optimization form is driven to perform deletion based on the deletion SQL execution statement to confirm the records or items that need to be deleted on the page. These operations are usually associated with the delete button provided in the form. When the user clicks the button, the corresponding deletion SQL statement is triggered. The deletion operation generally uses the DELETE statement to remove the specified data record from the database. Before executing the deletion operation, the data is verified and confirmed, 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 the 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. The SQL statement is called through the backend interface for actual execution. After the operation is completed, the page will reflect the deletion result in real time, remove the corresponding data row, and update the form view.

[0110] Furthermore, the document expansion calculation-driven operation for optimizing the database canvas page layout form based on document SQL execution statements includes:

[0111] Based on the document selection SQL execution statement, the database canvas page layout optimization form is executed with document selection driven execution, which drives the click of the document selection run button to execute the page document selection driven job;

[0112] In this embodiment of the invention, by combining the document selection SQL execution statement generated by the previous response, the driving operation of optimizing the database canvas page layout form is executed. Specifically, a form component is designed on the page, including a document selection box. This box can display relevant document data in the database. After the user clicks the selection box, the database is connected through an SQL statement to query the document data that meets the conditions, and this data is displayed in the drop-down list or pop-up window on 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. Based on the selected document parameters, the relevant database records are automatically filtered out and these records are fed back to the page for display. The page status is updated to the content of the selected document. The page will automatically display all necessary information related to the selected document and provide data support for subsequent summary and detailed processing.

[0113] Preferably, the form for optimizing the layout of the database canvas page is executed by summarizing SQL statements to drive the execution of document summary. Clicking the document summary run button will then execute the document summary driven job on the page.

[0114] In this embodiment of the invention, the document summary operation of the database canvas page form is completed by executing a summary SQL statement. Specifically, a summary SQL statement is first constructed based on the user's selection or input conditions on 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 summary operation is triggered 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, 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 is ensured that the summary results displayed on the page clearly reflect various statistical data, and all data are summarized and displayed based on the latest records in the database.

[0115] Preferably, the database canvas page layout optimization form is executed based on the detailed SQL execution statement to perform document detail-driven execution, so as to fill the corresponding detailed information of the selected or summarized documents on the page into the document detail table below;

[0116] In this embodiment of the invention, the database canvas page is displayed and populated with document details based on detailed SQL statements. When executing this step, a corresponding detailed SQL query statement is first constructed based on the document or summary item selected by the user on the page. The detailed SQL will query the corresponding detailed data records according to specific document or summary conditions. Typically, this data includes various details involved, such as the time, amount, and specific content of each transaction. After executing the query, the query results will be populated into the detail table at the bottom of the page. The table will display each detail item one by one according to the field information of the detail record, and ensure that the data display order and format are correct. In this way, the user can clearly view all the detailed information related to the selected document or summary item at the bottom of the page and further perform data analysis or operations.

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

[0118] In this embodiment of the invention, subsequent modifications are made to the relevant data in the database by executing post-SQL statements. These modifications typically occur during the data update stage after document selection, summarization, or detailed display. Specifically, after completing the previous steps of document selection, summarization, or detailed query, post-SQL statements are generated according to business rules to perform update, deletion, or insertion operations on the relevant records in the database. At this time, the post-SQL statements will execute specific update tasks through the database connection, such as modifying document status, updating field values, and deleting redundant data. After execution, the operation results will be promptly fed back and the page content will be updated to ensure data consistency and real-time performance. 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 records; if it fails, an error message will be displayed, prompting the user to check the data or operation conditions.

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

[0120] The database canvas page layout optimization form is driven by a pre-retrieval SQL execution statement to perform corresponding page form summary and detailed summary operations.

[0121] In this embodiment of the invention, the specified database canvas page layout optimization form is retrieved by utilizing the pre-configured SQL execution statement in the database canvas interface to obtain the required dataset. During implementation, the SQL execution statement is dynamically generated based on user-input conditions, filter options, and field settings in the page form. This SQL execution statement is then passed to the database management system for execution via a database connection. After execution, the obtained query results are used as the data source and populated into the display area of ​​the page form. Next, based on the form layout and requirements, automatic summary calculations are performed. 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, corresponding data summary calculations are performed based on the conditions and field definitions in the pre-configured SQL statement. Specifically, the totals and summaries of detailed data rely on the GROUP statement in the SQL query. Aggregate functions such as BY, SUM(), and AVG() perform summary and aggregation operations in the background and then display the results in a specified area on the page. Through pre-retrieval logic, it can be ensured that all data is synchronized with the latest database content every time the page loads, and is summarized and aggregated 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 pre-execution SQL statements, these detailed data are dynamically retrieved and summed in real time to ensure the real-time accuracy of the report.

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

[0123] In this embodiment of the invention, a post-SQL statement is used to verify and optimize the database page forms obtained after the pre-retrieval, ensuring the accuracy and consistency of the data. Based on the results of the pre-SQL execution, a post-SQL statement is generated. This statement performs more complex verification operations on the dataset retrieved by the pre-retrieval. The execution of the post-SQL not only depends on the pre-retrieval data but is also dynamically adjusted according to other business logic or rules in the platform. During implementation, the post-SQL statement verifies the dataset retrieved by the pre-retrieval. For example, if the data type of certain fields does not conform to preset standards, or the data range exceeds a defined threshold, the post-SQL will mark these data as abnormal data, record and provide detailed abnormal information. In addition... Post-retrieval operations can also perform secondary calculations based on business needs, such as reviewing the compliance and reasonableness of certain values ​​in the results of the preceding SQL query to ensure that no data is omitted or duplicated. Specifically, the SQL statements for post-retrieval include additional conditions and query filtering logic, such as using JOIN to query data from other tables, verifying whether the relationships between data are reasonable, or checking the integrity of data through calculation. For example, when processing financial data, post-retrieval SQL needs to audit the summarized amounts to verify the compliance and reasonableness of various expenses. Through the verification and optimization of post-retrieval SQL, the preceding data can be further refined to ensure that the data presented to users meets the system design requirements and business rules, avoiding final display errors caused by omissions or inaccuracies in the preceding retrieval.

[0124] Furthermore, the positive and negative audit-driven operation of the database canvas page layout optimization form based on the audit SQL execution statement includes:

[0125] API-driven auditing of database canvas page layout optimization forms based on SQL execution statements for auditing;

[0126] In this embodiment of the invention, the API calls corresponding to the database canvas page layout optimization form are reviewed by combining the previously generated API review SQL execution statements. These SQL execution statements are typically used to query or manipulate data in the database and affect the page layout of the database canvas. These SQL execution statements are passed to the backend API interface through the input boxes on the front-end page or the automation system, ready for review, to initiate API requests, with the SQL execution statements as the request body. The API request (body) is passed to the backend review service. It typically carries necessary authentication information and SQL statements, and is sent to the backend review interface via POST or PUT. Upon receiving the SQL statement, the backend service uses an SQL parser to check its syntax, logic, and execution efficiency. For example, it checks whether the SQL statement conforms to best practices for database performance optimization and whether there are potential performance bottlenecks (such as full table scans or unused indexes). The review process also determines whether the SQL statement will affect the accuracy of the database canvas page layout and checks whether it will lead to unnecessary queries or update operations, thus affecting page rendering speed and data consistency. The review result is returned to the frontend page via the API. If there are problems with the SQL statement, detailed review feedback information is generated, including the error type and suggested improvement plans. If the SQL statement conforms to the specifications, a "review passed" status is returned, and preparations are made for the next step, ensuring that the SQL statements used in the database canvas page layout optimization process meet performance and logical requirements.

[0127] Preferably, the SQL execution statement based on the form scheme is used to perform positive and negative review operations on the database canvas page layout optimization form after API-driven review, corresponding to the review comments.

[0128] In this embodiment of the invention, based on the API-driven audit results of the previous step, the optimized database canvas page layout form is further audited both positively and negatively to ensure the rationality of the page layout and data interaction. After the API audit of the SQL execution statement, the optimized database canvas page layout form will be displayed to the auditor. The form scheme includes information such as the optimized database form layout, field display method, and data relationship. The optimized form layout information is transmitted through the API and displayed on the front-end page. The audit of the SQL execution statement based on the previously generated form scheme provides a positive and negative audit driving mechanism. The auditor triggers positive or negative audit operations through the interactive buttons on the form. Positive audit usually includes confirming whether the form layout and SQL execution statement meet expectations; while negative audit includes modifying, providing feedback on, and re-auditing SQL execution statements and form layouts with potential problems. In the first stage, the auditor, based on the feedback provided by the automated audit, determines whether the optimized form layout meets the project requirements, ensuring the accuracy of page display and data interaction. The auditor confirms each element in the form, checks the consistency between the layout and the data, and confirms whether the SQL execution statement can be correctly bound to the front-end page elements. If there are no problems, 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 problems with the form layout or SQL execution statement, such as non-standard field positions, data query logic errors, or abnormal page display, the auditor can trigger a reverse audit, which will prompt for modification points. The auditor modifies the SQL execution statement or adjusts the form layout according to the prompts. After the modification is completed, it will be re-audited and the modified feedback result will be returned. The auditor continues to conduct forward 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, applied to the data-driven low-code development platform described above, the data-driven low-code development method comprising the following steps:

[0130] Obtain the field names and values ​​corresponding to the business data to get the business database table metadata columns; obtain the field type dictionary corresponding to the business data to generate the business database table field dictionary attributes; use the business database table metadata columns and business database table field dictionary attributes as database form metadata information;

[0131] In this embodiment of the invention, the metadata columns (i.e., the corresponding field names and field values) of the data table are extracted from the business data, and an SQL query statement such as SELECT column_name, column_value FROM is executed.<business_table> This tool can retrieve the column names (column_name) and corresponding column values ​​(column_value) of a database table. This data reflects the actual storage structure of the business data. The column names represent the names of each column in the database table, and the column values ​​indicate the data in each column. Through the database API, this metadata is extracted from the database and organized into a list of fields. These field names and values ​​will serve as the basis for generating the database form data structure in subsequent steps, thus obtaining the business database table metadata columns. It also retrieves the type dictionary information for each field by executing `SELECT column_name, data_type FROM information_schema.columns WHERE table_name = '`.<business_table> Such a query can retrieve the type of each field from the database's metadata table (such as information_schema.columns). The dictionary of field types consists 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 pickers, and dropdown lists depends on the field type, thus generating the dictionary attributes of the business database table fields. Simultaneously, by summarizing the previously obtained field names, field values, and field types, "cell data information" of the database table is generated. This information includes the basic name of the field, its data value, and the field's type characteristics. All the field metadata information forms a data structure, such as a dictionary or JSON object, representing 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 information about how these fields are displayed on the interface (such as control types).

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

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

[0134] Preferably, the prototype of the database metadata page form is used to generate various SQL drivers for the canvas control, generating various SQL driver statements for the database page form control; based on the various SQL driver statements for the database page form control, the prototype of the database metadata page form is executed with page form delay boosting to generate various form control delay boosting SQL execution statements, including maintenance SQL execution statements, document SQL execution statements, query SQL execution statements, and audit SQL execution statements;

[0135] In this embodiment of the invention, by analyzing and designing the prototype of the database metadata page form, each form prototype corresponds to a specific database entity. The metadata defines the attributes, field types, constraints, and relationships of these entities. By using professional graphical drawing tools (such as UI design tools) for prototype design, form module controls on the user interface (such as retrieval solution modules, page modification solution modules, document extraction solution modules, API solution modules, table editing solution modules, and drawing board solution modules, etc.) are constructed. Once the prototypes of these controls are created, the next task is to generate the corresponding SQL driving statements. In specific implementation, the development tool will automatically generate SQL operation statements corresponding to each control, such as INSERT, UPDATE, DELETE, SELECT, etc., based on the type of form control and the structure of the database table. The SQL driving statements of each control will interact at the database level to ensure that data can be correctly added, deleted, modified, and queried. When generating SQL statements, the tool ensures that the SQL statements comply with database constraints and field types, especially in terms of data type conversion and field mapping, avoiding errors and inconsistencies caused by manual coding. This way, developers do not need to write SQL manually; they can simply generate the corresponding SQL driver by dragging and dropping controls and selecting fields, thereby generating SQL driver statements for various database page form controls. Simultaneously, the previously generated SQL-driven statements are further optimized and designed with delayed execution using development tools. This process first distinguishes different SQL execution requirements. For example, maintenance SQL statements are used for data addition and update operations; document SQL statements are used for specific document generation and processing; query SQL statements are used to display and filter data; and audit SQL statements are used for the data audit process. Each type of SQL statement is embedded into the event-driven logic of form controls, such as submit and query buttons. The tool designs a delayed execution mechanism for each operation (add, query, audit, etc.), delaying the actual execution of the SQL based on certain triggering conditions (such as user operation, page loading, etc.). This delayed execution mechanism avoids unnecessary database operations, optimizes page loading and response time, and improves user experience. In practice, the database-driven tool performs syntax checks on each SQL statement to ensure there are no syntax errors and uses parameterized queries to prevent security issues such as SQL injection. Ultimately, this optimizes the generation of various form controls and improves the delayed SQL execution.

[0136] Preferably, the database metadata page form prototype is optimized in terms of page layout design to generate an optimized database canvas page layout form;

[0137] In this embodiment of the invention, the layout optimization design of the database canvas page mainly focuses on improving the visual presentation and interactive flow of the form. To enhance user convenience and readability, the layout of the form is carefully adjusted using the layout drag-and-drop function in the database canvas module. This 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, enabling non-professional developers to easily create complex application interfaces. For example, the arrangement of fields, the size of controls, the display position of labels, and the color scheme of forms are all optimized according to specific needs. The tool automatically adjusts the position and size of each control based on the field information, length, and type of the database table to avoid the interface being too crowded or difficult to operate. At the same time, based on user interaction habits, the tool also designs a responsive layout for controls to ensure that the form can be displayed correctly on different screen sizes. In addition, appropriate input validation rules are set for each form control to ensure that the data format entered by the user conforms to database constraints, such as the maximum length of text fields and the valid range of numeric fields. Through these layout optimizations, the database page form can achieve high efficiency and ease of use in both visual and functional aspects, ultimately designing and generating an optimized database canvas page form.

[0138] Preferably, 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, document expansion calculations are performed, queries are performed, and positive and negative audit driving operations are performed, thereby driving the development to obtain the corresponding low-code development platform.

[0139] In this embodiment of the invention, specific business operations are designed for the optimized form based on previously generated SQL execution statements (e.g., maintenance SQL statements, document SQL statements, query SQL statements, and audit SQL statements). These operations include form maintenance, querying, document expansion calculation, and auditing. Each operation triggers different SQL statement executions. Maintenance operations typically involve adding and modifying data, and the development tool generates specific SQL statements to perform data insertion and update operations. Query operations generate dynamic query SQL statements based on user input conditions, returning data results that meet the conditions. The query statements are optimized based on factors such as field type and index to improve query efficiency. Document expansion calculation is mainly used to generate and display specific business documents, such as invoices and orders. At this time, corresponding views are generated based on document templates and related database records, and relevant data is automatically populated. Auditing operations generate SQL statements based on business rules to perform positive and negative audits of the data, i.e., "audit comments." For example, in the positive audit stage, the optimized form layout is judged based on the feedback information provided by automatic auditing. To meet project requirements and ensure the accuracy of page display and data interaction, each element in the form is verified, checking for layout and data consistency. It also verifies that SQL execution statements are correctly bound to front-end page elements. If no issues are found, the system interface confirms "approved," triggering the subsequent form deployment process. During the reverse verification phase, if problems are found in the form layout or SQL execution statements, such as non-standard field positions, incorrect data query logic, or abnormal page display, a reverse verification can be triggered, providing suggestions for correction. Users modify the SQL execution statements or adjust the form layout according to the suggestions. After modification, a re-verification is conducted, and the revised feedback result is returned. Each SQL operation is embedded in the corresponding form control, ensuring that the correct SQL statement is executed when the user clicks the corresponding button. Furthermore, the development tool automatically handles parameter binding between form controls and SQL statements, ensuring data consistency and correctness, reducing errors from manual intervention. Ultimately, the low-code platform generates complete backend logic based on these business operations. Developers only need to perform minimal configuration to implement the entire system, thus driving development to obtain the corresponding low-code development platform.

[0140] The above description is merely a specific embodiment of the present invention, enabling those skilled in the art to understand or implement the invention. Various modifications to these embodiments will be readily 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 invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features of the invention herein.

Claims

1. A data-driven low-code development platform, characterized in that, The low-code development platform comprises the following module layers from bottom to top: The data foundation layer includes a field module and a dictionary module. The field module is used to obtain the field names and values ​​corresponding to the business data to obtain the metadata columns of the business database table. The dictionary module is used to obtain the dictionary of field types corresponding to the business data to generate the dictionary attributes of the business database table fields. The metadata columns of the business database table and the dictionary attributes of the business database table fields are used as the metadata information of the database form. The page data layer includes the page front-end representation unit corresponding to the canvas module, which is used to generate page forms from 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 canvas controls of the database metadata page form prototype, and generate various SQL driver statements for the database page form controls. This process involves using SQL-driven statements for various database page form controls to perform delayed execution of the database metadata page form prototype, generating delayed SQL execution statements for various form controls, including maintenance SQL statements, document SQL statements, query SQL statements, and audit SQL statements. The delayed execution of the database metadata page form prototype based on SQL-driven statements for various database page form controls includes: We conduct detailed and in-depth analysis of the SQL driver statements for various database page form controls to obtain the attributes, types, and interaction methods corresponding to the SQL driver statements for each form control. Based on the attributes, types, and interaction methods of the SQL driver statements for various database page form controls, we perform driver dependency evaluation and analysis to generate the relative driver execution dependencies and execution data flow between the SQL driver statements for various form controls. Based on the relative execution dependencies between SQL driver statements of various form controls, the driving duration of SQL driver statements of various database page form controls is monitored to generate the execution driving response duration of SQL driver statements of various form controls; based on the execution driving response duration of SQL driver statements of various form controls, page driving response analysis is performed on the database metadata page form prototype to obtain the SQL statement page form execution driving response efficiency. Based on the execution response time and data flow of SQL driver statements for various form controls, the driving time delay of SQL driver statements for various database page form controls is evaluated and analyzed to obtain the execution time delay of SQL driver statements. Based on the SQL statement page form execution drive response efficiency and SQL statement execution delay, the drive delay timing corresponding to the SQL statement of various database page form controls is adjusted and calculated using the statement drive delay adjustment calculation formula, so as to obtain the drive delay adjustment execution timing corresponding to the SQL statement of various form controls. Based on the execution timing of the SQL driver statements corresponding to various form controls, statement-driven hoisting is performed on the corresponding database page form control SQL driver statements to obtain various database page form SQL driver delay hoisting statements. Based on various database page form SQL-driven deferred boosting statements, the database metadata page form prototype is executed to generate various form control deferred boosting SQL execution statements. The page presentation layer includes the page post-design unit corresponding to the canvas module, which is used to optimize the page layout of the database metadata page form prototype to generate the database canvas page layout optimized form. The business data-driven layer includes a data maintenance module, a document module, a query module, and an approval module. The data maintenance module performs maintenance-driven operations on the database canvas page layout optimization form based on maintenance SQL statements. The document module performs document expansion calculations on the database canvas page layout optimization form based on document SQL statements. The query module performs query-driven operations on the database canvas page layout optimization form based on query SQL statements. The approval module performs positive and negative approval operations on the database canvas page layout optimization form based on approval SQL statements.

2. The data-driven low-code development platform according to claim 1, characterized in that, The various 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 canvas solution module.

3. The data-driven low-code development platform according to claim 2, characterized in that, The process of generating various SQL drivers for the canvas control based on the database metadata page form prototype includes: By pressing the corresponding search control on the canvas module in the search scheme module, the database metadata page form prototype is generated using the search scheme SQL driver, and the database page form search scheme SQL driver statement is generated. By using the page modification scheme module, the corresponding page modification control on the canvas module within the document extraction scheme module is pressed to modify the database metadata page form prototype using SQL driver generation, generating the database page form modification scheme SQL driver statement. By pressing the corresponding document extraction control on the canvas module in the document extraction scheme module, the document extraction SQL driver is generated for the database metadata page form prototype, and the database page form document extraction scheme SQL driver statement is generated. By pressing the corresponding API audit control on the canvas module in the API solution module, the database metadata page form prototype is generated using API audit SQL driver, and the database page form API audit SQL driver statement is generated. By pressing the corresponding table editing control on the canvas module in the table editing scheme module, the SQL driver for table editing of the database metadata page form prototype is generated, and the SQL driver statement for table editing of the database page form is generated. By pressing the corresponding canvas approval control on the canvas module, the canvas approval SQL driver is generated for the database metadata page form prototype, and the database page form approval SQL driver statement is generated.

4. The data-driven low-code development platform according to claim 3, characterized in that, This includes maintaining SQL statements, document SQL statements, query SQL statements, and auditing SQL statements. Maintaining SQL statements includes page modification SQL statements and table editing SQL statements. Page modification SQL statements include running SQL statements, subquery SQL statements, adding or modifying validation SQL statements, and deleting SQL statements. Document SQL statements include document selection SQL statements, summary SQL statements, detail SQL statements, and post-processing SQL statements. Query SQL statements include retrieving preceding SQL statements and retrieving following SQL statements. Auditing SQL statements include API auditing SQL statements and form scheme auditing SQL statements.

5. The data-driven low-code development platform according to claim 4, characterized in that, The specific formula for calculating the statement-driven delay adjustment is as follows: In the formula, T i The execution timing of the driver delay is adjusted for the SQL driver statement corresponding to the i-th type of form control, where n is the total number of SQL driver statements for form controls, and i is the item index of the SQL driver statement for the form control. This represents the start time of statement execution corresponding to the SQL driving statement for the i-th type of form control. Let t be the execution end time of the SQL statement corresponding to the i-th type of form control, τ be the statement execution time variable parameter, and D be the integral time component. i (t) represents the interaction complexity of the form control at time t, where α is the SQL driving statement for the i-th type of form control. i Adjust the interaction complexity factor for the SQL driving statement corresponding to the i-th type of form control. Let β be the execution resource consumption of the SQL driving statement for the i-th type of form control at time t. i Let Q(τ) be the resource consumption impact adjustment coefficient corresponding to the SQL driving statement for the i-th type of form control, and let Q(τ) be the SQL statement page form execution driving response efficiency at time τ. s γ is the delay in the execution of SQL-driven statements. i η is the execution response delay weighting coefficient corresponding to the SQL driving statement of the i-th type of form control, and η is the correction coefficient for adjusting the timing of the driving delay.

6. The data-driven low-code development platform according to claim 4, characterized in that, The maintenance-driven operation for optimizing the database canvas page layout form based on maintenance SQL execution statements includes: The SQL statement for table editing drives the page form editing of the database canvas page layout optimization form. The SQL statement is executed and the page editing is interpreted and executed. When the page editing is executed by clicking the page editing run button, the execution result is displayed in the details table below the canvas module. The database canvas page layout optimization form is driven by a subquery SQL execution statement. Clicking the subquery run button on the page will execute the configuration page form subquery detail table. The database canvas page layout optimization form is added or modified based on the SQL statement to be added or modified. Clicking the "Add or Modify" button on the page will execute the corresponding database verification and maintenance job before the form was added or modified. The SQL statement for deleting forms is used to drive the deletion of forms on the database canvas page layout optimization form. Clicking the "Delete Form Run" button on the page will then execute the form deletion maintenance job.

7. The data-driven low-code development platform according to claim 4, characterized in that, The document expansion calculation-driven operation for optimizing the database canvas page layout form based on document SQL execution statements includes: Based on the document selection SQL execution statement, the database canvas page layout optimization form is executed with document selection driven execution, which drives the click of the document selection run button to execute the page document selection driven job; Based on the summary SQL execution statement, the form of the database canvas page layout optimization is executed by summarizing the documents. Clicking the document summary run button will then execute the document summary driven job on the page. Based on the detailed SQL execution statement, the database canvas page layout optimization form is executed in a document detail-driven manner, so that the page document selection or summary corresponding detailed information is filled into the document detail table below; This involves performing a post-execution job on the database canvas page layout optimization form based on a SQL statement.

8. The data-driven low-code development platform according to claim 4, characterized in that, The query-driven operation for optimizing the database canvas page layout form based on SQL query execution statements includes: The database canvas page layout optimization form is driven by a pre-retrieval SQL execution statement to perform corresponding page form summary and detailed summary operations. This is a post-retrieval validation-driven job based on the SQL execution statement following the retrieval, which performs a post-retrieval validation on the database page forms after the preceding retrieval.

9. The data-driven low-code development platform according to claim 4, characterized in that, The positive and negative audit-driven operation for optimizing the database canvas page layout form based on audit SQL execution statements includes: API-driven auditing of database canvas page layout optimization forms based on SQL execution statements for auditing; Based on the form-based scheme, SQL execution statements are used to perform positive and negative review operations on the database canvas page layout optimization form after API-driven review.

10. A data-driven low-code development method, characterized in that, Applied to the data-driven low-code development platform as described in claim 1, the data-driven low-code development method includes the following steps: Obtain the field names and values ​​corresponding to the business data to get the business database table metadata columns; obtain the field type dictionary corresponding to the business data to generate the business database table field dictionary attributes; use the business database table metadata columns and business database table field dictionary attributes as database form metadata information; Generate a page form from the database form metadata information to generate a prototype of the database metadata page form; The database metadata page form prototype generates various SQL drivers for canvas controls, producing SQL driver statements for various database page form controls. Based on these SQL driver statements, the database metadata page form prototype is then executed with page form delay boosting to generate various form control delay boosting SQL execution statements, including maintenance SQL execution statements, document SQL execution statements, query SQL execution statements, and audit SQL execution statements. The page layout of the database metadata page form prototype is optimized to generate an optimized database canvas page layout form. Based on the maintenance of SQL execution statements, document SQL execution statements, query SQL execution statements, and audit SQL execution statements, the database canvas page layout optimization forms are maintained, documents are expanded and calculated, queries are performed, and positive and negative auditing are driven, thereby driving the development of a corresponding low-code development platform.

Images