Database model established for low-code platform

Abstract

A database model established for a low-code platform is characterized by comprising an engineering basic information table, a component definition table, a component type table, an engineering component association table, an engineering variable table, an engineering event registry, a data source registry, a data set registry and a data set field definition table, the model designed by the invention adopts a standardized structure, so that data storage and management are more orderly, subsequent data maintenance and query are facilitated, and the problems of data redundancy and inconsistency are reduced. Through the clearly defined table relation and foreign key constraint, the user can more effectively manage the relation between the data, the integrity and consistency of the data are ensured, and the efficiency of data operation is improved. The method can adapt to various business scenes and requirements, a user can easily adjust and expand the data model according to different business logics, and the expandability and adaptability of the system are enhanced. According to the invention, through reasonable database design, the capability of data-driven decision making is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of low-code development platforms, and specifically relates to a database model for building a low-code platform. Background Art

[0002] With the continuous deepening of the digital transformation of enterprises, the traditional software development model is facing increasingly severe challenges. Traditional development usually relies on professional technical teams for multiple links such as requirements analysis, system architecture design, coding implementation, and software testing. This not only has a long cycle and high cost, but also makes it difficult for enterprises to quickly adapt to market changes. In addition, the participation of non-technical personnel in business requirement definition and system design is relatively low, often resulting in a mismatch between the final product and actual requirements, thus affecting work efficiency and user experience.

[0003] Against this background, low-code development platforms have emerged. Low-code platforms enable users to quickly build applications that meet business requirements through simple dragging and configuration by providing a visual development environment, a component-based design concept, and rich template resources. However, existing low-code platforms still have certain limitations in aspects such as database model support, front-end and back-end API linkage processing, and user-defined interface design. This makes users still likely to face problems such as low development efficiency, inconvenient use, and limited functions even when using low-code platforms. Summary of the Invention

[0004] In view of the above problems, the present invention is proposed to provide a database model for building a low-code platform that overcomes the above problems or at least partially solves the above problems.

[0005] To solve the above technical problems, the embodiments of the present application disclose the following technical solutions:

[0006] The embodiments of the present invention disclose a database model for building a low-code platform, which is characterized by including: an engineering basic information table, a component definition table, a component type table, an engineering component association table, an engineering variable table, an engineering event registration table, a data source registration table, a data set registration table, and a data set field definition table; where:

[0007] The engineering basic information table is used to record the basic information of the project, and all the configuration data is associated and extended based on a specific project;

[0008] The component definition table is used to define all unit components in the platform construction, and at least includes the component code path, component type, component name, component default parameters, and component default UI information;

[0009] The component type table is used to define the types of all unit components, and is also used to organize the component directory tree of the platform interface through self-associated fields;

[0010] Engineering component association table, which is used to associate the basic engineering information table and the component definition table, store all component information associated under the project, as well as UI layout parameters, component configuration parameters, etc. of each component under the project;

[0011] Engineering variable table, which is used to define global variables used inside the project, uniformly constrain the data of multiple components, or perform dynamic update response processing for other scenarios;

[0012] Engineering event registration table, which is used to store event interaction configuration information between components in the project, connect each component in the project, and achieve various linkage interaction effects;

[0013] Data source registration table, which is used to define a record for different types of data sources, perform relevant configurations, and the server will establish a data connection in the background according to the configuration to obtain data;

[0014] Dataset registration table, which is used to configure specific datasets on the background service platform based on the defined data source registration table, and configure them to unit components or engineering variables when building the platform through the configured datasets;

[0015] Dataset field definition table, which is used to serve the dataset registration table, and make detailed descriptions of the field information of the data interface return results, including at least field aliases and field types, to facilitate field mapping matching when configuring the front-end page.

[0016] Further, the field information of the basic engineering information table at least includes engineering code, engineering name, engineering password, whether the project is shared, username of the person creating the project, user ID of the person creating the project, time of creating the project, and time of the last change and save of the project; among them, the engineering code is a unique value and will be used as a foreign key association in other associated information tables.

