gofr.dev
Migration Handling #1367
Unanswered
akshat-zopsmart
asked this question in
Q&A
Migration Handling
#1367
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Overview
gofr currently creates migration table/records in each of the datastore it's connected to for migrations being run on any of the data stores.
Issue Faced
Multiple applications are using a single Redis instance as cache (not the ideal implementation) - migrations in those applications (on SQL) are conflicting because of migration entries getting added in Redis
Suggested Implementation
Framework should maintain the migration table/recored only in the respective data store where the migration is running and not in all the connected data stores.
Beta Was this translation helpful? Give feedback.
All reactions