Method, device, equipment, storage medium and program product for generating domain model

Abstract

The application provides a method, device, equipment, storage medium and program product for generating a domain model. The method comprises: obtaining a structured data file and a table creation statement file corresponding to a database table of a system to be developed; determining association information between any two database tables according to the structured data file and the table creation statement file corresponding to the database table; extracting a table name and table field information of the database table from the table creation statement file of the database table, and generating a domain model corresponding to the database table according to the table name and table field information of the database table; and determining association information between domain models corresponding to any two database tables according to the data association information and the primary-foreign key association information between the two database tables, thereby generating a domain model reversely according to an existing database table and determining the association information between the domain models corresponding to any two database tables.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, device, storage medium, and program product for generating domain models. Background Technology

[0002] Low-code development platforms are primarily aimed at "non-programmers" (non-professional developers, such as business product and operations personnel, who lack practical coding experience) within the business domain. Essentially, low-code reduces the difficulty and improves efficiency for developers by leveraging various model capabilities (such as metadata models, business object models, online script engines, workflow models, business flow models, and platform programming models). In low-code development platforms, the domain model is the foundation of system application development.

[0003] To involve more application stakeholders beyond traditional developers in the application building process, low-code development platforms are needed. Rebuilding or updating existing system applications using low-code platforms requires reverse engineering existing database tables to generate domain models and the relationships between them. Therefore, a method for reverse engineering domain models and their relationships based on database tables is urgently needed. Summary of the Invention

[0004] This application provides a method, apparatus, device, storage medium, and program product for generating a domain model, used to reverse-generate a domain model based on a database table.

[0005] On the one hand, this application provides a method for generating a domain model, including:

[0006] Obtain the structured data files and table creation statement files corresponding to the database tables of the system to be developed;

[0007] Based on the structured data files corresponding to the database tables, perform association analysis on the structured data files of any two database tables to determine the data association information between the two database tables, and determine the primary and foreign key association information between any two database tables based on the table creation statement files of the database tables.

[0008] Extract the table name and table field information of the database table from the table creation statement file, and generate the domain model corresponding to the database table based on the table name and table field information.

[0009] Based on the data association information and primary and foreign key association information between any two database tables, determine the association information between the domain models corresponding to any two database tables.

[0010] On the other hand, this application provides an apparatus for generating a domain model, comprising:

[0011] The file acquisition module is used to acquire the structured data files and table creation statement files corresponding to the database tables of the system to be developed.

[0012] The inter-table association information determination module is used to perform association analysis processing on the structured data files of any two database tables based on the structured data files corresponding to the database tables, determine the data association information between the two database tables, and determine the primary and foreign key association information between any two database tables based on the table creation statement file of the database tables.

[0013] The domain model determination module is used to extract the table name and table field information of the database table from the table creation statement file of the database table, and generate the domain model corresponding to the database table based on the table name and table field information.

[0014] The domain model association information determination module is used to determine the association information between the domain models corresponding to any two database tables based on the data association information and primary and foreign key association information between any two database tables.

[0015] On the other hand, this application provides an apparatus for generating a domain model, comprising:

[0016] A processor, and a memory communicatively connected to the processor;

[0017] The memory stores computer-executed instructions;

[0018] The processor executes computer execution instructions stored in the memory to implement the method for generating a domain model as described above.

[0019] On the other hand, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method for generating a domain model as described above.

[0020] On the other hand, this application provides a computer program product including computer execution instructions that, when executed by a processor, implement the method for generating a domain model as described above.

[0021] The method, apparatus, device, storage medium, and program product for generating domain models provided in this application can obtain the structured data files and table creation statement files corresponding to the database tables of the system to be developed; perform association analysis processing on the structured data files of any two database tables based on the structured data files corresponding to the database tables to determine the data association information between the two database tables, and determine the primary and foreign key association information between any two database tables based on the table creation statement files of the database tables; extract the table name and table field information of the database tables from the table creation statement files of the database tables, and generate the domain model corresponding to the database tables based on the table name and table field information; determine the association information between the domain models corresponding to any two database tables based on the data association information and primary and foreign key association information between any two database tables, thereby generating a domain model from the database tables and determining the association information between the domain models corresponding to any two database tables. Attached Figure Description

[0022] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0023] Figure 1 A schematic diagram of the domain model and the relationship information between domain models provided in this application;

[0024] Figure 2 A flowchart of the method for generating a domain model provided in Embodiment 1 of this application;

[0025] Figure 3 This is a flowchart of a method for generating a domain model provided in Embodiment 2 of this application;

[0026] Figure 4 A flowchart illustrating an example of association analysis processing provided in Embodiment 2 of this application;

[0027] Figure 5 This is a flowchart illustrating the generation of the domain model corresponding to the database table provided in Embodiment 2 of this application;

[0028] Figure 6 A schematic diagram of the apparatus for generating a domain model provided in Embodiment 3 of this application;

[0029] Figure 7 A schematic diagram of the apparatus for generating a domain model provided in Embodiment 4 of this application;

[0030] Figure 8 This is a schematic diagram of the device for generating a domain model provided in Embodiment 5 of this application.

[0031] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0032] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0033] First, let me explain the terms used in this application:

[0034] PK: primary key, a database primary key, is an attribute that can uniquely identify a piece of data in a table. A table can only have one primary key, and it cannot be null.

[0035] FK: Foreign key, a database foreign key, is a foreign key in one table that is also the primary key in another table. It is used to establish the relationship and data constraints between the two tables.

[0036] ER diagram: Entity-Relationship diagram, provides a method for representing database entity types, attributes, and relationships.

[0037] Domain model, also known as business object model, is a visual representation of the object model describing business implementation. In low-code development platforms, the domain model is the foundation for feature development. The domain model visualization is similar to an ER diagram, with each domain model corresponding to a database table, and data items in the domain model corresponding to fields in the database table. Unlike an ER diagram, the attributes of the domain model and the attributes of the data items can be flexibly configured. Maintaining the various attributes of the domain model is crucial, as forms and processes are developed visually based on it.

