This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
SQLite migrations which cannot be completed #2428
Unanswered
evantahler
asked this question in
General
Replies: 1 comment
-
This discussion was introduced by #2426 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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:
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.
Beta Was this translation helpful? Give feedback.
All reactions