Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added stacktraces for queries #275

Closed
wants to merge 2 commits into from
Closed

added stacktraces for queries #275

wants to merge 2 commits into from

Conversation

dmecke
Copy link

@dmecke dmecke commented Feb 28, 2014

I've added a stacktrace to the query profiler. This can help to find out why a specific query has been executed. This one depends on pull request doctrine/dbal#535 in doctrine/dbal as it fetches the stacktrace information.

@stof
Copy link
Member

stof commented Feb 28, 2014

I don't really see the need of using a separate action to do the rendering of the trace, whcih is just rendering of data stored in the profile.

a separate action is used to render the query explanation, because it requires explaining the query first. IT is not the case here

@stof
Copy link
Member

stof commented Apr 23, 2015

closing as the DBAL PR has been rejected

@sustmi
Copy link
Sponsor

sustmi commented Dec 6, 2019

Just for reference, this feature is already available in Doctrine bundle from v1.11.0: https://symfony.com/blog/new-in-doctrinebundle-1-11-0#store-backtraces-when-profiling-queries (PR: #954) .

You just need to enable it by setting doctrine.dbal.profiling_collect_backtrace: true (I set it to '%kernel.debug%' instead because it is the default value of profiling setting).

Web search got me here and from this conversation it looks like it may not be available yet.

@stof
Copy link
Member

stof commented Dec 6, 2019

Well, this conversation is from 2015. There are other PRs newer than that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants