Commit 975c5afd authored by Claude Paroz's avatar Claude Paroz
Browse files

Added release note about percent literals in cursor.execute 

Thanks Aymeric Augustin for noticing the omission and Tim Graham
for the text review.
Fixes #9055 (again).
parent 23229061

docs/releases/1.6.txt

+18 −0
Original line number Diff line number Diff line
@@ -392,6 +392,24 @@ If you do not apply this change, the behaviour is unchanged: on MySQL, IPv6 
addresses are silently truncated; on Oracle, an exception is generated. No

database change is needed for SQLite or PostgreSQL databases.



Percent literals in ``cursor.execute`` queries

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



When you are running raw SQL queries through the

:ref:`cursor.execute <executing-custom-sql>` method, the rule about doubling

percent literals (``%``) inside the query has been unified. Past behavior

depended on the database backend. Now, across all backends, you only need to

double literal percent characters if you are also providing replacement

parameters. For example::



    # No parameters, no percent doubling

    cursor.execute("SELECT foo FROM bar WHERE baz = '30%'")



    # Parameters passed, non-placeholders have to be doubled

    cursor.execute("SELECT foo FROM bar WHERE baz = '30%%' and id = %s", [self.id])



``SQLite`` users need to check and update such queries.



Miscellaneous

~~~~~~~~~~~~~