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: mkdocs/docs/en/documentation/cache.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -211,6 +211,8 @@ Example of a complete configuration for `mycache.config` cache, parameters are d
211
211
2. When reading, sets the time [expiration](https://redis.io/commands/getex/) (optional)
212
212
3. Prefix a key in a specific cache to avoid key collisions within a Redis database, can be an empty string then keys will be without prefixes (**required**)
213
213
214
+
Module metrics are described in the [Metrics Reference](metrics.md#cache) section.
215
+
214
216
#### Configurator
215
217
216
218
Можно зарегистрировать `LettuceConfigurator` который позволит до настроить `Lettuce` клиент перед созданием.
Copy file name to clipboardExpand all lines: mkdocs/docs/en/documentation/database-migration.md
+28-4Lines changed: 28 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,20 +42,44 @@ Example of the complete configuration described in the `FlywayConfig` class (def
42
42
43
43
```javascript
44
44
flyway {
45
-
locations = "db/migration" //(1)!
45
+
enabled = true //(1)!
46
+
locations = ["db/migration"] //(2)!
47
+
executeInTransaction = true //(3)!
48
+
validateOnMigrate = true //(4)!
49
+
mixed = false //(5)!
50
+
configurationProperties = {} //(6)!
46
51
}
47
52
```
48
53
49
-
1. Directory paths where to look for migration scripts
54
+
1. Whether database migration is enabled when the application starts. If `false`, migrations will not be executed.
55
+
2. Directory paths where migration scripts are located.
56
+
3. Whether to execute migrations within a transaction.
57
+
4. Whether to verify checksums of existing migrations before execution. An error will occur if they do not match.
58
+
5. Whether to allow mixing transactional and non-transactional SQL operations in a single migration. If enabled, the entire migration will be executed **without a transaction** to avoid errors in databases where certain operations cannot be run inside a transaction.
59
+
60
+
This setting is only relevant for databases that do not support executing certain operations within a transaction: PostgreSQL, Aurora PostgreSQL, SQL Server, and SQLite.
61
+
6. Additional key-value configuration properties for `Flyway#configurationProperties`.
50
62
51
63
=== ":simple-yaml: `YAML`"
52
64
53
65
```yaml
54
66
flyway:
55
-
locations: "db/migration" #(1)!
67
+
enabled: true #(1)!
68
+
locations: ["db/migration"] #(2)!
69
+
executeInTransaction: true #(3)!
70
+
validateOnMigrate: true #(4)!
71
+
mixed: false #(5)!
72
+
configurationProperties: {} #(6)!
56
73
```
57
74
58
-
1. Directory paths where to look for migration scripts
75
+
1. Whether database migration is enabled when the application starts. If `false`, migrations will not be executed.
76
+
2. Directory paths where migration scripts are located.
77
+
3. Whether to execute migrations within a transaction.
78
+
4. Whether to verify checksums of existing migrations before execution. An error will occur if they do not match.
79
+
5. Whether to allow mixing transactional and non-transactional SQL operations in a single migration. If enabled, the entire migration will be executed **without a transaction** to avoid errors in databases where certain operations cannot be run inside a transaction.
80
+
81
+
This setting is only relevant for databases that do not support executing certain operations within a transaction: PostgreSQL, Aurora PostgreSQL, SQL Server, and SQLite.
82
+
6. Additional key-value configuration properties for `Flyway#configurationProperties`.
0 commit comments