CN114895955A - Method, device and equipment for controlling metadata version of low-code platform - Google Patents
Method, device and equipment for controlling metadata version of low-code platform Download PDFInfo
- Publication number
- CN114895955A CN114895955A CN202210335156.XA CN202210335156A CN114895955A CN 114895955 A CN114895955 A CN 114895955A CN 202210335156 A CN202210335156 A CN 202210335156A CN 114895955 A CN114895955 A CN 114895955A
- Authority
- CN
- China
- Prior art keywords
- metadata
- user
- warehouse
- git
- private
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for controlling metadata version of a low-code platform, which relates to the technical field of software development and solves the technical problem that the prior low-code platform can not realize accurate version control on metadata for metadata storage, and the method comprises the following steps: establishing a metadata main warehouse, and storing the metadata in the metadata main warehouse in a git mode; cloning a metadata private warehouse for each user from a metadata main warehouse by using a git clone api; uniformly storing a metadata main warehouse and a metadata private warehouse in the same network shared disk; storing the metadata of the user for business design into a metadata private warehouse of the user, or cloning the metadata from a metadata main warehouse to the metadata private warehouse of the user by the user and modifying the metadata; and submitting the changed content in the metadata private warehouse to a metadata main warehouse by using the gitcommit and git push api. The invention also discloses a device and equipment for controlling the metadata version of the low-code platform.
Description
Technical Field
The invention relates to the technical field of software development, in particular to a method for controlling metadata version of a low-code platform.
Background
In the low-code platform of the market at the present stage, a relational database or a non-relational database is generally used for storing metadata, and by using the storage mode, accurate version control on the metadata cannot be realized, so that a user cannot see the content of each version design, select a proper version for rollback, and perform parallel business design and conflict resolution.
Disclosure of Invention
The technical problem to be solved by the present invention is to solve the above-mentioned deficiencies of the prior art, and an object of the present invention is to provide a method for controlling metadata version of a low-code platform, which is convenient for a user to check the design content of each version.
The invention also aims to provide a device for controlling the metadata version of the low-code platform, which is convenient for a user to check the design content of each version.
The invention also aims to provide equipment for controlling the metadata version of the low-code platform, which can facilitate a user to check the design content of each version.
In order to achieve the above object, the present invention provides a method for metadata version control of a low-code platform, comprising:
establishing a metadata main warehouse, and storing metadata in the metadata main warehouse in a git mode;
using a git clone api to clone a metadata private repository for each user from the metadata master repository;
uniformly storing the metadata main warehouse and the metadata private warehouse in the same network shared disk;
storing the metadata of the user for business design into a metadata private warehouse of the user, or cloning the metadata from the metadata main warehouse to the metadata private warehouse of the user by the user and modifying the metadata;
and submitting the changed content in the metadata private warehouse to the metadata main warehouse by using git commit and git push api.
As a further improvement, when multiple users edit metadata, the latest metadata in the metadata master repository is pulled using git pull api, and it is checked whether the metadata of the metadata private repository conflicts with the metadata of the metadata master repository.
Further, if there is a conflict, the content of the conflict is sent back to the user, and the user is allowed to modify the metadata again.
Further, the git log api is used to view the change history of the metadata from the metadata repository and return the changed content to the user.
In order to achieve the second objective, the present invention provides an apparatus for metadata version control of a low code platform, comprising:
the low-code platform designer is used for providing a visualization mode for a user, realizing service design by dragging and dragging a ground and describing design content by using metadata;
the metadata service module is used for receiving the metadata of the low-code platform designer, and storing the metadata, reading the metadata and viewing the metadata by using a git interface;
the metadata main warehouse is used for storing metadata version information and file information;
a metadata private repository for providing a repository for individual use by a user;
and the network shared disk is used for uniformly storing the metadata main warehouse and the metadata private warehouse.
As a further improvement, when a user opens and enters the low code platform designer, the metadata service module checks whether the user enters for the first time; if the user enters for the first time, the metadata service module uses git clone api to clone a metadata private repository for the user from the metadata master repository.
Further, the user uses the low-code platform designer to design and store the service; and the metadata service module uses a file api to store the metadata of the business design into a file of a metadata private warehouse of the user.
Further, a user submits a business design using the low code platform designer; the metadata service module uses git pull api to pull the latest metadata of the metadata main warehouse and checks whether the metadata of the metadata private warehouse of the user conflicts with the metadata of the metadata main warehouse; if the conflict exists, the content with the conflict is sent back to the user, and the user is enabled to modify the metadata again; and if no conflict exists, using git commit and git push api to submit the changed content in the metadata private warehouse to the metadata main warehouse.
Further, a user views the content of the design change version using the low code platform designer; and the metadata service module checks the change history of the metadata from the metadata main warehouse by using git log api and returns the change content to the user.
In order to achieve the third objective, the invention provides a device for metadata version control of a low-code platform, which is characterized by comprising a processor and a memory connected with the processor;
the memory for storing a computer program for performing the above method;
the processor is used for calling and executing the computer program in the memory.
Advantageous effects
Compared with the prior art, the invention has the advantages that:
the invention sets a metadata main warehouse and a metadata private warehouse, and uses a git interface to store metadata, read the metadata and check the metadata, in a low code platform, a user can check the design content of each version, select the version needing to be backed off, check the change content of each version, the user can design in parallel by a plurality of people, and automatically sends the content with conflict back to the user when the design content conflicts, so that the user can revise the metadata, and the conflict problem is solved leisurely by merging the metadata.
Drawings
FIG. 1 is an overall framework of the present invention;
FIG. 2 is a flow diagram of cloning a metadata private repository from a metadata master repository in accordance with the present invention;
FIG. 3 is a flow diagram of the present invention using a designer to save a business design;
FIG. 4 is a flow diagram of the present invention for submitting a business design using a designer;
FIG. 5 is a flow chart of the present invention for viewing a changed version using a designer.
Detailed Description
The invention will be further described with reference to specific embodiments shown in the drawings.
Referring to fig. 1-5, a method of low code platform metadata version control includes:
establishing a metadata main warehouse, wherein metadata are stored in the metadata main warehouse in a git mode, and the metadata are data for describing the design content of the low-code platform;
cloning a metadata private warehouse for each user from a metadata main warehouse by using a git clone api;
the metadata main warehouse and the metadata private warehouse are uniformly stored in the same network shared disk, so that metadata of the metadata private warehouse can be conveniently submitted to the metadata main warehouse;
storing the metadata of the user for business design into a metadata private warehouse of the user, or cloning the metadata from a metadata main warehouse to the metadata private warehouse of the user by the user and modifying the metadata;
and submitting the changed contents in the metadata private warehouse to a metadata main warehouse by using the git commit and git push api.
When multiple users edit metadata, the latest metadata in the metadata master repository is pulled using git pull api, and it is checked whether the metadata of the metadata private repository conflicts with the metadata of the metadata master repository. And if the conflict exists, sending the content with the conflict back to the user, and enabling the user to modify the metadata again, and after the conflict does not exist, submitting the content after the change in the metadata private warehouse to a metadata main warehouse by using git commit and git push api.
The git log api is used to view the change history of the metadata from the metadata master repository and return the change content to the user.
An apparatus for low code platform metadata versioning, comprising:
the low-code platform designer is used for providing a visualization mode for a user, realizing service design by dragging and dragging a ground and describing design content by using metadata;
the metadata service module is used for receiving metadata of the low code platform designer, storing the metadata, reading the metadata and checking the metadata by using a git interface;
the metadata main warehouse is used for storing metadata version information and file information;
a metadata private repository for providing a repository for individual use by a user;
and the network shared disk is used for uniformly storing the metadata main warehouse and the metadata private warehouse.
When a user opens and enters a low-code platform designer, a metadata service module checks whether the user enters for the first time; if the user is the first entry, the metadata service module uses the git clone api to clone a metadata private repository for the user from the metadata master repository.
A user uses a low-code platform designer to design and store services; the metadata service module uses the file api to save the metadata of the business design into the file of the user's metadata private repository.
A user submits a business design by using a low-code platform designer; the metadata service module uses git pull api to pull the latest metadata of the metadata main warehouse and checks whether the metadata of the metadata private warehouse of the user conflicts with the metadata of the metadata main warehouse; if the conflict exists, the content with the conflict is sent back to the user, and the user is enabled to modify the metadata again; if no conflict exists, the content of the change in the metadata private warehouse is submitted to the metadata main warehouse by using git commit and git push api.
A user uses a low-code platform designer to view the content of a design change version; the metadata service module uses git log api to view the change history of the metadata from the metadata master repository and returns the change content to the user.
A low code platform metadata version control device comprises a processor, a memory connected with the processor;
the memory is used for storing a computer program for executing the method;
the processor is used to call and execute the computer program in the memory.
The invention mainly carries out version control based on the git file mode, can accurately obtain each character change record by using the git mode, and is very suitable for accurately checking the modification information of each version. Under the condition of simultaneous editing by multiple persons, the problem of conflict during editing by multiple persons can be well solved.
The above are only preferred embodiments of the present invention, and it should be noted that it is obvious to those skilled in the art that various changes and modifications can be made without departing from the structure of the present invention, which will not affect the effect of the implementation of the present invention and the practicability of the patent.
Claims (10)
1. A method for metadata versioning of a low code platform, comprising:
establishing a metadata main warehouse, and storing metadata in the metadata main warehouse in a git mode;
using a git clone api to clone a metadata private repository for each user from the metadata master repository;
uniformly storing the metadata main warehouse and the metadata private warehouse in the same network shared disk;
storing the metadata of the user for business design into a metadata private warehouse of the user, or cloning the metadata from the metadata main warehouse to the metadata private warehouse of the user by the user and modifying the metadata;
and submitting the changed content in the metadata private warehouse to the metadata main warehouse by using git commit and git push api.
2. The method for metadata version control of a low code platform as claimed in claim 1, wherein when multiple users edit metadata, the latest metadata in the metadata main warehouse is pulled by using git pull api, and whether the metadata of the metadata private warehouse conflicts with the metadata of the metadata main warehouse is checked.
3. The method of claim 2, wherein if there is a conflict, the conflicting content is sent back to the user to allow the user to modify the metadata again.
4. The method of claim 1, wherein git log api is used to view metadata change history from the metadata repository and return the change to the user.
5. An apparatus for low code platform metadata versioning, comprising:
the low-code platform designer is used for providing a visualization mode for a user, realizing service design by dragging and dragging a ground and describing design content by using metadata;
the metadata service module is used for receiving the metadata of the low-code platform designer, and storing the metadata, reading the metadata and viewing the metadata by using a git interface;
the metadata main warehouse is used for storing metadata version information and file information;
a metadata private repository for providing a repository for individual use by a user;
and the network shared disk is used for uniformly storing the metadata main warehouse and the metadata private warehouse.
6. The apparatus for metadata version control of low code platform according to claim 5, wherein when a user opens and enters the low code platform designer, the metadata service module checks whether the user enters for the first time; if the user enters for the first time, the metadata service module uses git clone api to clone a metadata private repository for the user from the metadata master repository.
7. The apparatus for metadata version control of low code platform according to claim 5, wherein the user uses the low code platform designer to design and save the business; and the metadata service module uses a file api to store the metadata of the business design into a file of a metadata private warehouse of the user.
8. The apparatus of claim 5, wherein a user submits a business design using the low code platform designer; the metadata service module uses git pull api to pull the latest metadata of the metadata main warehouse and checks whether the metadata of the metadata private warehouse of the user conflicts with the metadata of the metadata main warehouse; if the conflict exists, the content with the conflict is sent back to the user, and the user is enabled to modify the metadata again; if no conflict exists, using git commit and git push api to submit the changed content in the metadata private repository to the metadata master repository.
9. The apparatus of claim 5, wherein a user uses the low code platform designer to view the content of the design change version; and the metadata service module checks the change history of the metadata from the metadata main warehouse by using the gitlogapi and returns the change content to the user.
10. An apparatus for low code platform metadata version control, comprising a processor, a memory coupled to the processor;
the memory for storing a computer program for performing the method of any one of claims 1-4;
the processor is used for calling and executing the computer program in the memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210335156.XA CN114895955A (en) | 2022-03-31 | 2022-03-31 | Method, device and equipment for controlling metadata version of low-code platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210335156.XA CN114895955A (en) | 2022-03-31 | 2022-03-31 | Method, device and equipment for controlling metadata version of low-code platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114895955A true CN114895955A (en) | 2022-08-12 |
Family
ID=82716452
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210335156.XA Pending CN114895955A (en) | 2022-03-31 | 2022-03-31 | Method, device and equipment for controlling metadata version of low-code platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114895955A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115629746A (en) * | 2022-12-22 | 2023-01-20 | 西安葡萄城软件有限公司 | Method and system for multi-person collaborative development of low-code platform |
-
2022
- 2022-03-31 CN CN202210335156.XA patent/CN114895955A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115629746A (en) * | 2022-12-22 | 2023-01-20 | 西安葡萄城软件有限公司 | Method and system for multi-person collaborative development of low-code platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220092059A1 (en) | Dynamically materialized views for sheets based data | |
| US11086894B1 (en) | Dynamically updated data sheets using row links | |
| US10545981B2 (en) | Virtual repository management | |
| US8311974B2 (en) | Modularized extraction, transformation, and loading for a database | |
| CN113297320B (en) | Distributed database system and data processing method | |
| US20070192374A1 (en) | Virtual repository management to provide functionality | |
| CN111784108B (en) | Modeling method and device of main data management platform | |
| CN102272751A (en) | Data integrity in a database environment through background synchronization | |
| CN114925084A (en) | Distributed transaction processing method, system, device and readable storage medium | |
| CN108829651A (en) | A kind of method, apparatus of document treatment, terminal device and storage medium | |
| US10922328B2 (en) | Method and system for implementing an on-demand data warehouse | |
| CN114895955A (en) | Method, device and equipment for controlling metadata version of low-code platform | |
| CN111191153A (en) | Information technology consultation service display device | |
| US8156422B2 (en) | Method and apparatus for importing data from an application into a second application | |
| US8229946B1 (en) | Business rules application parallel processing system | |
| WO2021234019A1 (en) | Database management methods and associated apparatus | |
| CN112948441A (en) | Financial data-oriented multidimensional data aggregation method and equipment | |
| JP2017010376A (en) | Mart-less verification support system and mart-less verification support method | |
| CN111143328A (en) | Agile business intelligent data construction method, system, equipment and storage medium | |
| CN114611476B (en) | Form content structuring processing method and device | |
| CN116226092B (en) | Database updating method and device | |
| CN108804134A (en) | Software version management method, device, system based on product feature and medium | |
| US8504592B2 (en) | Data organization tool and apparatus for remotely managing a meeting | |
| US10372614B1 (en) | Smart data engine system and method | |
| CN117546158A (en) | Ingest system for distributed graphics database |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |