[6.x] Prevent ambiguous column with table name prefix #31174
Merged
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.
Description
When fetching a multi polymorphic relationships, the query builder is creating the query without inject the table name prefix in the query, throwing a MySQL ambiguous column error.
With this fix
QueriesRelationships
will automatically add thetable name
before the column definition preventing this kind of errors.Test case
Error
Fetching
Model_1::filteredModels()
the query builder return ambiguous column error.Returned query
Expected query