SQLite migrations which cannot be completed

[evantahler]

To make it easy to develop and test locally, Grouparoo supports both SQLite and Postgres databases. As a reminder, Grouparoo does not recommend using SQLite for persisting data. If you need to persist data, use a Postgres-compatible database to back your Grouparoo deployment.

From time-to-time there may be a migration which cannot be completed when you have data loaded into your SQLite database. When this happens, you will see a message like:

[ migration ] Cannot proceed with migration - table ${table} is not empty. Please remove your SQLite database at /path/to/database.sqlite and retry the migration. See #2428 for more information.

This is due primarily to a long-standing bug with Sequelize (sequelize/sequelize#12823), the ORM Grouparoo uses. Removing your existing SQLite database will allow Grouparoo to re-create the database migrated up to include all the new changes. As you are likely using code config, Grouparoo will then re-import your Records and Properties when the application next starts.

[evantahler]

This discussion was introduced by #2426