innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Small improvement to docs/model-api.txt 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@1306 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2005-11-20 17:35:29 +00:00
parent 2bb18eddbe
commit c472b1471d
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/model-api.txt
View File

@ -1079,9 +1079,17 @@ the resulting rows. Example::
row = cursor.fetchone() row = cursor.fetchone()
return row return row
Note that ``db`` and ``cursor`` simply use the standard `Python DB-API`_. If your custom SQL statement alters the data in your database -- for example,
via a ``DELETE``, ``INSERT`` or ``UPDATE`` -- you'll need to call
``db.commit()``. example::
If you're not familiar with the Python DB-API, note that the SQL statement in def my_custom_sql2(self):
cursor = db.cursor()
cursor.execute("DELETE FROM bar WHERE baz = %s", [self.baz])
db.commit()
``db`` and ``cursor`` simply use the standard `Python DB-API`_. If you're not
familiar with the Python DB-API, note that the SQL statement in
``cursor.execute()`` uses placeholders, ``"%s"``, rather than adding parameters ``cursor.execute()`` uses placeholders, ``"%s"``, rather than adding parameters
directly within the SQL. If you use this technique, the underlying database directly within the SQL. If you use this technique, the underlying database
library will automatically add quotes and escaping to your parameter(s) as library will automatically add quotes and escaping to your parameter(s) as