So, I am using Laravel's built in soft Deletes and I have run into an issue. When I call
it returns a query builder object. This would be fine for most cases but after I call this I then want to call a method like
which is specific to the MODEL and I no longer have access to now that I only have a query builder.
The reverse relationship also does not work as
also wants a model where any kind of parsing method I can think of would return the model's query builder.
So I was hoping to find a way to modify a model object with where clauses so I can add my filters and send the model to
WITH the filters in place. I am honestly not sure how to do this. Worst case scenario I can have the filter method return the query builder without any global scopes and add the
query on to the end manually.
So the end result would be something like this:
Im not trying to get a giant collection and whittle it down. Even with chunking when you have a few million rows it can get slow really quick, especially when you bring in filtering. Technically, for a one off, I could just add multiple
clauses to the query builder before i call
but that would mean doing custom filtering in every controller's index. So i am looking to abstract it as a method in the model that parses filters sent in and adds them to the model (this is the part im not sure on. Kind of like: github.com/marcelgwerder/laravel-api-handler