[0017] Further, the field information of the component definition table at least includes system number, component code, component's remarks name, component category, path of the component corresponding logic code file, component style configuration, component default parameter object, component effect preview diagram, registration configuration item; among them, the component code is a unique value and is used as a foreign key association in other associated information tables; the component category is used as a foreign key to associate the category code field in the component type table.

[0018] Further, the field information of the component type table includes at least a type number, a category name, an associated category code, and the arrangement order of the category at the current level; among them, the type number is used as a unique value and is used as a foreign key for association in the component definition table. The associated category code is used to associate the code of the upper-level category and is self-associated with the category code field. When the value of the associated category code is empty, the current category is the root-level category.

[0019] Further, the field information of the engineering component association table includes at least a system number, an engineering code, a component code, a component value, a component parameter configuration object, a component UI layout configuration object, and a custom component alias; among them, the engineering code is used as a foreign key to associate the engineering code field of the engineering basic information table; the component code is used as a foreign key to associate the component code field of the component definition table; the component parameter configuration object has a higher priority than the component default parameter object of the component definition table; the component UI layout configuration object has a higher priority than the component style configuration of the component definition table.

[0020] Further, the field information of the engineering variable table includes at least a system number, an engineering name, a variable name, a method for obtaining the variable value, a parameter object for data source acquisition, whether the variable needs to be automatically updated, the automatic update frequency of the variable, the name of the variable creator, the id of the variable creator, and the variable creation time; among them, the engineering name is used as a foreign key to associate the engineering code field of the engineering basic information table; the method for obtaining the variable value includes static data and service interfaces.

[0021] Further, the field information of the engineering event registration form at least includes system number, interaction event name, interaction event code, engineering code, component code of the event thrown, component value of the event thrown, name of the component throwing the event, pre-filter for the thrown event, interaction action name, interaction action type, target component code, target component value, action type for the target component, parameter configuration object of the target component, name of the target component function to be called, parameter acquisition logic code of the target component function to be called, routing name of the new page to be jumped to, parameter acquisition logic code of the new page route to be jumped to, custom execution code snippet, engineering variable name to be updated, engineering variable value acquisition logic code to be updated, name of the interaction action creator, id of the interaction action creator, interaction action creation time; among them, the engineering code is used as a foreign key to associate with the process code field of the engineering basic information table; the component code of the event thrown is used as a foreign key to associate with the component code field of the engineering component association table; the component value of the event thrown is used as a foreign key to associate with the component value field of the engineering component association table; the interaction action type includes operating the target component, page jump, executing custom code snippet, updating global variables; the target component code is associated with the component code field of the engineering component association table; the action type for the target component includes switching development, displaying, hiding, updating component configuration, refreshing, calling the target component function; the parameter configuration object of the target component corresponds to the component parameter object in the engineering component association table.

[0022] Further, the field information of the data source registration form at least includes data source code, data source type, detailed parameters of the data source, data source name, database type, database operation object; the database type at least includes Oracle, MySql, PostgreSQL, SqlServer.

[0023] Further, the field information of the data set registration form at least includes data set code, data set name, detailed parameters of the data set, arrangement order of data sets within the same level, data set type, data source code, value of the data table name or SQL expression; the data set type at least includes pure directory, static data, custom Sql, global function, internal interface, third-party interface, custom code snippet, service directory, Excel file, Shp file; the data source code is used as a foreign key to associate with the data source code of the data source registration form associated with the data source registration form.

[0024] Further, the field information of the data set field definition table at least includes data set code, field name in the interface return result, custom-configured field alias, whether the value corresponding to the field is of numeric type, field arrangement order, field type, field enumeration value; among them, the data set code is used as a foreign key to associate with the data set code field of the data set registration form; the field type includes numeric, text, dropdown, date and time.

