[Feature] 多环境数据表设计同步

[yangshulin-g]

描述需求
当我拥有一个多环境的数据库，比如dev、test、pro
当我开发完成dev后，在dev进行过ddl修改，这个ddl的语句我可能需要在test或者pro也执行一遍，但这可能会在1个月或者很长时间后，我已经忘记了ddl原本的语句。找到这个ddl或者重写可能有问题。需要可以一键同步到其他环境，或者串行三个环境

你的思路
最好是提供一个可视化的表修改界面，然后方便增删改。或者就是直接写ddl语句
这个修改只能在dev数据库执行，然后可以经过各个环境的审核同步到test或者pro，而不是dev审核完我再那这个ddl去创建一个test环境的工单走流程。

这里还会涉及到多个人同时改这一个表的问题，我这里认为是锁定这个表（第一个修改的人且没有同步到下一个环境前）如果其他人也要修改，需要想这个人进行申请加入，一起修改这个表，将这个所有的修改提交到下一个环境的人应该是第一个人

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Title: [Feature] Multi-environment data table design synchronization

Describe requirements
When I have a database in multiple environments, such as dev, test, pro
After I developed the dev, I modified the ddl in the dev. I may need to execute this ddl statement in test or pro, but this may be a month or a long time later, and I have forgotten the original ddl. statement. There may be a problem finding this ddl or rewriting it. If you need to synchronize to other environments with one click, or serialize three environments

your thoughts
It is best to provide a visual table modification interface to facilitate additions, deletions and modifications. Or just write the ddl statement directly
This modification can only be executed in the dev database, and then can be synchronized to test or pro after the review of each environment. Rather than after the dev review, I will use this ddl to create a work order process for the test environment.

This also involves the problem of multiple people modifying this table at the same time. I think it is locking this table (the first person to modify it is not synchronized to the next environment). If other people want to modify it, they need to ask this person to do it. Apply to join and modify this table together. The person who submits all modifications to the next environment should be the first person.