Pfthb

There is a model data:

class Order extends Model

How to write a custom method inside the Order class so that it can be called in constructor like this:

Order::myMethod()
Order->myMethod()

Where myMethod is:

public function myMethod() 
 return DB::query(<SQL QUERY>);

Purpose is to move SQL queries inside model's class, that don't mess this code in controllers.

Guess you are asking about the static functions:

class Order extends Model 
 public static function myMethod() 
 

and you can call it anywhere like

Order::myMethod();

Rather create a custom function in Model, You can use traits to achieve the desired output.

Please follow either steps:-

• https://medium.com/@kshitij206/traits-in-laravel-5db8beffbcc3


• https://www.conetix.com.au/blog/simple-guide-using-traits-laravel-5

I can't understand your exact problem is. but if you are using laravel, then you can write custom method inside the ABC model like this

class ABC extends Model

 //here is your fillable array;
 public function abc()
 
 //Here is your Eloquent statement or SQL query;
 

just call this abc() method inside the controller like this

 use ABC;
 class AbcController extends Controller
 
 private $_abc; // it is private variable
 // this is constructor
 public function __construct(ABC $abc)
 
 $this->_abc= $abc;
 
 public function abcMethod()
 
 $this->_abc->abc();
 
 

Thanks

You can achieve the desired behavior using magic methods __call and __callStatic
if your real method is static you can use __call() to intercept all "non static" calls and use it to call the static and use __callStatic to forward the calls to a new instance to that class .

Your methods should be always static because if a non static method exists and you are calling it statically php raises an error

Non-static method Foo::myMethod() should not be called statically

No problem if your method is static

class Order extends Model 
 public static function myMethod() 
 return static::query()->where(...)->get(); // example
 
 public function __call($name, $arguments) 
 return forward_static_call_array([__CLASS__, $name], $arguments);
 
 public static function __callStatic($name, $arguments) 
 return call_user_func_array([app(__CLASS__), $name], $arguments);
 


(new Order())->myMethod();
Order::myMethod();

I don't believe I'm understanding your intention. You've stated:

Purpose is to move SQL queries inside model's class, that don't mess this code in controllers.

Why does the Order->myMethod() need calling inside the constructor? If you're trying to design your data access layer to work efficiently, you can use data repositories.