[0025] The beneficial effects of the above technical solutions provided by the embodiments of the present invention at least include:

[0026] The present invention discloses a database model for building a low-code platform, which is characterized by including: an engineering basic information table, a component definition table, a component type table, an engineering component association table, an engineering variable table, an engineering event registration table, a data source registration table, a dataset registration table, and a dataset field definition table; The database model design model proposed in this patent of the present invention has the following beneficial effects:

[0027] 1. Structuring and standardization

[0028] The database design model adopts a standardized structure, making data storage and management more orderly, facilitating subsequent data maintenance and query, and reducing the problems of data redundancy and inconsistency.

[0029] 2. Efficient data relationship management

[0030] Through clearly defined table relationships and foreign key constraints, users can more effectively manage the relationships between data, ensure data integrity and consistency, and improve the efficiency of data operations.

[0031] 3. Support for multiple business scenarios

[0032] The model design is flexible and can adapt to multiple business scenarios and requirements. Users can easily adjust and expand the data model according to different business logics, enhancing the scalability and adaptability of the system.

[0033] 4. Simplify data analysis and decision support

[0034] Through reasonable database design, users can quickly generate data reports and analysis results, thereby providing strong support for business decisions and enhancing the ability of data-driven decision-making.

[0035] Next, through the drawings and embodiments, the technical solutions of the present invention will be further described in detail. Description of the Drawings

[0036] The drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation to the present invention. In the drawings:

[0037] Figure 1 It is a flowchart of a database model for building a low-code platform in Embodiment 1 of the present invention. Detailed Embodiments

[0038] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided so that the present disclosure can be more thoroughly understood and the scope of the present disclosure can be fully conveyed to those skilled in the art.

[0039] To solve the problems existing in the prior art, an embodiment of the present invention provides a database model for building a low-code platform.

[0040] Embodiment 1

[0041] The present invention discloses a database model for building a low-code platform, such as Figure 1 , including: project basic information table, component definition table, component type table, project-component association table, project variable table, project event registration table, data source registration table, dataset registration table, and dataset field definition table; where:

[0042] The project basic information table is used to record the basic information of the project, and the configuration data is associated and extended based on a specific project; the project basic information table is the core CPU of the entire low-code platform, and all configuration data is associated and extended based on a specific project. When a user builds the platform, they need to first create a project, and then select the created project before they can perform subsequent operations.

[0043] Specifically, as shown in Table 1, in this embodiment, the field information of the project basic information table cx_datav_project includes at least project code, project name, project password, whether the project is shared, username of the user who created the project, user ID of the user who created the project, creation time of the project, and the time when the project was last saved after modification; among them, the project code is a unique value and will be used as a foreign key association in other associated information tables.

[0044] Table 1 Project basic information table cx_datav_project

[0045]

[0046]

[0047] Specifically, after creating a project, the user can manually set a password for the project. After setting, password verification will be performed before saving subsequent changes to ensure data security. Considering that sometimes it is necessary to share the project with other users for reference on the large-screen configuration, a field configuration for whether to share is provided, and the project creator can decide whether to share the project. For shared projects, we also impose editing restrictions. Only the project creator can edit, and other users can only view, ensuring the data stability of the project.

[0048] The component definition table is used to define all unit components in the platform construction, including at least the component code path, component type, component name, component default parameters, and component default UI information; the component registration table is a definition table for all unit components in the platform construction, similar to all the small building block components in a building block game. Each component that can be used in the platform construction needs to have a corresponding registration record in the cx_comconf table, which contains information such as the component code path, component type, component name, component default parameters, and component default UI.

[0049] In this embodiment, as shown in Table 2, the field information of the component definition table cx_comconf includes at least the system number, component code, component's note name, component category, path of the component corresponding logical code file, component style configuration, component default parameter object, component effect preview diagram, and registration configuration item; among them, the component code is a unique value and is used as a foreign key in other associated information tables; the component category is used as a foreign key to associate with the category code field in the component type table.