[0038] Furthermore, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. In the following descriptions of embodiments, "a plurality of" means two or more, unless otherwise explicitly defined.

[0039] Low-code development platforms are primarily aimed at "non-programmers" in the business domain (non-professional developers, such as business product and operations personnel, who lack actual coding experience). Essentially, low-code development reduces the difficulty and improves efficiency for users by using various model capabilities (such as metadata models, business object models, online script engines, workflow models, business flow models, and platform programming models).

[0040] A domain model, also known as a business object model, is a visual representation of an object model that describes the implementation of a business. In low-code development platforms, the domain model is the foundation for system application development. Figure 1 An example of a domain model and the relationships between domain models is provided, using the example of a domain model having an attribute that includes encoding, and a data item having an attribute that includes encoding, to illustrate the domain model. Figure 1 It contains three domain models: Domain Model a, Domain Model b, and Domain Model c. The codes for Domain Model a, Domain Model b, and Domain Model c are a, b, and c, respectively. Domain Model a and Domain Model b are related, and Domain Model b and Domain Model c are also related. Domain Model a contains data items a1, a2, and a3, with codes a1, a2, and a3, respectively. Domain Model b contains data items b1, b2, and b3, with codes b1, b2, and b3, respectively. Domain Model c contains data items c1, c2, and c3, with codes c1, c2, and c3, respectively.

[0041] To involve more application stakeholders beyond traditional developers in the application building process, low-code development platforms are needed. Rebuilding or updating existing system applications using low-code development platforms requires reverse engineering the domain model based on existing database tables.

[0042] Currently, some database modeling and management tools (such as Navicat and PowerDesigner) can reverse-engineer business object entity classes based on the database table structure. However, the implementation methods are basically for single tables, directly generating a single business object entity class (such as a Java class). Although this quickly builds business object entity classes, it only applies to the CRUD operations of a single table and does not build the domain model relationships based on the relationships between tables, making it unsuitable for low-code development platforms.

[0043] The method for generating domain models provided in this application can obtain the structured data files and table creation statement files corresponding to the database tables of the system to be developed; perform association analysis on the structured data files of any two database tables based on the structured data files corresponding to the database tables to determine the data association information between the two database tables, and determine the primary and foreign key association information between any two database tables based on the table creation statement files; extract the table name and table field information of the database tables from the table creation statement files, and generate the domain model corresponding to the database tables based on the table name and table field information; determine the association information between the domain models corresponding to any two database tables based on the data association information and primary and foreign key association information between any two database tables, thereby reverse-engineering the domain model based on the existing database tables and determining the association information between the domain models corresponding to any two database tables.

[0044] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0045] Example 1

[0046] Figure 2 This is a flowchart of a method for generating a domain model according to Embodiment 1 of this application. This embodiment addresses the problem of needing to generate a domain model from an existing database table and provides a method for generating a domain model. The method in this embodiment is applied to a device for generating the domain model, which can be a mobile terminal or an electronic device such as a server. In other embodiments, the method can also be applied to other devices. This embodiment uses a device for generating the domain model as an example for illustrative explanation.

[0047] like Figure 2 As shown, the specific steps of this method are as follows:

[0048] Step S101: Obtain the structured data file and table creation statement file corresponding to the database table of the system to be developed.

[0049] The structured data file includes the field information and data contained in the database tables of the system to be developed.

[0050] The table creation statement file contains the table creation statements used to generate the data tables. Table creation statements typically include: the table name, table field information, and primary and foreign key information. The table field information includes information about all fields in the database table.

[0051] Optionally, the structured data files corresponding to the database tables of the system to be developed can be obtained by using a database connection tool to export the database tables of the system to be developed into corresponding structured data files.

[0052] Optionally, the format of the exported structured data file should facilitate the retrieval of the data corresponding to the fields in the structured data file. For example, the exported structured data file can be in JSON format, where fields and data are represented as key-value pairs, facilitating the analysis and processing of the structured data set of the database table corresponding to the structured data file. Alternatively, the exported structured data file can also be in XML format, etc.

[0053] Step S102: Perform association analysis on the structured data files corresponding to the database tables that need to be processed for association analysis. For any two database tables, perform association analysis to determine the data association information between the two database tables. Based on the table creation statement files of the database tables, determine the primary and foreign key association information between any two database tables.

[0054] In this application, the relationship information between two database tables may include: data relationship information between the two database tables and primary and foreign key relationship information between the two database tables.

[0055] In this step, by performing correlation analysis on the structured data files of any two database tables, based on the structure of the two database tables and the data in the tables, the possible correlation relationships between the fields in the two database tables are analyzed, and the data correlation information between the two database tables is obtained.

[0056] In this step, the primary and foreign key relationship information between any two database tables can also be determined based on the table creation statement file of the database tables.

[0057] Step S103: Extract the table name and table field information of the database table from the table creation statement file, and generate the domain model corresponding to the database table based on the table name and table field information.

[0058] In this embodiment, step S103 can be performed in parallel with step S102, or step S103 can be performed before step S102. This embodiment does not make a specific limitation on the order of steps S102 and S103.

[0059] In this embodiment, each domain model corresponds to a database table, and a domain model can be established for each database table. Data items in the domain model correspond to fields in the database table, and the association information between domain models corresponds to the relationship information between database tables.

[0060] In this step, the table name and field information of the database table can be extracted from the table creation statement file. Based on the table name and field information extracted from the table creation statement file, the attribute information of the domain model corresponding to the database table and the attribute information of the data items included in the domain model are determined, thereby generating the domain model corresponding to the database table.

[0061] The attributes of a domain model include: the domain model's ID. A domain model may include one or more data items, and the attributes of each data item include: the data item's ID and / or name.

