[9.x] Adds Eloquent User Provider query handler - #44226
Merged
taylorotwell merged 3 commits intoSep 21, 2022
Merged
Conversation
Member
|
Why did you need this in your application? |
Contributor
Author
I cannot alter which columns to retrieve from the table, or even use eloquent relations, without also altering all other queries in the app. For example, I hooked a Laravel app into an existing DB where someone decided it was a good idea to have an embedded image in a column Since I cannot remove it, or move it, my only chance is to tell the User Provider to not load a column that contains 2~5 mb of data. Another alternative is to extend the User Provider but feels so hacky... |
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
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.
What
Allows the user to register a query handler for retrieving the user from the
EloquentUserProvider. This allows to tap into the query and modify columns to retrieve, like bypassing columns that may have too much data or are unused.Since it works a
newModelQuery()level, any change be overridden through callbacks when retrieving the user.Also the
setQueryHandler()can be used to erase it withnulland it can be retrieved for further inspection (or even wrapping).