No repeating Eloquent query statements in the mathods of a controller

Thank you for your suggestion! The solution 1 seems to be more close to what I have in my mind but for the sake of good and clean modern programming I try not to use it. In solution 2 we will try to create functions into the model which will be available to be called in whatever controller. ButI have not used scopes in models. Besides reading the documentation I have no real experience in working with scopes. Would you mind giving me any good working example?

    Below is the index method of PagamController      

class PagamController extends Controller
{
    public function index(Request $request)
    {
        $currentefimeriosid = auth()->user()->relates_to_efimerios_id;
        $efimeriosdata = Efimer::findOrFail($currentefimeriosid);
       $currentenoriaid = $efimeriosdata->unit->id;

        $pagams = Pagam::with('unit')
                ->where('unit_id',$currentenoriaid)
                ->orderBy('arprot')
            ->get();
            $minyear = Pagam::whereNotNull('etoscreated')->min("etoscreated");
            $maxyear = Pagam::whereNotNull('etoscreated')->max("etoscreated");

        return view('pagams.index', compact('pagams','minyear','maxyear'));
            }```        
The statements which are repeated into somae methods of the Controller are        
      ``` $pagams = Pagam::with('unit')
                ->where('unit_id',$currentenoriaid)
                ->orderBy('arprot')
            ->get();
            $minyear = Pagam::whereNotNull('etoscreated')->min("etoscreated");
            $maxyear = Pagam::whereNotNull('etoscreated')->max("etoscreated");```
        The Pagam is the model        

You can use a view composer to share that information

https://laravel.com/docs/12.x/views#view-composers

I would also suggest that you code in English, you will get a lot of help from the framework.

Thanks for answering. If I am not mistaken, View Composers are a very good solution for sharing the same data in multiple blade views. I have a different problem: I want to be able to use the same Eloquent query in whatever controller's methods.

Since the code you have shown only passes those to the view, then it makes sense to use a view composer. If you just to use them for some logic in other methods in the controller, then I would set them in a constructor method.

class PagamController extends Controller
{
	protected int $minYear;
	protected int $maxYear;

    public function __construct()
    {
        $this->minYear = Pagam::whereNotNull('etoscreated')->min("etoscreated");
		$this->maxYear = Pagam::whereNotNull('etoscreated')->max("etoscreated");
    }

The statements which are repeated into somae methods of the Controller are…

@adamnet Then you clearly have some sort of partial in your layout template if you need to copy-and-paste this query in multiple controllers. And you’ve already been told that the solution to that problem is view composers. So why do you keep creating posts with the same question when you’ve already been given the answer?

So, create a view composer with the query, and bind it to the relevant view.

Thank you Tray2. I will try this and let you know.

Thank you very much Snapey! Your suggestions touched the right point!! I will go using class based blade components. Again thanks a lot!!