tekrda

Thanks for your reply!

An instance of a model represent an entity and thus contains methods related to that one entity. I've many queries which return a collections of a model ( many records ) and i want to wrap those queries into different functions so that i can reuse them. so adding those functions in a model is a good idea or bad?

here is an example:

$flights = Flight::where('destination', 'Paris')->get();

this is just an example, i've many and much complex queries which are going to be used in several controllers. repeating same query will make code unmanageable and putting them all in model to reuse them doesn't make sense as well. so what the solution creating repositories with different numbers and types of functions for different models or else? please suggest.. thank you!

Hi,

is there good alternatives of mixing methods for retrieving collections of Products, with methods for instances of one Product in a model?

Thank you very much! in case it might be helpful for someone or might be some sane person reply that "it is not a good idea to do this and that.." i'v started using laravel lately and i too have many such questions for that i keep googling which pop-ups such "archaeological debris". And the good thing is that many are helpful.

one can add sidebar as part of content view. include sidebar using @include('partials.sidebar') only in the required pages template instead of including in layout template globally.