[0062] Optionally, the database tables can be filtered to determine which database tables need to generate domain models. In this step, the corresponding domain models can be generated only for the database tables that need to generate domain models.

[0063] Step S104: Based on the data association information and primary and foreign key association information between any two database tables, determine the association information between the domain models corresponding to any two database tables.

[0064] The association information between domain models includes: data association information and primary and foreign key association information between domain models.

[0065] In this step, by using the association information between database table fields as the association information between the corresponding data items, the association information between database tables can be transformed into the association information between the domain models corresponding to the data tables. Thus, based on the data association information and primary and foreign key association information between any two database tables, the association information between the corresponding domain models of any two database tables can be determined.

[0066] In this embodiment, the system can obtain the structured data files and table creation statement files corresponding to the database tables of the system to be developed; based on the structured data files corresponding to the database tables, it performs association analysis on the structured data files of any two database tables to determine the data association information between the two database tables, and determines the primary and foreign key association information between any two database tables based on the table creation statement files; it extracts the table name and table field information of the database tables from the table creation statement files, and generates the domain model corresponding to the database tables based on the table name and table field information; based on the data association information and primary and foreign key association information between any two database tables, it determines the association information between the domain models corresponding to any two database tables, thereby generating a domain model from the existing database tables and determining the association information between the domain models corresponding to any two database tables.

[0067] Example 2

[0068] Figure 3A flowchart of a method for generating a domain model is provided for Embodiment 2 of this application. Based on Embodiment 1 above, in this embodiment, the structured data file corresponding to any database table is used as a base file, and the base file is sequentially subjected to the following association analysis processing with another structured data file:

[0069] Determine the support between the first data column corresponding to the first field in the baseline file and the second data column corresponding to the second field in another structured data file; if the support between the first data column and the second data stream is greater than or equal to the support threshold, then it is determined that there is a data association between the first field and the second field; if the support between the first data column and the second data stream is less than the support threshold, then it is determined that there is no data association between the first field and the second field.

[0070] like Figure 3 As shown, the specific steps of this method are as follows:

[0071] Step S201: Obtain the structured data file and table creation statement file corresponding to the database table of the system to be developed.

[0072] The structured data file includes the field information and data contained in the database tables of the system to be developed.

[0073] The table creation statement file contains the table creation statements used to generate the data tables. Table creation statements typically include: the table name, table field information, and primary and foreign key information. The table field information contains details about all fields in the database table.

[0074] Optionally, the structured data files corresponding to the database tables of the system to be developed can be obtained by using a database connection tool to export the database tables of the system to be developed into corresponding structured data files.

[0075] For example, using a database connection tool, you can export a set of JSON files containing the table structure and data; a database table can be exported as a single JSON file.

[0076] Optionally, the data in the exported structured data file is structured, making it easier to retrieve the data corresponding to the fields in the structured data file.

[0077] For example, the exported structured data file can be in JSON format. In JSON format, fields and data are represented as key-value pairs, making it easy to extract fields and their corresponding data. Alternatively, the exported structured data file can also be in XML format, etc.

[0078] Step S202: Based on the filtering configuration information, determine the database tables and / or fields that need to be processed for correlation analysis.

[0079] The filtering configuration information is used to filter all database tables and / or fields of the business system to determine the database tables and / or fields that need to be subjected to correlation analysis.

[0080] In this embodiment, by using filtering configuration information, database tables and / or fields that require association analysis can be configured. During association analysis, the filtering configuration information can filter out database tables and fields that do not require association analysis, allowing association analysis to be performed only on the necessary database tables and fields. This reduces the workload of association analysis and improves its efficiency.

[0081] In one optional implementation, the filtering configuration information may include: database tables and / or fields that do not require association analysis. Based on the configured filtering configuration information, the database tables and / or fields that do not require association analysis can be determined.

[0082] When performing association analysis, the database tables and / or fields that do not need to be analyzed are filtered out according to the set filtering configuration information. In subsequent steps, only the database tables and fields that need to be analyzed are analyzed. This avoids analyzing unnecessary database tables and fields, thereby reducing the workload of association analysis and improving the efficiency of association analysis.

[0083] For example, when performing association analysis, the database tables not included in the filter configuration information can be identified based on the filter configuration information, that is, the database tables that need to be analyzed. Then, the structured data files of any two database tables not included in the filter configuration information are analyzed to determine the data association information between the two database tables.

[0084] In another optional implementation, the filtering configuration information may include: database tables and / or fields that require association analysis processing. Based on the filtering configuration information, the device generating the domain model can determine the database tables included in the filtering configuration information, thus obtaining the database tables that require association analysis processing.

[0085] When performing association analysis, based on the configured filtering information, only the database tables and fields that need to be analyzed need to be analyzed. This avoids analyzing unnecessary database tables and fields, thereby reducing the workload of association analysis and improving its efficiency.

[0086] Optionally, the device that generates the domain model can provide a visual interface for configuring filter configuration information, through which the filter configuration information can be configured according to its own needs.

[0087] Step S203: Determine the primary and foreign key relationship information between any two database tables from the table creation statement file of the database tables to be processed for association analysis.

[0088] In this application, the relationship information between two database tables may include: data relationship information between the two database tables, and primary and foreign key relationship information between the two database tables.

[0089] The data relationship information between two database tables is determined by performing a relationship analysis on the data in the two database tables.

[0090] In this step, the primary and foreign key relationships between any two database tables can be determined based on the table creation statements. For any two database tables: the first database table and the second database table, if the primary key of the first database table is a foreign key of the second database table, then a primary and foreign key relationship exists between the first and second database tables.

[0091] For example, the primary key information and / or foreign key information of a database table can be extracted from the table creation statement file of a database table. Based on the primary key information and / or foreign key information of the database table, the foreign key field of the database table and another database table with the foreign key field as the primary key can be determined, and the primary and foreign key relationship between the database table and the other database table can be established.