[0050] Table 2 Component Definition Table cx_comconf

[0051]

[0052]

[0053] Specifically, the component definition table is the basic resource library of the entire low-code platform. As the saying goes, even the most skillful housewife can't cook a meal without rice. What this table stores is the rice of the entire platform. When constructing different project pages, they are all composed of various components in this table.

[0054] The Uicfg field mainly stores the style of the initial state of components, such as width, height, background color, padding, etc. The Params field is mainly used to store some parameter configuration objects customized for components. Considering subsequent extensibility, we also support generating a new component by combining existing components, and then dynamically registering the new component into this table as a new unit component. What the registerconf stores are the other sub-components associated with the registration. In this way, when rendering, by reading the registerconf configuration information, the loading can be fully restored.

[0055] The component type table is used to define the types of all unit components and is also used to organize the component directory tree of the platform interface through self-associated fields; the component type table mainly has two functions: 1. Define the types of all unit components. 2. Organize the component directory tree of the platform interface through self-associated fields.

[0056] In this embodiment, as shown in Table 3, the field information of the component type table cx_comcategory includes at least the type number, category name, associated category code, and the arrangement order of the category at the current level; among them, the type number is used as a unique value and is used as a foreign key association in the component definition table. The associated category code is used to associate the code of the superior category and is self-associated with the category code field. When the value of the associated category code is empty, the current category is the root-level category.

[0057] Table 3 Component type table cx_comcategory

[0058]

[0059]

[0060] The component type table is mainly used when constructing the component tree in the design interface. According to the self-associated relationship of the two fields code and glcode, a recursive algorithm is used to construct the tree structure data. Then, under each category, the component data is queried and filtered according to the value of the category field in the cx_comconf table and then mounted under the corresponding category node. In this way, the complete component directory tree is constructed.

[0061] The engineering component association table is used to associate the basic engineering information table and the component definition table, store all the component information associated under the project, as well as information such as the UI layout parameters and component configuration parameters of each component under this project; the engineering component association table is used to store all the component information associated under a certain project, as well as information such as the UI layout parameters and component configuration parameters of each component under this project. Through this table, the cx_datav_project and cx_comconf tables are associated. For each complete engineering page, there will be a corresponding component list in this table. The front end realizes the rendering and restoration on the interface through this configuration list.

[0062] In this embodiment, as shown in Table 4, the field information of the engineering component association table cx_plugincoms at least includes system number, project code, component code, component value, component parameter configuration object, component UI layout configuration object, and custom component alias; among them, the project code is used as a foreign key to associate the project code field of the basic engineering information table; the component code is used as a foreign key to associate the component code field of the component definition table; the component parameter configuration object has a higher priority than the component default parameter object in the component definition table; the component UI layout configuration object has a higher priority than the component style configuration in the component definition table.

[0063] Table 4 Engineering Component Association Table cx_plugincoms

[0064]

[0065]

[0066] Specifically, the data in the engineering component association table will be updated, such as adding, deleting, and modifying, every time the project is saved. Among them, plugname and comname are used as two foreign keys, externally linked to the name field of cx_datav_project and the name field of cx_comconf, which can ensure the association constraint limit when deleting projects and components, and ensure the stability of the project.

[0067] Among them, the comcode field is to solve the problem that in a project, when the same component A is referenced multiple times, it is impossible to distinguish specific objects only based on plugname and comname. Therefore, a unique key value will be assigned to each component in the project as an identifier.

[0068] The storage format of Comparam is the same as the params format of the component in cx_comconf, but it has a higher priority. When the front end renders, a deep merge process of the objects will be performed.

[0069] The uicfg storage format is the same as the uicfg format of components in cx_comconf, but with a higher priority. During front-end rendering, deep merging of objects will be performed.

[0070] Comalias mainly solves the problem that when viewing the list of each component or selecting component mapping in the front end, the function and role of the component can be known more clearly and intuitively through the alias.

