[10.x] Binding order is incorrect when using cursor paginate with multiple unions with a where #50810
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.
When using
cursorPaginate
on a query that has multiple unions, the binding order is incorrect.This happens because:
https://github.com/laravel/framework/blob/11.x/src/Illuminate/Database/Concerns/BuildsQueries.php#L436
adds the bindings for the cursor
where
to the end of the bindings and not in the position that they should be.The result is a query that binds the wrong values to the wrong parameters in the query.
Possible solutions I can now think of are:
union
a nested array until the bindings are resolved to make the query and add the cursor bindings to the right indexunion
bindings after adding the cursor bindingsThis PR implements the first solution.
This PR is similar to #50795 but made against 10.x