p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[1.8.x] Fixed #25430 -- Fixed incorrect RunSQL examples. 

Backport of 95edabb45e from master
This commit is contained in:
Flavio Curella 2015-09-18 21:35:28 -05:00 committed by Tim Graham
parent 1abd177696
commit 63147dfa07
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/ref/migration-operations.txt
View File

@ -222,8 +222,8 @@ queries and parameters in the same way as :ref:`cursor.execute()
<executing-custom-sql>`. These three operations are equivalent:: <executing-custom-sql>`. These three operations are equivalent::
migrations.RunSQL("INSERT INTO musician (name) VALUES ('Reinhardt');") migrations.RunSQL("INSERT INTO musician (name) VALUES ('Reinhardt');")
migrations.RunSQL(["INSERT INTO musician (name) VALUES ('Reinhardt');", None]) migrations.RunSQL([("INSERT INTO musician (name) VALUES ('Reinhardt');", None)])
migrations.RunSQL(["INSERT INTO musician (name) VALUES (%s);", ['Reinhardt']]) migrations.RunSQL([("INSERT INTO musician (name) VALUES (%s);", ['Reinhardt'])])
If you want to include literal percent signs in the query, you have to double If you want to include literal percent signs in the query, you have to double
them if you are passing parameters. them if you are passing parameters.
@ -232,8 +232,8 @@ The ``reverse_sql`` queries are executed when the migration is unapplied, so
you can reverse the changes done in the forwards queries:: you can reverse the changes done in the forwards queries::
migrations.RunSQL( migrations.RunSQL(
["INSERT INTO musician (name) VALUES (%s);", ['Reinhardt']], [("INSERT INTO musician (name) VALUES (%s);", ['Reinhardt'])],
["DELETE FROM musician where name=%s;", ['Reinhardt']], [("DELETE FROM musician where name=%s;", ['Reinhardt'])],
) )
The ``state_operations`` argument is so you can supply operations that are The ``state_operations`` argument is so you can supply operations that are