[0092] In this embodiment, step S203 can be performed in parallel with step S204, or step S204 can be performed before step S303. This embodiment does not make a specific limitation on the order of steps S203 and S204.

[0093] Step S204: Perform association analysis on the structured data files corresponding to the database tables that need to be processed for association analysis. For any two database tables, perform association analysis to determine the data association information between the two database tables.

[0094] The data association information between the two database tables includes the data association information between fields in the two different database tables.

[0095] In practical applications, when tables are not created in a standardized manner, foreign key constraints are easily overlooked, resulting in missing foreign key information in the table creation statement file. This makes it impossible to determine the primary and foreign key relationships between database tables based on the table creation statement file.

[0096] In this embodiment, by performing association analysis on the structured data files of any two database tables, the structure of the two database tables and the relationships between the data in the tables can be analyzed. This allows for the discovery of potential relationships between data columns in various fields of the two database tables. Even if the table creation statements lack information such as foreign key constraints, the data relationship information between the two database tables can be determined through data analysis. The data relationship information obtained through association analysis can supplement the primary and foreign key relationship information between the data tables determined in step S203, making the relationship information between the database tables more comprehensive and complete.

[0097] Optionally, the structured data file includes field information and data contained in the database tables. This step can be implemented in the following ways:

[0098] Each structured data file corresponding to a database table is used as a baseline file. The baseline files are then sequentially correlated with another structured data file to determine the data association information between the two database tables.

[0099] Optionally, the baseline file can be sequentially correlated with another structured data file to determine the data relationship information between the two database tables. This can be achieved in the following way:

[0100] Determine the support between the first data column corresponding to the first field in the baseline file and the second data column corresponding to the second field in another structured data file; if the support between the first data column and the second data column is greater than or equal to the support threshold, then it is determined that there is a data association between the first field and the second field; if the support between the first data column and the second data column is less than the support threshold, then it is determined that there is no data association between the first field and the second field.

[0101] Wherein, the first field refers to any field in the benchmark file; the second field refers to any field in another structured data file that is correlated with the benchmark file; the first data column corresponding to the first field contains all the data corresponding to the first field in the benchmark file; the second data column corresponding to the second field contains all the data corresponding to the second field in another structured data file.

[0102] For example, taking a structured data file as a JSON file of a database table exported using a database connection tool, in the structured data file, the data in the database table is arranged into data columns by field, and the data corresponding to each field is arranged into a column to form the data column corresponding to the field. Each row of data in the database table is still a row of data in the structured data file.

[0103] The support threshold can be set and adjusted according to the needs of the actual application scenario; no specific limit is set here.

[0104] Furthermore, the support between the first and second data columns can be determined as follows:

[0105] Based on the first data column and the second data column, determine the number of rows of a specified row in the second data column, where the specified row is identical to any row in the first data column; the ratio of the number of rows of the specified row in the second data column to the total number of rows in the second data column is used as the support between the first data column and the second data column.

[0106] Specifically, for a row in the second data column, if that row is identical to any row in the first data column, then that row in the second data column is considered the specified row. The number of specified rows refers to the number of specified rows in the second data column.

[0107] For example, if the first row of data in the second data column is data 1, and one or more rows of data in the first data column are also data 1, then the first row of data in the second data column is the specified row of data.

[0108] In one optional implementation of this step, when performing association analysis on the benchmark file and another structured data file in sequence to determine the data association information between the two database tables, the primary key data column in the benchmark file can be associated with all the data columns in the other structured data file to determine whether there is a data association between the primary key data column in the benchmark file and all the data columns in the other structured data file.

[0109] Specifically, the support between the primary key data column corresponding to the primary key of the benchmark file and the second data column corresponding to any field in another structured data file is determined. If the support between the primary key data column and the second data column is greater than or equal to the support threshold, it is determined that there is a data association between the primary key and the second field of the benchmark file. If the support between the primary key data column and the second data column is less than the support threshold, it is determined that there is no data association between the primary key and the second field of the benchmark file.

[0110] For example, Figure 4 This document provides a flowchart illustrating an example of performing association analysis on a structured data file of a database table in a system under development. The example uses a JSON file as the structured data file for the database table. Figure 4 As shown, the process of performing correlation analysis on all JSON files of the database tables in the system under development can include the following steps:

[0111] Step S1: Select a JSON file to be analyzed and set it as the baseline file.

[0112] Optionally, the selected benchmark file can be set to the analyzed JSON file.

[0113] Step S2: Check if there are any JSON files that have not been correlated with the baseline file.

[0114] In this step, if a JSON file that has not been correlated with the baseline file is found, then step S3 is executed; if no JSON file that has not been correlated with the baseline file is found, then the correlation analysis of the baseline file ends, and step S3 is executed to analyze the next JSON file to be analyzed.

[0115] In this step, it is determined whether there is a JSON file to be analyzed in pairs with the benchmark file. If not, the analysis of that benchmark file ends, and the analysis of the next benchmark file begins, until all files have been analyzed in pairs, at which point the process ends. If there is a JSON file to be analyzed in pairs with the benchmark file, a JSON file is read as the comparison file, and the analysis in pairs with the benchmark file begins.

[0116] Step S3: Check if there is a JSON file to be analyzed.

[0117] If the JSON file to be analyzed is found, proceed to step S1; if the JSON file to be analyzed is not found, then all JSON files that need to be correlated have been correlated and the process ends.

[0118] Step S4: Read a JSON file that is to be correlated with the benchmark file, and use it as the comparison file.

[0119] Specifically, a JSON file to be correlated with a benchmark file is selected, and the selected JSON file to be correlated with the benchmark file is set as the comparison file. Subsequent steps are then performed to correlate the comparison file with the benchmark file.

[0120] Step S5: Analyze a data column in the benchmark file by column to determine the support between all data columns in the comparison file and the data columns in the benchmark file.