[0071] The project variable table is used to define global variables used within the project, uniformly constrain the data of multiple components, or perform dynamic update response processing for other scenarios; the project variable table is used to define some internal global variables for the current project, facilitating the unified constraint of the data of multiple components, or performing dynamic update response processing for other scenarios.

[0072] For example, for this scenario: there is a large-screen page, and when switching different regions, the data of multiple statistical cards needs to be obtained and dynamically changed according to the selected region. In the above scenario, when implementing, we can create a variable xzqid for this large-screen project, with the value being the currently selected region ID, and then the data interfaces of the statistical cards that need to be filtered are uniformly filtered using this variable. In this way, when the variable value changes, the front end will refresh all components that depend on this variable.

[0073] In this embodiment, as shown in Table 5, the field information of the project variable table cx_plugvariable includes at least system number, project name, variable name, variable value acquisition method, parameter object for data source acquisition, whether the variable needs to be automatically updated, variable automatic update frequency, variable creator name, variable creator id, and variable creation time; among them, the project name is associated with the project coding field of the project basic information table as a foreign key; the variable value acquisition method includes static data and service interfaces.

[0074] Table 5 Project variable table cx_plugvariable

[0075]

[0076] After the variable is created, regarding how to obtain the value of the variable, we have designed two acquisition methods:

[0077] (1). Static data. The user directly enters a fixed value as the variable value for use.

[0078] (2). Data interface. The user can select a configured data interface, and the variable value will use the result returned by the data interface.

[0079] Variables also support setting an automatic update mode, which is mainly used to solve the problem of data monitoring dashboards that require real-time viewing of data change status. By enabling autoupdate and setting the automatic update frequency frequency, the front end creates a poller for this variable. Each time a poll is made, the variable value is re-obtained according to the configuration, and then all unit components that use this variable value are updated.

[0080] The project event registry is used to store the event interaction configuration information between various components in the project, connect various components in the project, and achieve various linkage interaction effects; the project event registry is used to store the event interaction configuration information between various components in our project, acting as bridges to connect various components and achieve various linkage interaction effects.

[0081] In this embodiment, as shown in Table 6, the field information of the project event registry cx_plugevents includes at least system number, interaction event name, interaction event code, project code, component code that throws the event, component value that throws the event, name of the component throwing the event, pre-filter for the thrown event, interaction action name, interaction action type, target component code, target component value, action type for the target component, parameter configuration object of the target component, name of the target component function to be called, parameter acquisition logic code of the target component function to be called, route name of the new page to be jumped to, parameter acquisition logic code of the new page route to be jumped to, custom execution code snippet, name of the project variable to be updated, variable value acquisition logic code of the project variable to be updated, name of the interaction action creator, id of the interaction action creator, and creation time of the interaction action; among them, the project code is used as a foreign key to associate with the process code field of the project basic information table; the component code that throws the event is used as a foreign key to associate with the component code field of the project component association table; the component value that throws the event is used as a foreign key to associate with the component value field of the project component association table; the interaction action type includes operating the target component, page jump, executing a custom code snippet, and updating global variables; the target component code is associated with the component code field of the project component association table; the action type for the target component includes switching development, displaying, hiding, updating component configuration, refreshing, and calling the target component function; the parameter configuration object of the target component corresponds to the component parameter object in the project component association table.

[0082] Table 6 Project Event Registry cx_plugevents

[0083]

[0084]

[0085] Data source registration table, which is used to define a record for different types of data sources, perform relevant configurations, and the server will establish a data connection in the background according to the configurations to obtain data; the data interface sources faced by the low-code platform may be diverse: excel files, online interfaces, different types of databases, Internet of Things interfaces, etc. For the diverse data sources, we have established a data source registration table, where a record can be defined for different types of data sources, relevant configurations can be performed, and the server will establish a data connection in the background according to the configurations to obtain data.

