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

Fixed some small typos in generic_relations model tests 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@3156 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2006-06-19 20:19:01 +00:00
parent 1a1b1aa5db
commit ed6d7285dd
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
tests/modeltests/generic_relations/models.py
View File

@ -64,7 +64,7 @@ API_TESTS = """
... o.save() ... o.save()
# Objects with declared GenericRelations can be tagged directly -- the API # Objects with declared GenericRelations can be tagged directly -- the API
# mimics the many-to-many API # mimics the many-to-many API.
>>> lion.tags.create(tag="yellow") >>> lion.tags.create(tag="yellow")
<TaggedItem: yellow> <TaggedItem: yellow>
>>> lion.tags.create(tag="hairy") >>> lion.tags.create(tag="hairy")
@ -79,26 +79,26 @@ API_TESTS = """
>>> bacon.tags.all() >>> bacon.tags.all()
[<TaggedItem: fatty>, <TaggedItem: salty>] [<TaggedItem: fatty>, <TaggedItem: salty>]
# You can easily access the content object like a foreign key # You can easily access the content object like a foreign key.
>>> t = TaggedItem.objects.get(tag="salty") >>> t = TaggedItem.objects.get(tag="salty")
>>> t.content_object >>> t.content_object
<Vegetable: Bacon> <Vegetable: Bacon>
# Recall that the Mineral class doesn't have an explicit GenericRelation # Recall that the Mineral class doesn't have an explicit GenericRelation
# defined. That's OK since you can create TaggedItems explicitally. # defined. That's OK, because you can create TaggedItems explicitly.
>>> tag1 = TaggedItem(content_object=quartz, tag="shiny") >>> tag1 = TaggedItem(content_object=quartz, tag="shiny")
>>> tag2 = TaggedItem(content_object=quartz, tag="clearish") >>> tag2 = TaggedItem(content_object=quartz, tag="clearish")
>>> tag1.save() >>> tag1.save()
>>> tag2.save() >>> tag2.save()
# However, not having the convience takes a small toll when it comes # However, excluding GenericRelations means your lookups have to be a bit more
# to do lookups # explicit.
>>> from django.contrib.contenttypes.models import ContentType >>> from django.contrib.contenttypes.models import ContentType
>>> ctype = ContentType.objects.get_for_model(quartz) >>> ctype = ContentType.objects.get_for_model(quartz)
>>> TaggedItem.objects.filter(content_type__pk=ctype.id, object_id=quartz.id) >>> TaggedItem.objects.filter(content_type__pk=ctype.id, object_id=quartz.id)
[<TaggedItem: clearish>, <TaggedItem: shiny>] [<TaggedItem: clearish>, <TaggedItem: shiny>]
# You can set a generic foreign key in the way you'd expect # You can set a generic foreign key in the way you'd expect.
>>> tag1.content_object = platypus >>> tag1.content_object = platypus
>>> tag1.save() >>> tag1.save()
>>> platypus.tags.all() >>> platypus.tags.all()