Migration
The Migration configuration category includes the following configurable options:
Only Dry-Run the Migration
Include Heavyweight Skippable Migrations
Migration Versions to skip
Database Update Mode
|
|
Only Dry-Run the Migration |
|
|
|
| BOOLEAN | |
If enabled, no migration will occur during startup, even if db.schema_update_mode is set to UPDATE. Instead, the SQL that would be executed is instead logged to the log file.
|
|
|
|
false
|
|
|
|
|
Include Heavyweight Skippable Migrations |
|
|
|
| BOOLEAN | |
If enabled, additional migrations will run, which can take a very long time to run on large databases. These are not critical but can improve performance for some systems. Equivalent to the smileutil --enable-heavyweight-migrations flag
|
|
|
|
false
|
|
|
|
|
Migration Versions to skip |
|
|
|
| STRING_MULTILINE | |
Versions included here will be skipped during bootup migration, or during the SmileCDR binary migrate command. Equivalent to the smileutil --skip-versions flag
|
|
|
|
| (no default) | |
|
|
|
Database Update Mode |
|
|
|
| ENUM | |
| Values |
|
| Controls whether Smile CDR should attempt to update the FHIR storage database schema on startup. If the database schema is out of date, Smile CDR automatically runs migration on the FHIR storage schema at startup if the value is "UPDATE" If the value is "NONE", then Smile CDR will abort starting the FHIR storage module if its schema is out of date. When set to "NONE", you should use the "smileutil migrate" command to upgrade the database manually. | |
|
|
UPDATE
|
|
|