From e3ac3bc074b0fe56af856adb41d8220cfe376fbb Mon Sep 17 00:00:00 2001
From: Adrian Holovaty <adrian@holovaty.com>
Date: Mon, 22 May 2006 05:22:58 +0000
Subject: [PATCH] Added small bit to docs/sites.txt

git-svn-id: http://code.djangoproject.com/svn/django/trunk@2963 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 docs/sites.txt | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/sites.txt b/docs/sites.txt
index 153b0141c5..b78cd84d05 100644
--- a/docs/sites.txt
+++ b/docs/sites.txt
@@ -239,6 +239,11 @@ With this model, ``Photo.objects.all()`` will return all ``Photo`` objects in
 the database, but ``Photo.on_site.all()`` will return only the ``Photo``
 objects associated with the current site, according to the ``SITE_ID`` setting.
 
+Put another way, these two statements are equivalent::
+
+    Photo.objects.filter(site=settings.SITE_ID)
+    Photo.on_site.all()
+
 How did ``CurrentSiteManager`` know which field of ``Photo`` was the ``Site``?
 It defaults to looking for a field called ``site``. If your model has a
 ``ForeignKey`` or ``ManyToManyField`` called something *other* than ``site``,