[0086] In this embodiment, as shown in Table 7, the field information of the data source registration table cx_sysds includes at least data source code, data source type, detailed parameters of the data source, data source name, database type, and database operation object; the database type includes at least Oracle, MySql, PostgreSQL, and SqlServer.

[0087] Table 7 Data source registration table cx_sysds

[0088]

[0089] Dataset registration table, which is used to, based on the defined data source registration table, configure specific datasets in the background service platform, and configure them to unit components or engineering variables when building the platform; the dataset table is based on the defined data source cx_sysds and configures specific datasets in the background service platform.

[0090] In this embodiment, as shown in Table 8, the field information of the dataset registration table cx_dataset includes at least dataset code, dataset name, detailed parameters of the dataset, arrangement order of datasets within the same level, dataset type, data source code, value of the data table name or SQL expression; the dataset type includes at least pure directory, static data, custom Sql, global function, internal interface, third-party interface, custom code snippet, service directory, Excel file, and Shp file; the data source code is used as a foreign key to associate with the data source code of the data source registration table.

[0091] Table 8 Dataset registration table cx_dataset

[0092]

[0093]

[0094] The no and glno fields in Table 8 have a self - associative relationship. In the background service management platform, a dataset directory tree will be constructed based on these two fields. The dataset supports multiple different types (static data, custom Sql, global functions, internal interfaces, third - party interfaces, custom code snippets, service catalogs, Excel files, Shp files), which can basically meet various scenarios of data interfaces.

[0095] The dataset field definition table is used for the service dataset registration table to elaborate on the field information of the data interface return results, including at least the field alias and field type, which is convenient for field mapping and matching on the front - end configuration page. The dataset field definition table serves the cx_dataset table and is used to elaborate on the field information of the data interface return results, including field aliases, field types, etc., which is convenient for field mapping and matching on the front - end configuration page.

[0096] In this embodiment, as shown in Table 9, the field information of the dataset field definition table cx_datafld includes at least the dataset code, the field name in the interface return result, the custom - configured field alias, whether the corresponding value of the field is a numeric type, the field sorting order, the field type, and the field enumeration value; among them, the dataset code is used as a foreign key to associate with the dataset code field of the dataset registration table; the field types include numeric, text, dropdown, date, and time.

[0097] Table 9 Dataset Field Definition Table cx_datafld

[0098]

[0099] This embodiment discloses a database model for building a low - code platform, which includes: project basic information table, component definition table, component type table, project - component association table, project variable table, project event registration table, data source registration table, dataset registration table, and dataset field definition table; the database model for building a low - code platform proposed in this embodiment has the following beneficial effects:

[0100] 1. Structured and standardized

[0101] The database design model adopts a standardized structure, making data storage and management more orderly, facilitating subsequent data maintenance and query, and reducing the problems of data redundancy and inconsistency.

[0102] 2. Efficient data relationship management

[0103] Through clearly defined table relationships and foreign key constraints, users can more effectively manage the relationships between data, ensure data integrity and consistency, and improve the efficiency of data operations.

[0104] 3. Support multiple business scenarios

[0105] The model is flexibly designed to adapt to a variety of business scenarios and needs. Users can easily adjust and expand the data model according to different business logics, enhancing the scalability and adaptability of the system.

[0106] 4. Simplify data analysis and decision support

[0107] Through reasonable database design, users can quickly generate data reports and analysis results, thereby providing strong support for business decisions and improving the ability to make data-driven decisions.

[0108] It should be understood that the specific order or hierarchy of steps in the disclosed process is an example of an exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the process can be rearranged without departing from the scope of protection of the present disclosure. The attached method claims present the elements of the various steps in an exemplary order and are not intended to be limited to the specific order or hierarchy described.

