Skip to content

Conversation

@n0099
Copy link
Contributor

@n0099 n0099 commented Jul 4, 2025

@greg0ire
Copy link
Member

greg0ire commented Jul 5, 2025

Sorry for inadvertently closing your other PR yesterday, it was because I deleted the target branch.

Please kindly squash your commits together. If you don't, we'll try to remember to do it for you but it's best if you save us this trouble.

How to do that?

  1. git rebase -i origin/3.5.x, assuming origin is a git remote that points to this repository, and not your fork. If you're not sure what your remotes are, run git remote -vvv, there should be your fork and the holy/reference/base/origin/whatever-you-call-it repository.
  2. A window will show up with many lines, replace pick with fixup on every line but the first one
  3. Close your editor, git should do its magic, and you should end up with one commit
  4. Use git push --force to overwrite what you already pushed. Don't forget the --force option otherwise git will try to merge both things together.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 5, 2025

There hasn't been any activity on this pull request in the past 90 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days.
If you want to continue working on it, please leave a comment.

@github-actions github-actions bot added the Stale label Oct 5, 2025
@n0099
Copy link
Contributor Author

n0099 commented Oct 8, 2025

bump

Modify the Output Walker to get the raw SQL with interpolated parameters
--------------------------------------------------------

Sometimes we may want to log or trace the raw SQL being generated from its DQL,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should elaborate here. I think your need is to get a SQL statement that you can replay yourself, with an SQL client. If so, please say so explicitly and clearly.

Copy link
Contributor Author

@n0099 n0099 Oct 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me there's two main usage of raw SQL: log the SQL being executed to debug possible slow queries in future, and UNION results of multiple DQL with WHERE as only DBAL query supports UNION as in https://stackoverflow.com/questions/4155288/how-to-write-union-in-doctrine-2-0/79647475#79647475 and https://github.com/n0099/open-tbm/blob/c960f09242097937403880a6ebd02ef4946ce3a8/be/src/PostsQuery/QueryResult.php#L219-L237.

Copy link
Contributor Author

@n0099 n0099 Oct 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Sometimes we may want to log or trace the raw SQL being generated from its DQL,
Sometimes we may want to log or trace the raw SQL being generated from its DQL
for profiling slow queries in the future or audit queries that changed many rows

@github-actions github-actions bot removed the Stale label Oct 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants