2020-10-21 01:33:31 -07:00
|
|
|
Example to demonstrate tests for schema migrations.
|
|
|
|
|
|
|
|
See `test/migration_test.dart` on how to use the generated verification code.
|
|
|
|
|
|
|
|
## Workflow
|
|
|
|
|
|
|
|
### Schema changes
|
|
|
|
|
|
|
|
After adapting a schema and incrementing the `schemaVersion` in the database, run
|
|
|
|
|
|
|
|
```
|
2022-03-02 08:23:11 -08:00
|
|
|
dart run drift_dev schema dump lib/database.dart drift_migrations/
|
2020-10-21 01:33:31 -07:00
|
|
|
```
|
|
|
|
|
|
|
|
### Generating test code
|
|
|
|
|
|
|
|
Run
|
|
|
|
|
|
|
|
```
|
2021-12-01 12:06:16 -08:00
|
|
|
dart run drift_dev schema generate drift_migrations/ test/generated/ --data-classes --companions
|
2020-10-21 01:33:31 -07:00
|
|
|
```
|
2022-01-19 10:55:19 -08:00
|
|
|
|
|
|
|
We're also using test code inside `lib/` to run migrations with older definitions of tables.
|
|
|
|
This isn't required for all migrations, but can be useful in some cases.
|
|
|
|
|
|
|
|
```
|
|
|
|
dart run drift_dev schema generate drift_migrations/ lib/src/generated
|
|
|
|
```
|