[0121] In this step, a data column L from the benchmark file is first read, and the support between column L and any data column X from the comparison file is calculated. The support between column L and any data column X from the comparison file is calculated as follows: Support between column L and column X = Number of rows in column X where any row of data in column L appears / Total number of rows in column X.

[0122] Step S6: Determine whether the support is greater than or equal to the support threshold.

[0123] In this step, based on the set support threshold, it is determined whether there is a data relationship between column L and column X, depending on whether the support of column L and column X is greater than or equal to the support threshold.

[0124] If the support is less than the support threshold, it is determined that there is no data relationship between the corresponding fields of the two data columns. Step S8 is executed to continue comparing data column L with the next column until all files have been compared.

[0125] If the support is greater than or equal to the support threshold, it is determined that there is a data relationship between the corresponding fields of the two data columns, and step S7 is executed.

[0126] Step S7: Record the data association information between corresponding fields in the data column.

[0127] Step S8: Determine whether all data columns in the benchmark file have been analyzed.

[0128] If all data columns in the baseline file have been analyzed, the data relationship information between the two database tables has been obtained, and step S9 is executed.

[0129] If there are still unanalyzed data columns in the baseline file, proceed to step S5 to continue analyzing the next data column in the baseline file.

[0130] Step S9: Record the JSON file containing the completed association analysis with the baseline file.

[0131] In this step, a JSON file containing the completed association analysis with the baseline file is recorded to avoid duplicate analysis, and S2 is executed.

[0132] Step S205: Extract the table name and table field information of the database table from the table creation statement file, and generate the domain model corresponding to the database table based on the table name and table field information.

[0133] In this embodiment, step S205 can be performed in parallel with steps S202-S204, or step S205 can be performed before steps S202-S204.

[0134] In this embodiment, each domain model corresponds to a database table, and a domain model can be established for each database table. Data items in the domain model correspond to fields in the database table, and the association information between domain models corresponds to the relationship information between database tables.

[0135] In this step, the table name and field information of each database table can be extracted from the table creation statement file. Based on the table name and field information of each database table, the attribute information of the domain model corresponding to the database table and the attribute information of the data items included in the domain model are determined, thereby generating the domain model corresponding to the database table.

[0136] The attributes of a domain model include: the domain model's ID. A domain model may include one or more data items, and the attributes of each data item include: the data item's ID and / or name.

[0137] Optionally, after extracting the table name and field information of each database table, the table name is determined as the code of the corresponding domain model; based on the information of each field of the database table, the code and name of the data item contained in the domain model are determined, and each field of the database table corresponds to a data item in the domain model; based on the code of the domain model and the code and name of the data item contained in the domain model, the domain model is generated.

[0138] Optionally, if the table name in the database does not conform to camelCase naming convention, the table name in the database is converted to camelCase naming convention to obtain the corresponding domain model encoding.

[0139] For example, Figure 5 An example flowchart for generating a domain model corresponding to a database table is provided, such as... Figure 5 As shown, first, the table creation statement file of the database table is obtained. Then, the encoding of the corresponding domain model is determined according to the table name in the table creation statement file, and the domain model transformation is completed. Finally, according to the information of each field of the database table in the table creation statement file, the encoding and name of the data items contained in the domain model are determined, and the transformation of the domain model data items is completed.

[0140] Furthermore, the encoding and name of the data items contained in the domain model can be determined through at least the following two feasible implementation methods.

[0141] An alternative implementation is as follows: when determining the encoding and name of the data items contained in the domain model based on the information of each field in the database table, the name of the field can be used as both the encoding and name of the data item.

[0142] Optionally, if the field name does not conform to camelCase naming convention, the field name will be converted to camelCase naming convention to obtain the corresponding data item's code and name.

[0143] Another optional implementation is that table field information can include field names and Chinese comments. Based on the information in each field of the database table, the encoding and name of the data items contained in the domain model can be determined in the following way:

[0144] The name of each field in the database table is used as the code for the corresponding data item; the Chinese comment or name of each field in the database table is used as the name for the corresponding data item.

[0145] For example, if the information of a field includes Chinese comments, then the Chinese comments of the field are used as the name of the data item corresponding to the field; if the information of a field does not include Chinese comments, then the name of the field is used as the name of the data item corresponding to the field.

[0146] Optionally, if the field name does not conform to camelCase naming convention, the field name will be converted to camelCase naming convention to obtain the corresponding data item code.

[0147] For example, a domain model is generated for each database table. The table name is converted into the domain model code using camelCase, the field name is converted into the code of the corresponding data item using camelCase, and the Chinese comments of the field are used as the name of the corresponding data item. If the Chinese comments of a field are empty, the field name is used as the name of the data item.

[0148] Step S206: Based on the data association information and primary and foreign key association information between any two database tables, determine the association information between the domain models corresponding to any two database tables.

[0149] The association information between domain models includes: data association information and primary and foreign key association information between domain models.

[0150] In this step, the association information between any two database tables is transformed into the association information between the corresponding domain models of the two database tables.

[0151] Optionally, for any two database tables, the data association information and primary and foreign key association information between the database tables include the data association and primary and foreign key association information between the fields of the two database tables. By transforming the association information between the fields of the database tables into the association information between the data items corresponding to the fields, the association information between the database tables can be transformed into the association information between the domain models corresponding to the data tables.

[0152] Specifically, based on the data relationship information between any two database tables, if it is determined that there is a data relationship between the third field in the first database table and the fourth field in the second database table, then it is determined that there is a data relationship between the first data item in the first domain model and the second data item in the second domain model; based on the primary and foreign key relationship information between any two database tables, if it is determined that there is a primary and foreign key relationship between the third field in the first database table and the fourth field in the second database table, then it is determined that there is a primary and foreign key relationship between the first data item in the first domain model and the second data item in the second domain model.

[0153] In this context, the first database table refers to any database table, the third field refers to any field in the first database table, the first domain model is the domain model corresponding to the first database table, the first data item corresponds to the third field, the second domain model is the domain model corresponding to the second database table, and the second data item corresponds to the fourth field.

