-
Notifications
You must be signed in to change notification settings - Fork 28
Preparations of some tables to migrate #7477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Preparations of some tables to migrate #7477
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7477 +/- ##
==========================================
+ Coverage 87.75% 89.44% +1.69%
==========================================
Files 1784 1515 -269
Lines 68856 59753 -9103
Branches 1133 531 -602
==========================================
- Hits 60422 53447 -6975
+ Misses 8122 6163 -1959
+ Partials 312 143 -169
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
cd1baf9
to
cad45da
Compare
|
What do these changes do?
Preparations for the database migration to another system.
destination database has already data
some of the data in the source and destination is the same. e.g. the same user, defined by its email is in both, then the user_id from the source has to be mapped to the user_id of the destination and all the references need to be kept
final user should not do anything
is there any other resource (like users) that can be repeated? I guess products, ... check which are missing
basic ideas (by @sanderegg )
thoughts
Related issue/s
How to test
Dev-ops
None