How to override the Laravel Illuminate Database Connection.php run method?

Question

I need to customize the callback function call in the run() method of the Connection.php class, located in the frameword Laravel src Illuminate Database Connection.php

The problem is that it is in the project vendor folder, which means it is not the best place to make the change.

Could someone shed some light on how I can do that? The project contains several classes and numerous query operations scattered within the project. And since we now need to change the calls to API, the best place to change is in this method [run()]. The commented line

// $result = $this->runQueryCallback($query, $bindings, $callback);

contains the original package call. My change is for the API calling function, which already returns the data similarly to "runQueryCallbck"

$result = execSqlApiFirebird($query);

Here is the complete method:

/**
 * Run a SQL statement and log its execution context.
 *
 * @param  string  $query
 * @param  array  $bindings
 * @param  \Closure  $callback
 * @return mixed
 *
 * @throws \Illuminate\Database\QueryException
 */
protected function run($query, $bindings, Closure $callback)
{
    $this->reconnectIfMissingConnection();

    $start = microtime(true);

    // Here we will run this query. If an exception occurs we'll determine if it was
    // caused by a connection that has been lost. If that is the cause, we'll try
    // to re-establish connection and re-run the query with a fresh connection.
    try {
        $query = str_replace(array('?'), array('\'%s\''), $query);
        $query = vsprintf($query, $bindings);
        // dump($query);
        // $result = $this->runQueryCallback($query, $bindings, $callback);
        $result = execSqlApiFirebird($query);
        // dd($result);
    } catch (QueryException $e) {
        $result = $this->handleQueryException(
            $e, $query, $bindings, $callback
        );
    }

    // Once we have run the query we will calculate the time that it took to run and
    // then log the query, bindings, and execution time so we will report them on
    // the event that the developer needs them. We'll log time in milliseconds.
    $this->logQuery(
        $query, $bindings, $this->getElapsedTime($start)
    );
    // dump($result);
    return $result;
}

Answer 1

I decided to build endpoint in API and linking directly to Controller the calls. There I build the objects and forgetfulness the Eloquent (It would be interesting to implement this modification, because the MVC would be intact throughout the project).
But in a company that seeks results, less is more. I ended up doing it the way I know rather than continuing to look for other ways.
Who knows in the near future I solve it right? = D
For now, it is better to deliver quick result and keep the job. rsrs