Level 2
Have a look at https://github.com/itsgoingd/clockwork or https://github.com/barryvdh/laravel-debugbar
These are chrome extensions and will log db queries for you and present them in developertools.
2 likes
Nov 9, 2015
10
Level 6
Is there an easy way to find out where are my queries are being generated from?
Hi, I am building an application using Laravel 5.1. I am trying I use Eloquent as an ORM to interact with my database.
One of the things that I am having difficulties with is trying to identify the source of each query being generated my Eloquent.
Trying I understand what is being executed at the server, I turn on MySQL general log and log it to a table "for easy access." However, I got 36 queries being exexuted from a single page refresh "this is a red flag in my mind."
The challenge here is how to know what job/what at what point in my code was each query generated?
I want to make sure I don't sacrafy DB performance because I am trying to use Eloquent.
How can I drill down the source of each query?
Does Eliquent have its own log? If so where do I find it? If not how would I know what is generating these queries?
It would be very nice if Eloquent have its own general logs like MySQL. I would be a dream come true if the eloquent log would tell me at what point in my code query x was executed. To take this thought further, it will be yet more powerful if the queries are logged in a general format where one can get stats on how many time query x was generated regardless of the vales passes to it. It will help to know if query x was cached by the application or not.
Thank you for your help.
Level 88
Like said above, the laravel-debugbar is really usefull in this case!
Level 55
Along with the above packages, I sometimes prefer a more direct way that listens for SQL queries and dumps them right alongside your code; put the following in your routes.php file and that's all you need.
Event::listen('illuminate.query', function($sql) {
var_dump($sql);
});
This way you can not only see what query is being executed, but where it is being executed. It is great in finding N+1 issues when iterating through lists.
1 like
Level 6
@mstnorris is there a way to add a listener to show the query after it is prepared? Instead of looking at ? ? ? ? I like to evaluate the number that are being passed
Level 55
I'm not aware of a method to do that.
Level 41
@mstnorris @malhayek You can accept 3 more parameters. :)
Event::listen('illuminate.query', function($query, $bindings, $time, $name)
{
var_dump($query); // The query
var_dump($bindings); // The arguments being passed to the query
var_dump($time); // The amount of time the query took to run
var_dump($name); // The database connection name
});
Level 1
You can also do it like following:
\DB::listen(function ($sql) {
var_dump($sql);
});
Using service provider to register your query listener would help you in this situation, following documentation will guide you for it:
http://laravel.com/docs/5.1/database#listening-for-query-events
Level 88
You can also do this
User::where('username', '=', $name)->orWhere('active', '=', 1)->toSql();
You can perform the toSql function instead of get or first
Level 2
https://twitter.com/barryvdh/status/732570607058046977
If you're using https://github.com/barryvdh/laravel-debugbar it has an option to turn backtrace on which will show you the file that is making the query. In your config/debugbar.php file scroll down to the "options" array and set 'backtrace' => true.
https://github.com/barryvdh/laravel-debugbar/blob/master/config/debugbar.php#L124
Enjoy! =) -Tim
4 likes
Level 4
Thanks @TimG1 , it was really helpful!
Please or to participate in this conversation.