fix(drizzle): check rawRelations instead of table existence to avoid naming collision (#16181)#16189
Open
deepshekhardas wants to merge 1 commit intopayloadcms:mainfrom
Open
Conversation
…naming collision (payloadcms#16181) Changed table existence check to relation existence check in buildFindManyArgs This prevents false positives when array fields are named numbers, texts, or rels Fixes payloadcms#16181
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #16181 - Array field named numbers causes TypeError
Problem: When a collection has an array field named numbers, texts, or rels, queries fail with TypeError due to table existence check false positives
Solution: Changed table existence checks to relation existence checks using adapter.rawRelations