fitztrev/query-tracer

Backtrace database queries

1.0.2 2016-05-22 13:30 UTC

Requires

• php: >=5.5.9
• laravel/framework: ^5.2

Requires (Dev)

• illuminate/database: 5.2.*
• orchestra/testbench: ~3.0
• phpunit/phpunit: ~4.1

MIT

• database
• debug
• laravel
• eloquent

README

Find exactly where a specific database query is being called in your Laravel application.

Want to optimize or debug your database queries but not sure where they're being called? See how it works below with Clockwork:

If you use Debugbar, it has this functionality built-in if you set debugbar.options.db.backtrace to true.

Installation

1. Install via composer:

   composer require fitztrev/query-tracer

2. Add the service provider to your config/app.php:

   'providers' => [
       // ...
       Fitztrev\QueryTracer\Providers\QueryTracerServiceProvider::class,
   ],

How does it do it?

It makes use of Laravel's global query scopes to do a backtrace and find where a query originated. Then it puts that info in extraneous but helpful WHERE clauses.

By default, it's only enabled when debug is on. You can change this behavior for specific models by adding an enableQueryTracer() method to your model(s). For example:

public function enableQueryTracer()
{
    return config('app.env') == 'local';
}