This is an automated email from the ASF dual-hosted git repository.
mappjzc pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
The following commit(s) were added to refs/heads/main by this push:
new 9389aa144 delete duplicated text (#221)
9389aa144 is described below
commit 9389aa14425660397e90d156714aa1236e65858c
Author: mindlesscloud <[email protected]>
AuthorDate: Fri Sep 23 00:45:38 2022 +0800
delete duplicated text (#221)
---
docs/DeveloperManuals/DBMigration.md | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/docs/DeveloperManuals/DBMigration.md
b/docs/DeveloperManuals/DBMigration.md
index b165644b5..b4394d33c 100644
--- a/docs/DeveloperManuals/DBMigration.md
+++ b/docs/DeveloperManuals/DBMigration.md
@@ -14,12 +14,8 @@ The migration scripts are written with gorm in Golang to
support different SQL d
## Migration Script
Migration script describes how to do database migration.
They implement the `Script` interface.
-When DevLake starts, scripts register themselves to the framework by invoking
the `Register` function
-
-The method `Up` contains the steps of migration. When you write a new
migration script, please pay attention to the fault tolerance and the side
effect.
-It would be better if the failed script could be safely retry, in case of
something goes wrong during the migration. For this purpose, the migration
scripts should be well-designed.
-For example, if you created a temporary table in the `Up` method, it should be
dropped before exiting, regardless of success or failure.
-Using the `defer` statement to do some cleanup is a good idea.
+When DevLake starts, scripts register themselves to the framework by invoking
the `Register` function.
+The method `Up` contains the steps of migration.
```go
type Script interface {