[0154] Step S207: Output the domain model corresponding to the database table and the relationship information between the domain models.

[0155] After generating the domain model and determining the relationships between the domain models, this step outputs the relationship information between the domain models to demonstrate the relationships between them to relevant personnel.

[0156] In addition, it can also support relevant personnel to confirm and adjust the domain model and the relationship information between domain models.

[0157] Optionally, the domain model and the relationships between domain models can be visualized. For example, the domain model and its relationships can be displayed on a front-end page; alternatively, a report containing visualizations can be generated based on the domain model and its relationships, and the report can be pushed out in a specified manner. Here, the visualizations refer to the domain model diagrams generated based on the domain model and its relationships, and the specified report push method can be set and adjusted according to the needs of the actual application scenario.

[0158] Optionally, in the output association information between domain models, dashed lines can be used to represent data associations, and solid lines can be used to represent primary and foreign key associations.

[0159] The primary and foreign key relationships between domain models are determined based on the table creation statements in the database. They accurately reflect the primary and foreign key relationships between domain models and are valid association information. Data association information between domain models is determined through association analysis of data in the database tables, representing potential associations. Some of these associations may be invalid, and their validity can be manually verified.

[0160] Optionally, the device that generates the domain model can provide the ability to edit dashed connections, such as the ability to replace dashed connections with solid connections or to delete dashed connections.

[0161] For example, in response to the confirmation operation of the dashed connection, the dashed connection is replaced with a solid connection; in response to the deletion operation of the dashed connection, the dashed connection is deleted and the data association information corresponding to the dashed connection is deleted.

[0162] Optionally, the device for generating the domain model may also provide the function of editing the domain model, which can edit at least one of the domain model's encoding, the encoding of data items, and the name of data items. For example, in response to an operation on the domain model, the domain model's encoding, the encoding of data items, and the name of data items are updated; in response to a save operation on the domain model, the domain model's encoding, the encoding of data items, and the name of data items are updated to the modified content.

[0163] For example, the device that generates the domain model can provide a domain model display interface. This interface displays the domain model's encoding, data item encoding, and data item names, and shows dashed and solid lines connecting the domain models. Users can confirm or delete dashed lines on the domain model display interface, edit at least one of the domain model's encoding, data item encoding, or data item names, and save the edited content.

[0164] In this embodiment, by using the structured data file corresponding to any database table as a reference file, the reference file is sequentially compared with another structured data file using the following association analysis: determining the support of the first data column corresponding to the first field in the reference file and the second data column corresponding to the second field in the other structured data file; if the support of the first data column and the second data column is greater than or equal to the support threshold, it is determined that there is a data association between the first field and the second field; if the support of the first data column and the second data column is less than the support threshold, it is determined that there is no data association between the first field and the second field. This allows for association analysis of structured data files of any two database tables. Even if the database tables are not built in a standardized manner and lack primary and foreign key information, the association information between the corresponding domain models of the database tables can be determined by performing association analysis on the data columns of each field in the database tables and the data association between the fields in the database tables.

[0165] Example 3

[0166] Figure 6This is a schematic diagram of the apparatus for generating a domain model according to Embodiment 3 of this application. The apparatus for generating a domain model provided in this embodiment can execute the processing flow provided in the method embodiment for generating a domain model. Figure 6 As shown, the device 30 for generating a domain model includes: a file acquisition module 301, a table association information determination module 302, a domain model determination module 303, and a domain model association information determination module 304.

[0167] Specifically, the file acquisition module 301 is used to acquire the structured data file and table creation statement file corresponding to the database table of the system to be developed.

[0168] The inter-table association information determination module 302 is used to perform association analysis processing on the structured data files of any two database tables based on the structured data files corresponding to the database tables, determine the data association information between the two database tables, and determine the primary and foreign key association information between any two database tables based on the table creation statement files of the database tables.

[0169] The domain model determination module 303 is used to extract the table name and table field information of the database table from the table creation statement file of the database table, and generate the domain model corresponding to the database table based on the table name and table field information.

[0170] The domain model association information determination module 304 is used to determine the association information between the domain models corresponding to any two database tables based on the data association information and primary and foreign key association information between any two database tables.

[0171] The apparatus provided in this application embodiment can be specifically used to execute the method embodiment provided in Embodiment 1 above, and the specific functions will not be repeated here.

[0172] In this embodiment, the system can obtain the structured data files and table creation statement files corresponding to the database tables of the system to be developed; based on the structured data files corresponding to the database tables, it performs association analysis on the structured data files of any two database tables to determine the data association information between the two database tables, and determines the primary and foreign key association information between any two database tables based on the table creation statement files; it extracts the table name and table field information of each database table from the table creation statement files, and generates the domain model corresponding to the database table based on the table name and table field information; based on the data association information and primary and foreign key association information between any two database tables, it determines the association information between the domain models corresponding to any two database tables, thereby generating a domain model from the existing database tables and determining the association information between the domain models corresponding to any two database tables.

[0173] Example 4

[0174] Figure 7 This is a schematic diagram of the apparatus for generating a domain model provided in Embodiment 4 of this application. Based on Embodiment 4 above, in this embodiment, optionally, the structured data file includes field information and data contained in a database table, and the inter-table relationship information determination module 302 is further used for:

[0175] Each structured data file corresponding to any database table is used as a baseline file. The baseline file is then subjected to the following association analysis with another structured data file: the support of the first data column corresponding to the first field in the baseline file and the second data column corresponding to the second field in the other structured data file are determined; if the support of the first data column and the second data column is greater than or equal to the support threshold, then it is determined that there is a data association between the first field and the second field; if the support of the first data column and the second data column is less than the support threshold, then it is determined that there is no data association between the first field and the second field.

[0176] Optionally, the inter-table relationship information determination module 302 is also used for:

