connection.queries reports different SQL query than MySQL log

[creecode]

I'm using MySQL 5.0.x and Django v1.0.2.

The QuerySet...

Entry.objects.filter ( content__search = 'heat pipes' )

...is producing this SQL...

SELECT my_app_entry.id, my_app_entry.title, my_app_entry.content, my_app_entry.url, my_app_entry.created, my_app_entry.modified, my_app_entry.website_id FROM my_app_entry WHERE MATCH (my_app_entry.content) AGAINST (heat pipes IN BOOLEAN MODE) LIMIT 21

...as reported from connection.queries. I seem to be getting results back with no reports of errors but if you look closely at the above SQL you'll see there is a syntax error. I verified this by putting the above SQL into a client app that tried to run the above SQL and received an error.

At this point I was a bit confused and took a look at the MySQL log and it reported...

SELECT my_app_entry.id, my_app_entry.title, my_app_entry.content, my_app_entry.url, my_app_entry.created, my_app_entry.modified, my_app_entry.website_id FROM my_app_entry WHERE MATCH (my_app_entry.content) AGAINST ('heat pipes' IN BOOLEAN MODE) LIMIT 21

You'll notice that the query string in the SQL here is properly single quoted.

[Karen Tracey]

Yes, the connection.queries log doesn't necessarily include quoting. Quoting is done by the backend, and if the backend does not provide a method to retrieve the exact sql sent to the DB for the last query (psycopg2 seems to be the only one that does), then the queries are logged without quoting. Changing component to doc, as this behavior is known and expected, but should probably be mentioned in the doc as it comes up and confuses people from time to time.

[Karen Tracey]

(In [10847]) Fixed #11209 -- Added a note to doc on connection.queries that the logged sql may not inlude parameter quoting.

[Karen Tracey]

(In [10848]) [1.0.X] Fixed #11209 -- Added a note to doc on connection.queries that the logged sql may not inlude parameter quoting.

r10847 from trunk.