Show stack trace of Doctrine query

[iluuu1994]

Description

When a page executes too many queries it would be extremely useful to know where these queries are executed. Since these queries are generated by Doctrine it is very non-obvious where they are coming from.

Example

I would add another toggle "Show stack trace" that shows you exactly where the query was executed in your code.

[javiereguiluz]

@iluuu1994 I agree that this would be great. However, it seems that Doctrine DBAL is not ready for this. Check doctrine/DoctrineBundle#722 (and duplicated issues like doctrine/DoctrineBundle#800).

So, I must close this and I hope that one day this is fixed in Doctrine and leveraged in DoctrineBundle. Thanks.

[iluuu1994]

@javiereguiluz Thanks for investigating!

DBAL already has a DebugStack logger doing this

Is this not an option?

[javiereguiluz]

Sadly that's not an option. The Doctrine data collector used in DoctrineBridge is already using it. However, as you can see in its code (https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Logging/DebugStack.php) it doesn't log who/where the query was executed. That's why we don't have that info in the data collected by Symfony:

[iluuu1994]

Bummer. Anyway, thanks @javiereguiluz!

[alcaeus]

Just to follow up, this was added in doctrine/DoctrineBundle#954 and will be released in version 1.11.0 of the Doctrine Bundle 👍

[iluuu1994]

Hype! Thanks @ottaviano and @alcaeus!

[mayro]

Hello @alcaeus,
I'm using doctrine 1.11.2 and i haven't this profiling, i have only the query...

[stof]

@mayro due to the performance impact (it increases memory usages of the collected queries), you need to opt-in in your DoctrineBundle config (see profiling_collect_backtrace). It is turned off by default.

[mayro]

Thanks @stof i enable the profilning_collect_backtrace, I can now trace the steps but anyway it doesn't log where the query was executed... I'm using the Master/Slave connection and i need to know in which Database my query executed

[stof]

"in which connection of the Master/Slave" is not the same question than "where in the project", which is what a debug backtrace provides.

[mayro]

@stof Thank you for clarifying that. so is there any way to know in which connection (Master or slave) the query was executed please ?