You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: waltz-schema/src/main/resources/liquibase/README.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,22 @@
2
2
3
3
Waltz uses [Liquibase](http://www.liquibase.org/index.html) to manage it's schema.
4
4
5
+
6
+
## About
7
+
8
+
Liquibase is an open-source database change management tool that allows developers to manage and automate changes to database schemas.
9
+
It provides a way to define, track, and execute changes to database structures, such as tables, columns, indexes, and constraints.
10
+
11
+
Waltz uses Liquibase by defining changes XML "changelog" files which are versioned and stored alongside the application code (in `waltz-scheme\src\main\resources\liquibase`.
12
+
The changelog describes how to migrate the database it to newer versions, and Liquibase ensures that the changes are applied in the correct order.
13
+
14
+
5
15
## Authoring
6
16
7
17
The changelog file follows the [best practice guidelines](http://www.liquibase.org/bestpractices.html) outlined
8
18
on the liquibase site.
9
19
20
+
10
21
### Change Ids
11
22
12
23
Id's have undergone several changes since project inception. The current format is:
@@ -19,7 +30,6 @@ For example:
19
30
Strictly speaking the date is not required, but it helps when searching for changes in a certain time range.
20
31
21
32
22
-
23
33
## Updating the database
24
34
25
35
Liquibase can either apply the changes directly to the database or prepare an sql file for manual execution.
@@ -33,6 +43,7 @@ An _alternative_ mechanism to get the files is to download and extract them from
33
43
For example:
34
44

35
45
46
+
36
47
### Executing the changes using Liquibase:
37
48
38
49
This approach uses Liquibase to directly modify the database.
0 commit comments