[0177] Based on the first data column and the second data column, determine the number of rows of a specified row in the second data column, where the specified row is identical to any row in the first data column; the ratio of the number of rows of the specified row in the second data column to the total number of rows in the second data column is used as the support between the first data column and the second data column.

[0178] Optionally, the inter-table relationship information determination module 302 is also used for:

[0179] Obtain the filtering configuration information, which includes database tables and / or fields that do not require correlation analysis. Based on the filtering configuration information, perform correlation analysis on the structured data files of any two database tables not included in the filtering configuration information to determine the data correlation information between the two database tables.

[0180] Optionally, the domain model determination module 303 is also used for:

[0181] The table name in the database is determined as the code of the corresponding domain model; based on the information of each field in the database table, the code and name of the data item contained in the domain model are determined, and each field in the database table corresponds to a data item in the domain model; based on the code of the domain model and the code and name of the data item contained in the domain model, the domain model is generated.

[0182] Optionally, the domain model determination module 303 is also used for:

[0183] The name of each field in the database table is used as the code for the corresponding data item; the Chinese comment or name of each field in the database table is used as the name for the corresponding data item.

[0184] Optionally, such as Figure 7 As shown, the domain model association information determination module 304 also includes:

[0185] The data item association information determination unit 3041 is used to determine, based on the data association information between any two database tables, that if it is determined that there is a data association between the third field in the first database table and the fourth field in the second database table, then it is determined that there is a data association between the first data item in the first domain model and the second data item in the second domain model.

[0186] The data item primary and foreign key association information determination unit 3042 is used to determine, based on the primary and foreign key association information between any two database tables, if it is determined that there is a primary and foreign key association between the third field in the first database table and the fourth field in the second database table, then it is determined that there is a primary and foreign key association between the first data item in the first domain model and the second data item in the second domain model.

[0187] The first domain model is the domain model corresponding to the first database table, and the first data item corresponds to the third field. The second domain model is the domain model corresponding to the second database table, and the second data item corresponds to the fourth field.

[0188] Optionally, such as Figure 7 As shown, the apparatus 30 for generating the domain model further includes:

[0189] Domain model output module 305 is used to output the domain model corresponding to the database table and the relationship information between the domain models.

[0190] Optionally, the domain model output module 305 is also used for:

[0191] In the output domain model association information, dashed lines represent data associations, and solid lines represent primary and foreign key associations. In response to the confirmation operation of a dashed line connection, the dashed line connection is replaced with a solid line connection. In response to the deletion operation of a dashed line connection, the dashed line connection is deleted, and the data association information corresponding to the dashed line connection is also deleted.

[0192] Optionally, the file acquisition module 301 is also used for:

[0193] Use a database connection tool to export the database tables of the system to be developed into corresponding structured data files.

[0194] The apparatus provided in this application embodiment can be specifically used to execute the method embodiment provided in Embodiment 2 above, and the specific functions will not be repeated here.

[0195] In this embodiment, by using the structured data file corresponding to any database table as a reference file, the reference file is sequentially compared with another structured data file using the following association analysis: determining the support of the first data column corresponding to the first field in the reference file and the second data column corresponding to the second field in the other structured data file; if the support of the first data column and the second data column is greater than or equal to the support threshold, it is determined that there is a data association between the first field and the second field; if the support of the first data column and the second data column is less than the support threshold, it is determined that there is no data association between the first field and the second field. This allows for association analysis of structured data files of any two database tables. Even if the database tables are not built in a standardized manner and lack primary and foreign key information, the association information between the corresponding domain models of the database tables can be determined by performing association analysis on the data columns of each field in the database tables and the data association between the fields in the database tables.

[0196] Example 5

[0197] Figure 8 This is a schematic diagram of the device for generating a domain model provided in Embodiment 5 of this application. Figure 8 As shown, the device 40 for generating the domain model includes: a processor 401, a memory 402, and computer-executable instructions stored in the memory 402 and executable on the processor 401.

[0198] The processor 401 implements the method for generating a domain model provided in any of the above method embodiments when executing computer execution instructions.

[0199] In this embodiment, the system can obtain the structured data files and table creation statement files corresponding to the database tables of the system to be developed; based on the structured data files corresponding to the database tables, it performs association analysis on the structured data files of any two database tables to determine the data association information between the two database tables, and determines the primary and foreign key association information between any two database tables based on the table creation statement files; it extracts the table name and table field information of the database tables from the table creation statement files, and generates the domain model corresponding to the database tables based on the table name and table field information; based on the data association information and primary and foreign key association information between any two database tables, it determines the association information between the domain models corresponding to any two database tables, thereby generating a domain model from the existing database tables and determining the association information between the domain models corresponding to any two database tables.

[0200] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the method provided in any of the above-described method embodiments.

[0201] This application also provides a computer program product, which includes: computer execution instructions stored in a readable storage medium. At least one processor of the device generating the domain model can read the computer execution instructions from the readable storage medium, and the at least one processor executes the computer execution instructions to cause the device generating the domain model to perform the method provided in any of the above method embodiments.

[0202] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the determination of a unit is only for one logical function, and in actual implementation, there may be other determination methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0203] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0204] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.

