Database physical model forward design publishing method, system and device and readable storage medium
By creating corresponding processes and branches on the integrated development, operation and maintenance platform and model design management platform, physical model changes and audits, and database change scripts are generated and published, the isolated problems of database physical model design and release process are solved, and effective management and quality control of model design behavior is achieved.
Patent Information
- Application Number
- CN202411784251.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-06
- Publication Date
- 2025-04-11
AI Technical Summary
In the prior art, the database physical model design and release process are relatively isolated and cannot be effectively integrated into the project R&D activity process, resulting in confusion in model design changes and release management, and it is difficult for designers to control the behavior of them.
Create project R&D activity processes on the integrated development and operation platform, and create development branches and design branches on the model design management platform, perform physical model changes and audits, generate and publish database change scripts, and integrate them into the code hosting platform.
The physical model design and release are integrated into the project R&D activity process, connecting the two stages of model design change and release, realizing effective management and quality control of model design behavior.
Smart Images
Figure CN119807164A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method, system, device and readable storage medium for publishing forward design of a database physical model. Background Art
[0002] At present, with the increasing complexity of software engineering, physical model design changes and release activities are poorly integrated with project R&D activities in most cases, resulting in the independence of the tools used for database physical model design and release within the project, such as navicat, erwin, or no tools are used. There is no corresponding platform to unify or integrate the database physical model forward design and release process, resulting in loose management of physical model design and release behavior, uncontrolled model design behavior, isolation of model design content between designers, and uncontrolled model design quality. In addition, physical model design tools are independent of each other and cannot well support physical model forward release behavior, resulting in serious consequences such as releasing changes first and then designing, or only releasing without designing.
[0003] To this end, a technical solution is proposed that can integrate physical model design and release into the project R&D activity process, and connect the two important stages of model design change and release. This has important guiding and practical significance for model forward design and release, and is a technical problem that needs to be urgently solved by technical personnel in this field. Summary of the invention
[0004] The purpose of this application is to solve the problem that the physical model design and release stages are relatively isolated, and the physical model designers cannot be well constrained to carry out positive model design and release behaviors. Moreover, it is not well integrated with the project development activity process, so that the physical model design change and release process cannot be well controlled by the project development process, resulting in the model design change release management in the entire project development activity. In response to the above problems, the technical solutions adopted by this application are as follows:
[0005] In a first aspect, an embodiment of the present application provides a method for forward design and publishing of a database physical model, the method comprising:
[0006] Create a project R&D activity process on the development and operation integration platform, and fill in system information, production date and R&D activity purpose in the project R&D activity process;
[0007] Based on the project R&D activity process, create development branches and design branches on the model design management platform;
[0008] Perform physical model changes on the design branch, submit the changes for review, and merge the design branch content into the development branch after passing the review;
[0009] Generate database change scripts, review the generated scripts, and publish them to the code hosting platform after passing the review.
[0010] Optionally, in creating development branches and design branches on the model design management platform based on the project R&D activity process, the creation of development branches and design branches is based on the production date of the project R&D activity process, and without the project R&D activity process, the development branches and design branches cannot be pulled and the model cannot be modified.
[0011] Optionally, the physical model change is performed on the design branch and submitted for review. After the review is passed, the design branch content is merged into the development branch. The physical model change includes at least one branch, multiple versions, and multi-person collaborative visual model design. The review of the change content is controlled based on the stage of the project R&D activity process.
[0012] Optionally, in the generation of the database change script, the generated script is reviewed and published to the code hosting platform after the review is passed. The generation of the database change script includes obtaining the change table list and generating the database table structure definition change script, and the review of the database change script includes verifying the consistency of the script with the model change content. After the review is passed, different folders and script files are created according to the production date of the R&D activity process for publication.
[0013] In a second aspect, the present invention provides a database physical model forward design publishing system, the system comprising: a first creation module, a second creation module, a first review module, and a second review module, wherein:
[0014] The first creation module is used to create a project R&D activity process on the development and operation integration platform, and fill in system information, production date and R&D activity purpose in the project R&D activity process;
[0015] The second creation module is used to create a development branch and a design branch on the model design management platform based on the project R&D activity process;
[0016] The first review module is used to make physical model changes on the design branch, submit the changes for review, and merge the design branch content into the development branch after passing the review;
[0017] The second review module is used to generate database change scripts and review the generated scripts. After passing the review, they are published to the code hosting platform.
[0018] Optionally, in creating development branches and design branches on the model design management platform based on the project R&D activity process, the creation of development branches and design branches is based on the production date of the project R&D activity process, and without the project R&D activity process, the development branches and design branches cannot be pulled and the model cannot be modified.
[0019] Optionally, the physical model change is performed on the design branch and submitted for review. After the review is passed, the design branch content is merged into the development branch. The physical model change includes at least one branch, multiple versions, and multi-person collaborative visual model design. The review of the change content is controlled based on the stage of the project R&D activity process.
[0020] Optionally, in the generation of the database change script, the generated script is reviewed and published to the code hosting platform after the review is passed. The generation of the database change script includes obtaining the change table list and generating the database table structure definition change script, and the review of the database change script includes verifying the consistency of the script with the model change content. After the review is passed, different folders and script files are created according to the production date of the R&D activity process for publication.
[0021] In a third aspect, the present invention provides an electronic device, including a processor and a memory;
[0022] The memory is used to store operation instructions;
[0023] The processor is used to execute the above-mentioned database physical model forward design and publishing method by calling the operation instruction.
[0024] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method for forward design and release of a database physical model is implemented.
[0025] The database physical model forward design and release scheme disclosed in this application creates a project R&D activity process on a development and operation integrated platform, fills in system information, production date and R&D activity purpose; based on the project R&D activity process, creates development branches and design branches on the model design management platform; and makes physical model changes on the design branch, submits the change for review, and merges the design branch content into the development branch after the review is passed; generates a database change script, and reviews the generated script, and publishes it to the code hosting platform after the review is passed. The beneficial effects brought about by the technical solution provided by this application are: integrating the physical model design and release into the project R&D activity process, connecting the two important stages of model design change and release, and having important guiding and practical significance for the model forward design and release. This technical solution can be well integrated into the project R&D activity process, so that the physical model design change activities are managed by the project R&D activities, and can ensure the positive release behavior of the model designer, thereby achieving the expected effect. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in describing the embodiments of the present application are briefly introduced below.
[0027] Figure 1 A flowchart of a database physical model forward design and publishing method provided in an embodiment of the present application;
[0028] Figure 2 A flowchart of a database physical model forward design and publishing method provided in an embodiment of the present application;
[0029] Figure 3 A schematic diagram of the structure of a database physical model forward design and publishing system provided in an embodiment of the present application;
[0030] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0031] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as limiting the present application.
[0032] It will be understood by those skilled in the art that, unless otherwise stated, the singular forms "a", "an" and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.
[0033] In order to make the objectives, technical solutions and advantages of the present application more clear, the specific implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.
[0034] The core of the present invention is to provide a database physical model forward design and publishing method. Figure 1 The figure is a flow chart of the database physical model forward design and publishing method provided in this embodiment. In order to better understand the method, Figure 1 The technical solution of this embodiment is described in detail:
[0035] Step S101: Create a project R&D activity process on the development and operation integration platform, and fill in system information, production date and R&D activity purpose in the project R&D activity process;
[0036] Step S102: Based on the project R&D activity process, create a development branch and a design branch on the model design management platform;
[0037] Step S103, making a physical model change on the design branch, submitting the change for review, and merging the design branch content into the development branch after passing the review;
[0038] Step S104: Generate a database change script, review the generated script, and publish it to the code hosting platform after passing the review.
[0039] This embodiment includes three platforms: development and operation integration, model design management, and code hosting. Among them, the development and operation integration platform is the carrier platform for the project development activity process, responsible for the full life cycle management of the project development activity, including the creation of the project development activity process, and the change of the project development activity stage (start-demand analysis-development-testing-online-end).
[0040] As a carrier platform for model design activities, the model design management platform is responsible for the full process operation and management of physical model design, providing multi-branch, multi-version, and multi-person collaborative visual model design capabilities, and receiving R&D activity process information from the development and operation integration platform to pull branches, control changes, and merge branches.
[0041] The code hosting platform is responsible for receiving and storing the database change scripts published by the model management platform.
[0042] For example, the R&D activity administrator can create a project R&D activity process on the development and operation integration platform, and fill in the main information such as system information, production date, and R&D activity purpose. When the physical model designer recognizes that a database change is required, he can separate the physical model design task from the R&D activity process and fill in important information such as the task name, task purpose, and task person. After the R&D activity process and physical model design task are created, the development and operation integration platform will synchronize the R&D activity process information and physical model design task information to the model design management platform in real time.
[0043] As a preferred method of this embodiment, in step S102, the creation of development branches and design branches is based on the production date of the project R&D activity process, and without the project R&D activity process, the development branches and design branches cannot be pulled, and the model cannot be modified.
[0044] As a preferred method of this embodiment, in step S103, the physical model change includes at least one branch, multiple versions, and multi-person collaborative visual model design, and the review of the change content is controlled based on the stage of the project R&D activity process.
[0045] As a preferred method of this embodiment, in step S104, the generation of the database change script includes obtaining the change table list and generating the database table structure definition change script, and the review of the database change script includes verifying the consistency of the script with the model change content. After the review is passed, different folders and script files are created and published according to the production date of the R&D activity process.
[0046] Taking R&D activities as an example, the following will introduce the specific implementation process of using the database physical model forward design and release method described in the embodiment of the present application to achieve the management of R&D activities and ensure the positive release behavior of model designers.
[0047] 1. Create project R&D activities
[0048] The R&D activity administrator can create the project R&D activity process on the development and operation integration platform, and fill in the main information such as system information, production date, and R&D activity purpose. When the physical model designer recognizes that a database change is required, he can separate the physical model design task from the R&D activity process and fill in important information such as the task name, task purpose, and task person. After the R&D activity process and physical model design task are created, the development and operation integration platform will synchronize the R&D activity process information and physical model design task information to the model design management platform in real time.
[0049] 2. Model changes
[0050] Physical model designers can make design changes based on existing models or new models on the model design management platform. The model design management platform manages changes based on branches, and the model branch types are divided into main branches, development branches, and design branches. Physical model designers pull the development branch from the main branch according to the production date of the project R&D activity process. The name of the development branch is the name of the project R&D activity process, and then create a design branch based on the physical model design task. The design branch name is the name of the physical model design task. Physical model designers can make physical model changes on the design branch. After the change is submitted for review and passed, the model design management platform will merge the design branch content into the development branch. Model branch pulling must be based on the project R&D activity process, that is, without the project R&D activity process, the development branch and design branch cannot be pulled, and the model cannot be modified. In addition, the model change behavior can be controlled according to the stage of the project R&D activity process according to the actual situation (for example, physical model design changes are prohibited in the online stage) to ensure the positivity of physical model design changes.
[0051] 3. Database script generation and publishing
[0052] The model design management platform can obtain all change table lists of the physical model development branch and generate a database change script (database table structure definition change script). Users can modify the generated script and add non-database change statements (update statements or delete statements). After the modification is completed, the script as a whole needs to be checked. The database change script is verified during the inspection phase. The database change script needs to be consistent with the selected model change content (the database table structure definition change script is semantically consistent). After the inspection is passed, it will be released. Different folders and script files will be created according to the production date of the R&D activity process, and all generated files will be published to the code hosting platform for storage.
[0053] 4. End of R&D activities
[0054] After the R&D activity process reaches the online stage, the development and operation integration platform will synchronize the R&D activity process status information to the model management platform, triggering a branch merge event. The model management platform will merge the development model branch bound to the R&D activity process into the main model branch.
[0055] Figure 2This is a flowchart of the specific steps of this embodiment. In the embodiment of this application, by creating a project R&D activity process on the development and operation integration platform, fill in the system information, production date and R&D activity purpose; based on the project R&D activity process, create a development branch and a design branch on the model design management platform; and make physical model changes on the design branch, submit for review after the change, and merge the design branch content into the development branch after the review is passed; generate a database change script, and review the generated script, and publish it to the code hosting platform after the review is passed. It realizes the integration of physical model design release into the project R&D activity process, connecting the two important stages of model design change and release, which has important guidance and practical significance for the forward design release of the model. This technical solution can be well integrated into the project R&D activity process, so that the physical model design change activities are managed by the project R&D activities, and the forward release behavior of the model designer can be guaranteed, thereby achieving the expected effect.
[0056] based on Figure 1 The embodiment shown provides a database physical model forward design and publishing method. Figure 3 A database physical model forward design and publishing system provided by an embodiment of the present application is shown. Figure 3 As shown, the system may mainly include: 201 a first creation module, 202 a second creation module, 203 a first review module, 204 a second review module, wherein:
[0057] 201 A first creation module: used to create a project R&D activity process on the development and operation integration platform, and fill in system information, production date and R&D activity purpose in the project R&D activity process;
[0058] 202 A second creation module: used to create a development branch and a design branch on the model design management platform based on the project R&D activity process;
[0059] 203 A first review module: used to change the physical model on the design branch, submit the change for review, and merge the design branch content into the development branch after passing the review;
[0060] 204 The second review module: used to generate database change scripts, review the generated scripts, and publish them to the code hosting platform after passing the review.
[0061] As a preferred method of this embodiment, in the second creation module, the creation of development branches and design branches is based on the production date of the project R&D activity process, and without the project R&D activity process, the development branches and design branches cannot be pulled and the model cannot be modified.
[0062] As a preferred method of this embodiment, in the first review module, the physical model change includes at least one branch, multiple versions, and multi-person collaborative visual model design, and the review of the change content is controlled based on the stage of the project R&D activity process.
[0063] As a preferred method of this embodiment, in the second review module, the generation of the database change script includes obtaining the change table list and generating the database table structure definition change script, and the review of the database change script includes verifying the consistency of the script with the model change content. After the review is passed, different folders and script files are created and published according to the production date of the R&D activity process.
[0064] In the embodiment of the present application, by creating a project R&D activity process on the development and operation integration platform, filling in system information, production date and R&D activity purpose; based on the project R&D activity process, creating a development branch and a design branch on the model design management platform; and making physical model changes on the design branch, submitting the change for review, and merging the design branch content into the development branch after the review is passed; generating a database change script, and reviewing the generated script, and publishing it to the code hosting platform after the review is passed. It realizes the integration of physical model design release into the project R&D activity process, connecting the two important stages of model design change and release, which has important guiding and practical significance for the forward design release of the model. This technical solution can be well integrated into the project R&D activity process, so that the physical model design change activities are managed by the project R&D activities, and the forward release behavior of the model designer can be guaranteed, thereby achieving the expected effect.
[0065] It can be understood that the above modules of the database physical model forward design and publishing system in this embodiment have the functions of implementing Figure 1 The functions of the corresponding steps of the method in the embodiment shown in . The function can be implemented by hardware, or by hardware executing the corresponding software. The hardware or software includes one or more modules corresponding to the above functions. The above modules can be software and / or hardware, and the above modules can be implemented separately or integrated with multiple modules. For the functional description of the above modules, please refer to Figure 1 The corresponding description of the method in the embodiment shown in will not be repeated here.
[0066] An embodiment of the present application provides an electronic device, including a processor and a memory;
[0067] A memory, used for storing operation instructions;
[0068] The processor is used to execute the database physical model forward design and publishing method provided in any embodiment of the present application by calling an operation instruction.
[0069] As an example, Figure 4 A schematic diagram of the structure of an electronic device applicable to the embodiment of the present application is shown. Figure 4 As shown, the electronic device 2000 includes: a processor 2001 and a memory 2003. The processor 2001 and the memory 2003 are connected, such as through a bus 2002. Optionally, the electronic device 2000 may also include a transceiver 2004. It should be noted that in actual applications, the transceiver 2004 is not limited to one, and the structure of the electronic device 2000 does not constitute a limitation on the embodiments of the present application.
[0070] The processor 2001 is applied in the embodiment of the present application to implement the method shown in the above method embodiment. The transceiver 2004 may include a receiver and a transmitter. The transceiver 2004 is applied in the embodiment of the present application to implement the function of the electronic device of the embodiment of the present application communicating with other devices when executed.
[0071] Processor 2001 may be a CPU (Central Processing Unit), a general purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 2001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.
[0072] The bus 2002 may include a path to transmit information between the above components. The bus 2002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 2002 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0073] The memory 2003 can be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.
[0074] Optionally, the memory 2003 is used to store application code for executing the solution of the present application, and the execution is controlled by the processor 2001. The processor 2001 is used to execute the application code stored in the memory 2003 to implement the database physical model forward design publishing method provided in any embodiment of the present application.
[0075] The electronic device provided in the embodiment of the present application is applicable to any embodiment of the above method and will not be described in detail here.
[0076] An embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the database physical model forward design and publishing method shown in the above method embodiment is implemented.
[0077] The computer-readable storage medium provided in the embodiments of the present application is applicable to any embodiment of the above method and will not be described in detail here.
[0078] The database physical model forward design and release solution provided in the embodiment of the present application is to create a project R&D activity process on the development and operation integration platform, fill in the system information, production date and R&D activity purpose; based on the project R&D activity process, create a development branch and a design branch on the model design management platform; and make physical model changes on the design branch, submit the change for review, and merge the design branch content into the development branch after the review is passed; generate a database change script, and review the generated script, and publish it to the code hosting platform after the review is passed. It realizes the integration of physical model design and release into the project R&D activity process, connecting the two important stages of model design change and release, which has important guiding and practical significance for the model forward design release. This technical solution can be well integrated into the project R&D activity process, so that the physical model design change activities are managed by the project R&D activities, and the positive release behavior of the model designer can be guaranteed, thereby achieving the expected effect.
[0079] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the specific system can be divided into different functional modules to complete all or part of the functions described above.
[0080] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0081] In several embodiments covered by the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, or it can be an electrical, mechanical or other form of connection.
[0082] The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the embodiments of the present application.
[0083] In addition, each functional module in each embodiment of the present application can be implemented in the form of hardware or in the form of software functional modules. If these functional modules are implemented in the form of software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application is essentially or part of the prior art that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a computer program product, which includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program product is stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, a computer instruction can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).
[0084] The above contents are merely examples and explanations of the structure of the present invention. The technicians in this technical field may make various modifications or additions to the specific embodiments described or replace them in a similar manner. As long as they do not deviate from the structure of the invention or exceed the scope defined by the claims, they should all fall within the protection scope of the present invention.
Claims
1. A database physical model forward design and publishing method, characterized in that: The following steps are involved: Create a project R&D activity process on the development and operation integration platform, and fill in system information, production date and R&D activity purpose in the project R&D activity process; Based on the project R&D activity process, create development branches and design branches on the model design management platform; Perform physical model changes on the design branch, submit the changes for review, and merge the design branch content into the development branch after passing the review; Generate database change scripts, review the generated scripts, and publish them to the code hosting platform after passing the review.
2. The database physical model forward design and publishing method according to claim 1, characterized in that: In creating development branches and design branches on the model design management platform based on the project R&D activity process, the creation of development branches and design branches is based on the production date of the project R&D activity process, and without the project R&D activity process, the development branches and design branches cannot be pulled, and the model cannot be modified.
3. The database physical model forward design and publishing method according to claim 1, characterized in that: The physical model changes are made on the design branch and submitted for review. After the review is passed, the design branch content is merged into the development branch. The physical model changes include at least one branch, multiple versions, and multi-person collaborative visual model design. The review of the change content is controlled based on the stage of the project R&D activity process.
4. The database physical model forward design and publishing method according to claim 1, characterized in that: In the generation of the database change script, the generated script is reviewed and published to the code hosting platform after the review is passed. The generation of the database change script includes obtaining the change table list and generating the database table structure definition change script, and the review of the database change script includes verifying the consistency of the script with the model change content. After the review is passed, different folders and script files are created according to the production date of the R&D activity process for publication.
5. A database physical model forward design and publishing system, characterized in that: The system comprises: a first creation module, a second creation module, a first review module, and a second review module, wherein: The first creation module is used to create a project R&D activity process on the development and operation integration platform, and fill in system information, production date and R&D activity purpose in the project R&D activity process; The second creation module is used to create a development branch and a design branch on the model design management platform based on the project R&D activity process; The first review module is used to make physical model changes on the design branch, submit the changes for review, and merge the design branch content into the development branch after passing the review; The second review module is used to generate database change scripts and review the generated scripts. After passing the review, they are published to the code hosting platform.
6. The database physical model forward design and publishing system according to claim 5, characterized in that: In creating development branches and design branches on the model design management platform based on the project R&D activity process, the creation of development branches and design branches is based on the production date of the project R&D activity process, and without the project R&D activity process, the development branches and design branches cannot be pulled, and the model cannot be modified.
7. The database physical model forward design and publishing system according to claim 5, characterized in that: The physical model changes are made on the design branch and submitted for review. After the review is passed, the design branch content is merged into the development branch. The physical model changes include at least one branch, multiple versions, and multi-person collaborative visual model design. The review of the change content is controlled based on the stage of the project R&D activity process.
8. The database physical model forward design and publishing system according to claim 5, characterized in that: In the generation of the database change script, the generated script is reviewed and published to the code hosting platform after the review is passed. The generation of the database change script includes obtaining the change table list and generating the database table structure definition change script, and the review of the database change script includes verifying the consistency of the script with the model change content. After the review is passed, different folders and script files are created according to the production date of the R&D activity process for publication.
9. An electronic device, characterized in that: including a processor and a memory; The memory is used to store operation instructions; The processor is used to execute the method according to any one of claims 1 to 4 by calling the operation instruction.
10. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.