From dc2933f73b4a970d6b37241b6f185bbbacd1bb69 Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Fri, 15 Jul 2005 18:40:21 +0000 Subject: Fixed #3 -- Made OneToOneField act like ForeignKey and ManyToManyField. This is the last big API change before the official launch. git-svn-id: http://code.djangoproject.com/svn/django/trunk@59 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/db-api.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/db-api.txt b/docs/db-api.txt index 2a41e9b373..f96b3ebca8 100644 --- a/docs/db-api.txt +++ b/docs/db-api.txt @@ -141,8 +141,7 @@ method. For example:: class Restaurant(meta.Model): ... fields = ( - meta.IntegerField('id', 'ID', primary_key=True, - rel=meta.OneToOne(places.Place, 'place', 'id')), + meta.OneToOneField(places.Place), ... ) @@ -294,7 +293,7 @@ For example:: Changing objects ================ -Once you've retrieved an object from the database using any of the above +Once you've retrieved an object from the database using any of the above options, changing it is extremely easy. Make changes directly to the objects fields, then call the object's ``save()`` method:: -- cgit v1.3