[0109] In the above detailed description, various features are grouped together in a single embodiment to simplify the disclosure. This method of disclosure should not be interpreted as reflecting an intention that the embodiments of the claimed subject matter require more features than are clearly stated in each claim. On the contrary, as reflected in the appended claims, the invention is in a state of having less than all the features of the disclosed individual embodiments. Therefore, the appended claims are hereby expressly incorporated into the detailed description, with each claim standing on its own as a separate preferred embodiment of the invention.

[0110] Those skilled in the art will also appreciate that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in conjunction with the embodiments herein can all be implemented as electronic hardware, computer software, or a combination thereof. In order to clearly illustrate the interchangeability between hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above around their functions. Whether such functions are implemented as hardware or software depends on specific applications and the design constraints imposed on the entire system. A skilled person can implement the described functions in an alternative manner for each specific application, but such implementation decisions should not be interpreted as departing from the scope of protection of the present disclosure.

[0111] The steps of the methods or algorithms described in connection with the embodiments of this specification may be directly embodied as hardware, software modules executed by a processor, or a combination thereof. The software modules may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium well known in the art. An exemplary storage medium is connected to the processor so that the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The ASIC may be located in a user terminal. Of course, the processor and the storage medium may also exist as discrete components in the user terminal.

[0112] For a software implementation, the techniques described in this application may be implemented using modules (e.g., procedures, functions, etc.) that perform the functions described in this application. These software codes may be stored in a memory unit and executed by a processor. The memory unit may be implemented within the processor or outside the processor, and in the latter case, it is communicatively coupled to the processor by various means, which are well known in the art.

[0113] The above description includes examples of one or more embodiments. Of course, it is not possible to describe all possible combinations of components or methods for the purpose of describing the above embodiments, but those of ordinary skill in the art should recognize that the various embodiments may be further combined and arranged. Accordingly, the embodiments described herein are intended to cover all such changes, modifications, and variations that fall within the scope of the appended claims. In addition, with respect to the term "comprising" used in the specification or claims, this term is inclusive in a manner similar to the term "including" as interpreted when used as a transitional word in a claim. Further, any use of the term "or" in the claims or specification is to mean "non-exclusive or".

Claims

1. A database model for low-code platform construction, characterized in that: include: Project basic information table, component definition table, component type table, project component association table, project variable table, project event registry, data source registry, data set registry, and data set field definition table; among which: The project basic information table is used to record the basic information of the project. The configuration data is associated and extended based on a specific project. The component definition table is used to define all unit components in the platform construction, including at least component code path, component type, component name, component default parameters, and component default UI information; The component type table is used to define the types of all unit components and to organize the component directory tree of the platform interface through self-association fields; The project component association table is used to associate the project basic information table with the component definition table, store all component information associated with the project, as well as the UI layout parameters, component configuration parameters and other information of each component in the project; Project variable table, used to define global variables used within the project, to uniformly constrain the data of multiple components, or to dynamically update and respond to other scenarios; The project event registry is used to store the event interaction configuration information between various components in the project, connect various components in the project, and achieve various linkage interaction effects; The data source registry is used to define a record for different types of data sources and perform related configurations. The server will establish a data connection in the background according to the configuration to obtain data; The data set registry is used to configure specific data sets through the background service platform based on the defined data source registry. The configured data sets are configured to unit components or project variables when the platform is built. The dataset field definition table is used to serve the dataset registry. It provides detailed descriptions of the field information of the results returned by the data interface, including at least the field alias and field type, to facilitate field mapping and matching when configuring the front-end page.

2. A database model for building a low-code platform as described in claim 1, characterized in that: The field information of the project basic information table includes at least the project code, project name, project password, whether the project is shared, the user name of the project creator, the user ID of the project creator, the time when the project was created, and the time when the latest change to the project was saved; among them, the project code is a unique value and will be used as a foreign key association in other related information tables.

