[5.8] Fix UPDATE and DELETE queries with join bindings on PostgreSQL #29306
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.
On PostgreSQL, Laravel implements
UPDATE
andDELETE
queries with joins by adding their constraints after theWHERE
constraints. If both clauses have bindings, their order is incorrect:We have to put the
where
bindings before thejoin
bindings.We could also swap the constraints in the generated SQL, but that's quite cumbersome.