Inconsistency in Query.__str__ and actual query

[Andriy Sokolovskiy]

Inspired by ​http://stackoverflow.com/a/31287932/2116126
Different backends may quote or do something with params, so actual query diffs from the Query.__str__, which is inconsistent.
I think Django should format params how backend actually do this to prevent confusion.

[Tim Graham]

According to #17741, str(query) "isn't intended to give you valid SQL, just a basic representation of the query." Therefore, not sure it's feasible or practical to implement this.

[Andriy Sokolovskiy]

Well, I can investigate if it is feasible.
The point about "a basic representation of the query" seems strange for me. Why should we have a tool that differs from reality?
The practical thing is to have ability to get actual query without looking to logs.

[Tim Graham]

As the linked ticket says, "There isn't [a way to get the actual query], because Django never actually interpolates the parameters: it sends the query and the parameters separately to the database adapter, which performs the appropriate operations."

[Claude Paroz]

Feel free to reopen if you can come up with something more accurate than the current situation.