3. A database model for building a low-code platform as described in claim 1, characterized in that: The field information of the component definition table includes at least the system number, component code, component remark name, component category, path of the component corresponding logic code file, component style configuration, component default parameter object, component effect preview image, and registration configuration items; the component code is a unique value and is used as a foreign key association in other related information tables; the component category is used as a foreign key to associate the category code field in the component type table.

4. A database model for building a low-code platform as described in claim 1, characterized in that: The field information of the component type table includes at least the type number, category name, associated category code, and the order of categories at the current level; among them, the type number is used as a unique value and is used as a foreign key association in the component definition table. The associated category code is used to associate with the code of the parent category and is self-associated with the category code field. When the value of the associated category code is empty, the current category is the root category.

5. A database model for building a low-code platform as described in claim 1, characterized in that: The field information of the project component association table at least includes system number, project code, component code, component value, component parameter configuration object, component UI layout configuration object, and custom component alias; The project code is used as a foreign key to associate with the project code field in the project basic information table; the component code is used as a foreign key to associate with the component code field in the component definition table; the component parameter configuration object has a higher priority than the component default parameter object in the component definition table; the component UI layout configuration object has a higher priority than the component style configuration in the component definition table.

6. A database model for building a low-code platform as described in claim 1, characterized in that: The field information of the project variable table includes at least the system number, project name, variable name, method for obtaining variable values, parameter object obtained by the data source, whether the variable needs to be automatically updated, frequency of automatic variable updates, name of the variable creator, id of the variable creator, and time of variable creation; among them, the project name is used as a foreign key to associate with the project code field of the project basic information table; methods for obtaining variable values ​​include static data and service interfaces.

7. A database model for building a low-code platform as described in claim 1, characterized in that: The field information of the project event registry includes at least the system number, the interactive event name, the interactive event code, the project code, the component code of the thrown event, the component value of the thrown event, the name of the component thrown event, the pre-filter for the thrown event, the interactive action name, the interactive action type, the target component code, the target component value, the action type for the target component, the parameter configuration object of the target component, the name of the target component function to be called, the parameter acquisition logic code of the target component function to be called, the route name of the new page to be jumped, the parameter acquisition logic code of the new page route to be jumped, the custom executed code snippet, the project variable name to be updated, the project variable value acquisition logic code to be updated, and the creator of the interactive action. Name, interaction creator id, interaction creation time; among them, the project code is used as a foreign key to associate with the process code field of the project basic information table; the component code of the thrown event is used as a foreign key to associate with the component code field of the project component association table; the component value of the thrown event is used as a foreign key to associate with the component value field of the project component association table; the interaction action types include operating the target component, page jump, executing custom code snippets, and updating global variables; the target component code is associated with the component code field of the project component association table; the action types for the target component include switching display, showing, hiding, updating component configuration, refreshing, and calling target component functions; the parameter configuration object of the target component corresponds to the component parameter object in the project component association table.

8. A database model for building a low-code platform as described in claim 1, characterized in that: The field information of the data source registry includes at least the data source code, data source type, detailed parameters of the data source, data source name, database type, and database operation object; the database types include at least Oracle, MySql, PostgreSQL, and SqlServer.

9. A database model for building a low-code platform as described in claim 1, characterized in that: The field information of the dataset registration table shall at least include the dataset code, dataset name, detailed parameters of the dataset, the order of datasets in the same level, dataset type, data source code, data table name or the value of SQL expression; Data set types include at least pure directory, static data, custom SQL, global function, internal interface, third-party interface, custom code snippet, service directory, Excel file, Shp file; The data source code is used as a foreign key to associate the data source registry with the data source code of the data source registry.

10. A database model for building a low-code platform as described in claim 1, characterized in that: The field information of the dataset field definition table includes at least the dataset code, the field name in the interface return result, the custom configured field alias, whether the value corresponding to the field is a numeric type, the field arrangement order, the field type, and the field enumeration value; among them, the dataset code is used as a foreign key to associate the dataset code field of the dataset registry; the field types include numeric, text, drop-down, date, and time.

Images