Solve foreign key error on push transfers #19870
Merged
+176
−50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
christiancp100
added
pr: fix
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Convly
approved these changes
Mar 22, 2024
echoes-hq
bot
added
the
echoes/type: bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
It solves the foreign key error on push transfers by fixing the way we are getting the component UIDs when mapping the old IDs and the new IDs.
Why is it needed?
To avoid FK Constraint errors on transfers.
How to test it?
Create a content type with a component and a repeatable component, both containing relation to another content type inside. Fill them with data and execute an export/import and/or a transfer. It should work without displaying any warning about a foreign key constraint.
Related issue(s)/PR(s)
#18350