fix: missing cross-base link fields when update dbTableName #1200
+136
−49
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
tea-artist
force-pushed
the
fix/update-db-table-name
branch
from
6f76395 to
935d424
Compare
|
Deployment Status: ✅ Success |
🧹 Preview Environment Cleanup
|
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.
If the current table is associated with the link field or lookup field of another base, modifying dbTableName will lead to a 500 error in modifying the link field cell.
In the original code, when updating the database name, the fkHostTableName in the relevant link field and lookup field was updated. However, the code query condition restricts only querying the field information under the current baseId. But since the cross-base link was introduced later, the fkHostTableName may come from different bases. At this time, a query of global fields is needed to ensure that the modification is correct.