fitztrev/query-tracer

Backtrace database queries

Maintainers

Details

github.com/fitztrev/query-tracer

Source

Issues

Installs: 18 243

Dependents: 0

Suggesters: 0

Security: 0

Stars: 229

Watchers: 7

Forks: 5

Open Issues: 2

1.0.2 2016-05-22 13:30 UTC

Requires

Requires (Dev)

MIT 351fff26cec4962e414864fd9c376923a94ace28

databasedebuglaraveleloquent

This package is not auto-updated.

Last update: 2024-12-19 03:53:49 UTC

README

Build Status Latest Stable Version

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';
}