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

Removed section in docs/model-api.txt about connection.commit(), which no longer exists 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@2863 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2006-05-06 23:16:43 +00:00
parent 3c72a46f62
commit be0032f5ba
1 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/model-api.txt
View File

@ -1581,15 +1581,6 @@ rows. Example::
row = cursor.fetchone() row = cursor.fetchone()
return row return row
If your custom SQL statement alters the data in your database -- for example,
via a ``DELETE`` or ``UPDATE`` -- you'll need to call ``db.commit()``. Example::
def my_custom_sql2(self):
from django.db import connection
cursor = connection.cursor()
cursor.execute("DELETE FROM bar WHERE baz = %s", [self.baz])
connection.commit()
``connection`` and ``cursor`` simply use the standard `Python DB-API`_. If ``connection`` 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 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