Improved docs/db-api.txt to say add_FOO() methods always return the newly-created object.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@825 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2005-10-10 20:18:56 +00:00
parent 705a2c31c1
commit eb4f16e666
1 changed files with 3 additions and 2 deletions

View File

@ -449,8 +449,7 @@ Related objects (e.g. ``Choices``) are created using convenience functions::
>>> p.get_choice_count() >>> p.get_choice_count()
4 4
Each of those ``add_choice`` methods is equivalent to (except obviously much Each of those ``add_choice`` methods is equivalent to (but much simpler than)::
simpler than)::
>>> c = polls.Choice(poll_id=p.id, choice="Over easy", votes=0) >>> c = polls.Choice(poll_id=p.id, choice="Over easy", votes=0)
>>> c.save() >>> c.save()
@ -459,6 +458,8 @@ Note that when using the `add_foo()`` methods, you do not give any value
for the ``id`` field, nor do you give a value for the field that stores for the ``id`` field, nor do you give a value for the field that stores
the relation (``poll_id`` in this case). the relation (``poll_id`` in this case).
The ``add_FOO()`` method always returns the newly created object.
Deleting objects Deleting objects
================ ================