[0205] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0206] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described functional modules are used as examples. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be determined as different functional modules to complete all or part of the functions described above. The specific working process of the device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0207] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0208] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method of generating a domain model, characterized by, The application relates to a method for generating a domain model of a database table. The method comprises the following steps: obtaining a structured data file and a table creation statement file corresponding to a database table of a system to be developed; the structured data file comprises field information and data contained in the database table, performing correlation analysis processing on the structured data files of any two database tables according to the structured data file corresponding to the database table, determining data correlation information between the two database tables, and determining primary-foreign key correlation information between any two database tables according to the table creation statement file of the database table; extracting the table name and table field information of the database table from the table creation statement file of the database table, and generating a domain model corresponding to the database table according to the table name and table field information of the database table; determining the correlation information between the domain models corresponding to any two database tables according to the data correlation information and the primary-foreign key correlation information between the two database tables; the correlation analysis processing on the structured data files of any two database tables according to the structured data file corresponding to the database table comprises the following steps: respectively taking the structured data file corresponding to any database table as a reference file, and sequentially performing the following correlation analysis processing on the reference file and another structured data file: determining the number of specified row data in a second data column corresponding to a second field in the another structured data file according to a first data column corresponding to a first field in the reference file, the specified row data being the same as any row data in the first data column; wherein the first data column contains all data corresponding to the first field in the reference file, and the second data column contains all data corresponding to the second field in the another structured data file; taking the ratio of the number of the specified row data in the second data column to the total number of rows in the second data column as the support degree of the first data column and the second data column; if the support degree of the first data column and the second data column is greater than or equal to a support degree threshold, it is determined that the first field and the second field have data correlation; 2. The method of claim 1, wherein, if the support degree of the first data column and the second data column is less than the support degree threshold, it is determined that the first field and the second field do not have data correlation. the correlation analysis processing on the structured data files of any two database tables according to the structured data file corresponding to the database table further comprises the following steps: obtaining filtering configuration information, wherein the filtering configuration information comprises database tables and / or fields that do not need to be subjected to the correlation analysis processing; 3. The method of claim 1, wherein, performing correlation analysis processing on the structured data files of any two database tables not contained in the filtering configuration information according to the filtering configuration information, and determining the data correlation information between the two database tables. the generation of the domain model corresponding to the database table according to the table name and the table field information of the database table comprises the following steps: determining the table name of the database table as the code of the corresponding domain model. determining the encoding and name of the data item included in the domain model according to the information of each field of the database table, each field of the database table corresponding to one data item of the domain model; generating a domain model according to the encoding of the domain model, the encoding and name of the data item included in the domain model.

4. The method of claim 3, wherein, The determining the encoding and name of the data item included in the domain model according to the information of each field of the database table comprises: determining the name of each field of the database table as the encoding of the data item corresponding to the field; determining the Chinese annotation or name of each field of the database table as the name of the data item corresponding to the field.

5. The method according to claim 3 or 4, characterized in that, The determining the association information between the domain models corresponding to any two database tables according to the data association information and the primary-foreign key association information between the any two database tables comprises: determining that there is data association between a first data item in a first domain model and a second data item in a second domain model according to the data association information between any two database tables if it is determined that there is data association between a third field in a first database table and a fourth field in a second database table; determining that there is primary-foreign key association between the first data item in the first domain model and the second data item in the second domain model according to the primary-foreign key association information between any two database tables if it is determined that there is primary-foreign key association between the third field in the first database table and the fourth field in the second database table; wherein the first domain model is the domain model corresponding to the first database table, the first data item corresponds to the third field, the second domain model is the domain model corresponding to the second database table, and the second data item corresponds to the fourth field.

6. The method of claim 1, wherein, After the determining the association information between the domain models corresponding to any two database tables according to the data association information and the primary-foreign key association information between the any two database tables, the method further comprises: outputting the domain models corresponding to the database tables and the association information between the domain models.

7. The method of claim 6, wherein: the association information between the output domain models comprises dashed lines representing data association and solid lines representing primary-foreign key association; in response to a confirmation operation on the dashed line, the dashed line is replaced by a solid line; in response to a deletion operation on the dashed line, the dashed line and the data association information corresponding to the dashed line are deleted.

8. The method of claim 1, wherein, The obtaining the structured data file corresponding to the database table of the system to be developed comprises: exporting the database table of the system to be developed into the corresponding structured data file using a database connection tool.

9. An apparatus for generating a domain model, the apparatus comprising: The method comprises: a file obtaining module configured to obtain a structured data file corresponding to a database table of a system to be developed and a table creation statement file; the structured data file comprises field information and data included in the database table; The table inter-association information determination module is configured to perform association analysis processing on the structured data files of any two database tables according to the structured data files corresponding to the database tables, determine data association information between the two database tables, and determine primary-foreign key association information between any two database tables according to the table creation statement files of the database tables. The domain model determination module is configured to extract table name and table field information of the database tables from the table creation statement files of the database tables, and generate domain models corresponding to the database tables according to the table name and table field information of the database tables. The domain model association information determination module is configured to determine association information between domain models corresponding to any two database tables according to the data association information and the primary-foreign key association information between the two database tables. The table inter-association information determination module is specifically configured to perform association analysis processing on the structured data files of any two database tables according to the structured data files corresponding to the database tables, determine data association information between the two database tables, and include the following steps. The structured data file corresponding to any of the database tables is taken as a reference file, and the reference file is sequentially associated with another structured data file for the following association analysis processing. A support degree of a first data column corresponding to a first field in the reference file and a second data column corresponding to a second field in the other structured data file is determined, wherein the first data column corresponding to the first field contains all data corresponding to the first field in the reference file, and the second data column corresponding to the second field contains all data corresponding to the second field in the other structured data file. If the support degree of the first data column and the second data column is greater than or equal to a support degree threshold, it is determined that there is data association between the first field and the second field. If the support degree of the first data column and the second data column is less than the support degree threshold, it is determined that there is no data association between the first field and the second field. The table inter-association information determination module is specifically configured to determine a number of specified row data in the second data column according to the first data column and the second data column, the specified row data being the same as any row data in the first data column. A ratio of the number of specified row data in the second data column to a total number of rows of the second data column is taken as the support degree of the first data column and the second data column.

10. An apparatus for generating a domain model, the apparatus comprising: The processor and the memory connected with the processor in communication; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory to implement the method in any one of claims 1-8. The computer readable storage medium stores computer execution instructions, and the computer execution instructions are executed by the processor to implement the method in any one of claims 1-8.

11. A computer readable storage medium, characterized in that, The computer execution instructions are executed by the processor to implement the method in any one of claims 1-8.

12. A computer program product, characterised in that, ​

Images