mirror of
https://github.com/status-im/status-go.git
synced 2025-01-10 14:47:06 +00:00
b6d4e75cf1
fix flaky test: TestRetrieveBlockedContact resolve conflict when rebase origin/develop Feat/sync activity center notification (#3581) * feat: sync activity center notification * add test * fix lint issue * fix failed test * addressed feedback from sale * fix failed test * addressed feedback from ilmotta go generate ./protocol/migrations/sqlite/... feat: add updated_at for syncing activity center notification
How to write migrations?
We only write up
migrations, down
migrations are not always possible in sqlite or
too complex/too expensive. For example to remove a column you would have to duplicate
the table, copy over the data, delete and recreated.
This can be very expensive for some tables (user_messages for example), so should not be attempted.
Notes
One issue we faced multiple times is that updates to user_messages
can be very
expensive, leading to slow upgrade times and interrupted migrations. So avoid
writes if not necessary.